EOS.IO Stack Exchange is a question and answer site for users and developers of distributed applications built on top of the blockchain operating system, EOS.IO. It only takes a minute to sign up.
Sign up to join this community
There are several eosio.* accounts - also referred to as system accounts - described in the bios sequence tutorial:
eosio.bpay
eosio.msig
eosio.names
eosio.ram
eosio.ramfee
eosio.saving
eosio.stake
eosio.token
eosio.vpay
It is mentioned there that eosio.msig is a privileged account
What is the purpose of each of these accounts?
Bios sequence tutorial (Deprecated Wiki) explain these well - eosio.token, eosio.msig.
The remaining accounts are described below.
I refer to the following link. https://steemit.com/eos/@slavix/block-one-releases-eosio-dawn-4-2
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, transfer, and get information about tokens.
The msig contract enables and simplifies defining and managing permission levels and performing multi-signature actions.
The eosio.system contract contract provides the actions for pretty much all token-based operational behavior. Prior to installing the system contract, actions are done independent of accounting. Once the system contract is enabled, actions now have an economic element to them. Resources (cpu, network, memory) must be paid for. Likewise, new accounts must be paid for. The system contract enables tokens to be staked and unstaked, resources to be purchased, potential producers to be registered and subsequently voted on, producer rewards to be claimed, privileges and limits to be set, and more.
