RAM, CPU, and NET limits
The FIO Chain inherits EOSIO resource management, but makes a number of modifications to it to remove the user complexity, while supporting its fee model.
Every new account will have initial RAM allocated to 25600 bytes (25K). Every time an account pays a fee or covers a transaction from a bundle, that account’s RAM will be permanently increased by the number associated with the executed action. In case of multi-action transactions, each action will increment the RAM independently.
|Action||Increase amount in bytes|
|UPDATEAUTH||1,024 per 1,000 bytes of trx size|
|PROPOSE||1,024 per 1,000 bytes of trx size|
Account A registers a FIO Address for themselves and pays a 40 FIO fee Account A RAM is increased by 2,560 bytes Account A transfers funds to a key not associated with an account Account A RAM is increased by 2,560 bytes Account B is created with initial limit of 25KB of RAM
Scheduled BP RAM override
When a BP is added to the BP schedule to produce blocks, their RAM limit will be changed to unlimited When a BP is removed from BP schedule, their RAM will be changed to existing RAM usage of their account + 25K
Transaction size limit
Every transaction is limited to max size of 8098 bytes. BPs in schedule as exempt from the transaction limit for propose action.
All accounts are created with unlimited CPU, as only authorized contracts with pre-approved CPU usage can run on the FIO Chain.
All accounts are created with unlimited NET, as there is a transaction size limit.