We are very excited to announce eosDAC custodian candidate voting is now live! Once we reach 15% of EOSDAC token holders voting for candidates, the DAC will be turned over to the top 12 voted custodian candidates via an automated permissions change on the dacauthority account.
한국어 번역본: eosDAC 관리인 후보 투표 개시!
Этот пост также доступен на русском языке: Голосование за Хранителей eosDAC запущено!
bài này có sẵn bằng tiếng việt: Chức Năng Bỏ Phiếu Bầu Ứng Viên Giám Hộ Đã Mở!
Esta publicación está disponible en vietnamita: ¡Ya se puede votar a los candidatos al primer Consejo de Representantes eosDAC!
The eosDAC community has been working hard to reach this important moment which included many off-chain requirements such as forming The DAC Foundation and securing commercial terms with a service company, namely Dacoco Gmbh. All registered members of eosDAC can now vote for custodian candidates they trust to secure the long-term value of the DAC.
In true, decentralized style, you can build the EOS Member Client yourself and run it locally using the code on our Github here in order to vote for your favorite candidates. You can also use the version hosted at https://members.eosdac.io/ Just click the Vote for Custodians menu item, review the profiles of the candidates, click the + button next to five you like, and then click Submit My Votes.
Once the required 15% threshold is met, the DAC permissions will be turned over so the code and funds which run the DAC will be controlled by the custodians who are voted in through on-chain voting of EOSDAC stake-weighted votes by registered members of eosDAC. This is a huge milestone for us as a community-owned EOS Block Producer and DAC Enabler. Our goal is to provide technical leadership and answer directly to the EOS community. We are also paving the way for a more decentralized future as we not only build but also use tools to enable Decentralized Autonomous Communities.
Thank you for your continued support as we build these open source, DAC-enabling tools. Please vote for eosdacserver to support our work and if you haven't already, register as a member of eosDAC and use your EOSDAC tokens to vote for custodians and help us fully launch the DAC by achieving 15% voting.
For a little more detail on the current technical structure of the DAC, read on!
In Terms of EOS Accounts and Code, What Is eosDAC?
The main EOS account which controls the DAC is called dacauthority. Click on "permissions" on the bloks.io explorer to see how it is set up:
Temporarily, the initial block producer team of Rob, Michael, and Luke will retain access to the EOS5XZMyRHJdq8DaCQbeK63SoAo1vmCLbW9bnvbiFPGYSGEsbVNxp owner key for a period of time to fix any technical problems which might arise such as a technical failure preventing the elected custodians from fulfilling their role or some other code bug which could not otherwise be corrected. After there is enough confidence within the community, that key will be resigned as well. The high, med, and low permissions correspond to the voting threshold requirements outlined in the eosDAC constitution. Once the DAC reaches 15%, the high, medium, low, and one permissions will be updated to be the accounts of the elected custodians.
The block producer account eosdacserver is also currently controlled via multisig by Rob, Michael, and Luke as you can see here:
There are also additional permissions configured for specific on-chain actions such as claiming block producer rewards.
Rob, Michael, and Luke have an active worker proposal to provide block production services to the DAC and in the future, control of that account will also be given over to the DAC so that, if the token holders decide via their custodian representatives to replace Rob, Michael, and Luke, they will have the on-chain ability to do so. This is important as we define decentralization as no single point of failure.
The next part of the DAC is the eosdactokens account which has all the code for the EOSDAC token including member registration which you can review here. As you can see, full control of this account is in the hands of dacauthority which will be controlled by the custodians when we reach 15% voting threshold required to launch the DAC:
The main functionality for the DAC can be found in the daccustodian account with code you can review here. This includes functions like claiming pay, nominating custodians, casting votes, updating configurations, and more:
The permissions on this account are again controlled by dacauthority with an additional time-delay xfer permission so all code-initiated transfers will have to delay transactions by 1 hour. The purpose of this delay is to ensure the code is functioning as expected and if somewhere in the code a transfer is initiated incorrectly, we may have time as a DAC to fix it before the DAC loses funds inappropriately.
The main funds of the DAC are held in the eosdacthedac account which is again controlled by dacauthority and also has the same timed-delay xfer permission.
The code we're still working on includes functionality to help custodians approve multi-signature proposals on chain through our member client. We're also building out a full worker proposal system which will facilitate all the work the DAC is doing.
As we continue to build and refine our process for running DACs on the EOSIO software, we'll also continue to explore our DAC Chain Initiative so these core DAC functionalities will be available to future DACs as system-level contracts on the DAC Chain.
As always, we welcome any and all feedback and encourage you to join our community on discord: http://discord.io/eosdac
Thank you again for your encouragement and support as we've worked to reach this milestone.
Now get out there and vote for some eosDAC candidates! :) http://members.eosdac.io
Please vote for eosdacserver
Join our newsletter to stay informed and follow us on your favorite social media platform: