Skip to main content
4 votes
Accepted

What is the purpose for each of the eosio.* system accounts?

Bios sequence tutorial (Deprecated Wiki) explain these well - eosio.token, eosio.msig. The remaining accounts are described below. all RAM trading fees sent from user to eosio.ramfee all proceeds ...
smarteasy's user avatar
  • 1,015
2 votes

Initialization of system account within unit tests

Found the answer. It is genesis block initialization (mostly by eosio.bios.wast).
Teresa's user avatar
  • 125
1 vote

Error: Provided keys, permissions, and delays do not satisfy declared authorizations

This error message means you do not have the correct permissions to run the command as the account eosio. You need to make sure that the private key for the eosio account is in your wallet. You can do ...
Phillip Hamnett - EOS42's user avatar
1 vote
Accepted

Issue registering proxy in a new EOS enviroment

I solve it myself. The issue was with the order of setting up the system contracts. The eosio.bios contract must be set before the eosio.system contract. Then everything worked
KrisKoin's user avatar
1 vote

Who can use EOS tokens belonging to eos.ramfee?

These are locked and are waiting on a community decision on how to use them. Ram fees plus name auction fees will probably be added to the Resource Exchange (REX) pool. This will be paid to accounts ...
Ami Heines's user avatar
  • 1,686
1 vote

What is the purpose for each of the eosio.* system accounts?

This article goes into detail. https://developers.eos.io/eosio-nodeos/docs/bios-boot-sequence Here are some that I found: The eosio.token contract. This contract enables you to create, issue, ...
Nat's user avatar
  • 3,425

Only top scored, non community-wiki answers of a minimum length are eligible