I am trying to setup a private eos for my app, I want to know if there is possible to change the usage of CPU, NET etc in private setup without staking tokens. If YES, then please guide me with the procedure.

  • I don't understand what you are asking for.
    – cmadh
    Jan 10, 2020 at 7:49
  • I want to setup a local setup of eos, I want that if a user has not staked tokens he can still be able to make transactions on the local network Jan 10, 2020 at 9:34

2 Answers 2


Easy: Use eosio.bios instead of eosio.system contract

Advanced: newaccount in eosio.system initializes account's resources with 0.

   void native::newaccount( const name&       creator,
                            const name&       newact,
                            ignore<authority> owner,
                            ignore<authority> active ) {
      /* ... */

      user_resources_table  userres( get_self(), newact.value );

      userres.emplace( newact, [&]( auto& res ) {
        res.owner = newact;
        res.net_weight = asset( 0, system_contract::get_core_symbol() );
        res.cpu_weight = asset( 0, system_contract::get_core_symbol() );

      // three zero params mean ram, net and cpu in order
      // you can change these to proper values, or set -1 to make them unlimited
      set_resource_limits( newact, 0, 0, 0 );
  • Yes, eosio.bios contract works well for me. You'll be able to create accounts, set the producer schedule and get ordered transaction history as per normal.
    – Scott Owen
    Mar 16, 2020 at 0:37

You can't just reduce the resources usage if you want to get an alternative and don't have EOS tokens for stake see the REX(Resources Exchange System) in eosio documentation.

Also must watch this video for simple explanation of REX video.

For explanation of different REX functionalities see this blog article

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.