0

I want to deploy a private eos network on which users don't have to stake or pay ram or network or cpu is that possible if yes how so ? do I have to tweak code in eosio.system contracts Also what are risks involved in doing so i mean would that be architecturally right.

0

Resources are managed by eosio.system contract, so if you don't deploy eosio.system to eosio account, there is no limitations on sending transactions.

For example, you can run single-node local testnet like this:

nodeos -e -p eosio --plugin eosio::chain_api_plugin

After launching single-node local testnet, create account by the next command:

cleos create account eosio YOUR_ACCOUNT_NAME

You can see all resources such as CPU, NET bandwidth and RAM are unlimited.

cleos get account YOUR_ACCOUNT_NAME

A limitation on resource makes blockchain secure. For example, in above single-node local testnet, user can send transactions infinitely (Unlimited CPU/NET), it can be a point of DOS (Denial-Of-Service) attack. Moreover, when network is congested, CPU and NET set priorities among transactions, so block producers can determine which transaction should be processed first.

| improve this answer | |
  • how to can we regproducer without system contract can we ? – hassan ahmed Jun 18 at 13:17
  • also are the accounts created with cleos create account command and function newaccount (github.com/EOSIO/eosio.contracts/blob/…) basically same or not ? – hassan ahmed Jun 18 at 15:29
  • Use eosio.bios contract instead of eosio.system. cleos create account only calls newaccount, but cleos system newaccount will send a transaction consisting of 3 actions, newaccount, delegatebw (for CPU/NET staking) and buyram. – conr2d Jun 18 at 16:25

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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