You are viewing a single comment's thread from:
RE: The "REAL" EOS - Fighting for Identities
This is a no-brainer I guess. No one is above the law. So, no special treatment whatsoever just because you are tasked to set the EOS MainNet into motion. Giving them special privilege would only advance themselves in the competition due to that special name endowed upon them. What about the latecomers?
During the boot process of the mainnet the group of block producers involved have direct control of the "eosio" account. This is a privileged system account that can "do anything it wants".
Can you please elaborate on this. Are you saying that they, fingers crossed, will be able to modify the code or insert something into it?
At network creation the boot node will need this power to load the necessary system contracts and snapshot. Once this is done eosio control is transferred to the governance system. The community is devising several verification methods to be sure that the boot node did not abuse this power by inserting custom code or manipulating the snapshot prior to selecting a network as the mainnet.
Only one node will initiate this process? If so, how is it being selected?
This is a great question. We all need to form consensus on a way to validate which node should be selected. Currently the BIOS Boot page is peer reviewing candidates based on launch drills but this does not cover the entire BP community.