We have noticed many users in the EOS community talking about Block.one’s tokens, but there seems to always be some confusion around their vesting schedule. We at EOS Canada wanted to clear this up and present the code that handles this -- providing you with the definitive answer!
If you've gone through our Multisig and Permission series, you should know how to craft an account’s permission structure to provide the security that you need, and how to create an msig proposal. We can finally move on to gathering the required signatures over the blockchain.
Following the reading of our Overview of Multisig and Permissions on EOSIO and Using eosc to Update Your Account’s Authority Structure, you should now be comfortable with altering the authority structure of your account. If you have chosen to leverage the native multisig features for additional security, we must now discuss how to collect the required signatures to satisfy it.
On the second part of our Multisig and Permission series, we review how to update the authority structure of your account on an EOSIO blockchain, which is still somewhat of a mystery to many users. By using the correct tools and having a proper understanding of what the blockchain requires, it becomes rather simple and you’ll be able to harness the incredible power of this unique feature.
One of the differentiators that sets EOS apart from other blockchains is its resource staking mechanism -- users get access to chain-wide CPU and bandwidth resources by staking EOS tokens. However, with the incredible user and dapp adoption that we’ve seen, resource staking has also become a bottleneck at times. Block Producers and Block.one have both been working to resolve these issues.
Keen observers will have noticed that on the EOS blockchain there are system accounts that control various functions. These are all denominated by the prefix eosio.*. At EOS Canada, we felt it would be useful to provide an overview of which system accounts exist, and what they each control.
Brandon Parker, also known as HappyMoneyMan, invited Alexandre Bourget to his podcast "The EOS Podcast" to discuss all things EOS. They focused on our new dfuse API, sidechains and interblockchain communication, decentralization and when it adds value, microforks and the CPU issues that may cause them, and much more!
Microforks can happen on any blockchain. Alexandre explains what a microfork is, when one would happen, and why it would happen.
Still have questions? Join us in our Telegram channel