This week’s Custodian Board (Custodians are re-elected every 7 days! If you want to engage in running eosDAC and make decisions for it, stake a minimum of 35000 EOSDAC and register yourself as a candidate on https://members.eosdac.io/)
This weeks highlights
- Want to participate in a community owned block producer and help enable decentralized autonomous communities? Joining eosDAC has become easier again with EOS Lynx wallet! Users can just head to ‘Explore’ menu and select ‘eosDAC Member Client’ to access to the client. Be part of the DAC future!
- EOS Weekly uploaded a fantastic 10-minute video explaining the current token Contract Security Risks and different solutions proposed, including eosDAC's. If you think you "own" an unsecured EOS token, you may be surprised to learn a single person really controls that token!
eosDAC, along with many other BPs, activated and tested the EOSIO Consensus Protocol Upgrade v1.8 on Jungle Testnet. Here’s what we learned. Once consensus protocol upgrade is activated, any node running < v1.8 of EOSIO software will kicked from the network.
(We wish this was our mainnet rank! Please support eosdacserver)
- For those who want to gift EOS accounts to noobs, check out this EOS Gift Card project. https://eosgiftcard.com/
Msigs of the Week
We have 1 msig proposal approved and executed this week:
Update The Constitution To V4 (try #2)
This is to reflect the changes in the custodian contract which include fixing the custodian payment calculation from "median" to "mean" and other small formatting issues. (You can see the full diff here)
Once this is updated, members will have to log back in to the member client and sign the constitution again.
And 1 to-be-approved:
Update Custodian Contract
This is a follow-up to actually update the custodian contract regarding the payment change described above.
Burn them all!
On 8th of May 2019 marks an incredible milestone for EOS - 34 Millions tokens from the eosio.saving account has been officially retired (AKA burned!).
Reasoning behind? The current inflation rate is set to be a total of 5%, of which 1% goes to BP rewards and the rest of 4% of inflated tokens were initially reserved to fund the EOS Worker Proposal System but never served the community and been just accumulated in the account. Debates and opinions raised by the community on how to utilise this fund (for example) but the agreement could not be reached. On 22nd of April 2019 EOS Nation proposed the retire savings and this was executed with approvals of 15 Active BPs and 6 Stand-bys. (See the transaction 26ca16319febafc0942a8c6e3be26c16b84846b7cfe5f6ade906a0b86a6c2bb7)
Dan Larimer seemed to be supportive of this idea too as per his message earlier on:
Whether you supported the idea or not, you’ll all agree that this truly shows how EOS is governing itself. The idea was proposed, supported and executed by the ecosystem!
Related but a completely different news is that MEET.ONE has submitted a multisig-proposal to remove the 4% inflation on the EOS mainnet after testing the code on Kylin Testnet last week. If this proposal gets approved by 15 Active BPs, the EOS network will only retain 1% of the additional issuance for rewarding Block Producers. MEET.ONE has previously asked the community about the idea and the majority answered 'YES' for it! (See the Referendum and comments down below)
So, let us know what is your thought on this! If you aren't sure whther to support it or not, we strongly recommend you watch this video featuring Luke covering the subject:
EOSIO Labs™ Release: The Assert Manifest Security Model
Block.One introduces the concept of a Layered Security Model which firstly help the end users validate the source of the application (whether it’s legitimate), and secondly give them assurance that the transactions being posted by the application are legitimate by validating transaction contents. A great initiative to help the users understand what they are signing and to avoid fraudulent dApps. This is at its inception so if you would like to explore the concept in detail and leave feedback, read this post.
eosDAC Twitter highlights
Please vote for eosdacserver
Join our newsletter to stay informed and follow us on your favorite social media platform: