Please vote for us, we need your support to continue offering such tools and services!

Should EOS tokens sent to eosio.ramfee and eosio.names accounts in the future be allocated to REX?

rex4all by eosreferenda 12-May-2019 00:00:00 UTC referendum-v1

Poll status

22,967,355 EOS voted
Vote

You voted {{(lastVote==1)?'YES':'NO'}}  

{{votingResponse.message}}

Post a public comment (optional)

Select Yes/No to cast your vote and make your comment public on the EOS blockchain. Your comment and vote will be recorded on-chain for ever, if you want to change your comment please vote again and our algorithm will attempt to just show your latest comment.

Account
{{ webdigiWallet.account.account_name}}

  • 1474 accounts
  • 38 days since poll started
  • 2.2% participation
  • 98% YES lead over NO

Question

Should future EOS tokens sent to eosio.ramfee and eosio.names accounts be allocated to REX?

Method

To do this, the Block Producers will have to set CHANNEL_RAM_AND_NAMEBID_FEES_TO_REX = 1 (https://github.com/EOSIO/eosio.contracts/blob/44d53447e04cb9fc32e1a73aacb7119511363a29/contracts/eosio.system/include/eosio.system/eosio.system.hpp#L23)

Background Information

The EOS Resource Exchange (REX) enables token holders to lend/borrow CPU and NET resources. One of the features of REX is that it can also distribute EOS fees paid into system accounts, eosio.ramfee and eosio.names, on top of the fees paid by those borrowing the resources.

  • eosio.ramfee account: This account holds the 0.5% fee paid for all RAM purchases and sales on EOS.
  • eosio.names account: This account holds all EOS paid for short names (e.g. ".eos") each day in the shortname auction

Original Announcement of REX from Dan Larimer: https://medium.com/@bytemaster/proposal-for-eos-resource-renting-rent-distribution-9afe8fb3883a

Additional notes

The addition of these funds would not increase inflation nor effect the 4% inflation allocated to the eosio.saving. The current funds in both accounts in question would not be touched, only future tokens that enter the accounts would be reallocated into REX.





Time Frame:








13 Comments

These comments were made along with their vote

Sort by...

Related Polls

POLL AT 1.37%
Referendum

Should the EOS mainnet establish the EOS Commons Development Program as outlined in this referendum?

EOS COMMONS DEVELOPMENT FUND PROGRAM (AKA PLATFORM DEVELOPMENT FUND, AKA WORKER PROPOSAL SYSTEM, AKA WPS) Proposers Anand, Gautam Buck, Justin Espinoza, Branden Karaivanov, Todor Kauffman, Josh Lee Kiho Kim Naeun Ma Larry Mao Yifeng Margulies, David Pahalahti, Samuli Pollard, Chris Seo, Leo Shi, Ricky Describe Initiative / 提案描述 / 제안 요약 This proposal is to fund a 6-month bootstrap stage EOS Commons Development Fund System. / 本提案旨在资助为期6个月的启动阶段的EOS公共发展基金系统。/ 이 제안은 6개월간의 EOS 공동 개발 펀드 시스템 부트스트랩 단계를 위한 것입니다. Our goal is to create a mechanism to fund a portion of the innovation and advancement of the EOS network, and do so in a transparent manner, utilizing community-directed funds, while addressing and reducing the risks of systemic fraud. / 本提案旨在资助为期6个月的启动阶段的EOS公共发展基金系统。我们的目标是建立一个机制,以透明的方式资助EOS网络的创新和发展,利用社区导向的资金,同时消除系统性欺诈的风险。/ 우리의 목표는 EOS 네트워크의 혁신과 진보를 위한 펀드를 제공하는 메커니즘을 만듭니다. 그리고 이를 위한 투명한 방법과 커뮤니티 규제 하의 펀드 운용을 통해 체계적인 사기를 대처하고 미연에 방지합니다. The Official language of this Referendum will be English: all efforts have been made to translate accurately to other languages for ease of understanding, but English is the prevailing language in case of dispute. / 本次公投的官方语言将是英语:为了方便理解,我们已尽力准确地翻译成其他语言,但在发生争议时,以英语为主。/ 국민 투표의 공식 언어는 영어가 될 것입니다. 물론 쉬운 이해를 돕기 위한 노력으로, 다른 언어로의 명확한 번역이 이루어질 것이지만, 주요 언어는 영어일 예정입니다. 中文译本: https://tinyurl.com/ybthxm99 한국어 번역판: http://bit.ly/wg_eos As other language translations become available they will be shared on http://bit.ly/working_group. Ongoing discussions concerning this Proposal will take place on Telegram: https://t.me/eosio_wps. State Question Should the EOS mainnet establish the EOS Commons Development Program as outlined in this referendum? Yes, I vote to establish the EOS Commons Development Program. No, I vote to reject the EOS Commons Development Program. Interpretive Statement (What a Yes Vote Will Do) The proposal includes: 1. Transfer of Funds. Top 21 Block Producers transfer 1 million EOS tokens from the eosio.saving account to a newly created eosio.wps account. The purpose of this amount is to fund the EOS Commons Development Program activities for six months. [See Section 7 below for more details on eosio.saving.] 2. Initial Allocation The first allocation of funding will be immediate and will include funding for Emergency Committee Operations EOS Commons Development Program portal development and management The balance of the initial allocation of 1MM tokens will be held under custody of the Emergency Committee, to be disbursed if, and only if, the community has approved other proposals for funding by the EOS Commons Development Program (as outlined in Article XI of the Constitution). 3. Emergency Committee Operation. Establish the Emergency Committee to filter and oversee proposals that go to community vote, oversee the progress of proposals, oversee the use of funds, report Emergency Committee findings back to the community periodically, and assist in the preparation of governance proposals for EOS Commons Development Program Categories. Requested EOS on 20190112: ($68,943.72/$2.44) + 84 = EOS 28,339.623 Slate of nominees: http://bit.ly/slateofnominees Updated Budget and proposal links: (proposal) http://bit.ly/committee_proposal (budget) http://bit.ly/committee_budget Emergency Committee Emergency Proposal Assessment Overview: http://bit.ly/EmCom_assessment 4. EOS Commons Development Program Portal Development and Management. Portal Development to support the growth of EOS Ecosystem by developing the software and platform for the community to review, discuss, select, fund, and hold accountable projects proposed by community members to benefit EOS; includes the following: Smart contracts for registration, submission, proposal review, and voting. Web platform for registration, submission, forum and voting. Software that incorporates the needs of new categories as they come online. Secure infrastructure to deploy the platform. Requested EOS on 20190112: ($378,420.00/$2.44) + eos750 = EOS 155,840.164 Updated Budget and proposal links: (proposal) http://bit.ly/portalDev_proposal (budget) http://bit.ly/portalDev_budget Preliminary github http://bit.ly/github_draft 5. Recognition of EOS Commons Development Program Categories The EOS Commons Development Program categories are established and recognised for future development to allow for the greatest variety of governance options to figure out what works best, while limiting scope for abuse or failure: Oversight -- intended for portal maintenance, quality control, and oversight of other categories, as well as supporting any proposals that go through direct referenda instead of one of the EOS Commons Development Program Categories. Infrastructure -- for supporting the underlying code base of the blockchain. Examples include security audits, bug patches, and code repository maintenance Community -- includes meetups, educational content and platforms, public relations, lawyers, advocates and lobbyists. Development -- for supporting developers and ideas. Miscellaneous -- for any proposal which may not fit directly into any of the other categories. 6. Open Call for Governance Design Proposals for Individual Categories. The Emergency Committee will manage a competition for individual category governance structure designs to allow experimentation with governance without risk to the whole ecosystem: The governance structure for each category is up to worker proposals submitted by the community. Winning Designs are those chosen by community vote. As each category is approved by the community, the category in question becomes active. To become an activated category, the winning submission will be chosen as the one with the highest participation of voting tokens, with no less than 5% of total currency supply, and must maintain no less than 55% Yes votes of the total voting supply, maintained for no less than 15 consecutive days within a period of 60 days. Each active category will be limited to its own financial boundaries,(i.e., 10% of eosio.saving) to limit abuse and waste, and to allow room for future growth if and when token holders decide on it. (See Section 7.) When a category goes live, the Emergency Committee surrenders control over relevant proposals. Over time, the Emergency Committee ceases to exist as its duties are absorbed. 7. Retire the Remaining Balance of eosio.saving. Until such time as there is community confidence in the various government structures, we propose a recurring retirement of all funds in eosio.saving not allocated to eosio.wps: On day 1, after the initial 1 million EOS tokens are moved to the eosio.wps account: Remainder in eosio.saving will be retired; and, eosio.saving will continue being retired monthly, as it accumulates. Once the Categories have been properly established: 10% of the tokens flowing into eosio.saving per approved Category will be distributed into eosio.wps. Full description: http://bit.ly/eosiosaving_burn (NB, external document reflects a previous intention to bundle ECAF and Mainnet Repository Maintenance that is no longer planned. For transparency we will not edit already published documents unless required for accuracy.) Block Producer Instructions Create a multisig proposal to create an account named eosio.wps with 10 EOS staked for Network bandwidth and 100 EOS staked for CPU bandwidth and 1500000 bytes of RAM Create eosio.wps account structure with owner permission designated to [email protected] and the active permission set up as a 4 of 7 multisig, with keys provided by the 7 members of the EmCom. Create a multisig proposal to transfer 1 million EOS from eosio.saving to eosio.wps Create a multisig proposal to retire the remaining balance of eosio.saving after the transfer of 1 million tokens has been executed Every 30 days following, a new multisig proposal shall be put forward by the EmCom to retire the unallocated funds within eosio.saving Arguments Summary Arguments In Favor EOS requires support and development and funds have been set aside for this purpose. CDF is a safe and secure way to bootstrap this support system. Public goods should be funded by the commons. Decentralization and separation of powers requires an independent CDF. Summary Arguments Against EOS Inflation is too high at 5%; no development or support is needed so inflation should be reduced to BP rewards. A Commons Development Fund to handle development is a central bureaucracy; instead the money and duties should be trusted to the Block Producers. DPoS does not work; Whales would use a fund like this to just vote themselves money. To read full arguments, both for and against, including rebuttals, please go to: http://bit.ly/argument_rebuttals Supporting Documentation GitHub: http://bit.ly/wps_portal and http://bit.ly/wps_backend Hash of GitHub, latest commit: 5ea8f491efa11fb07acc8d51eff04fbcdef69a69 (portal) and 053fb79b86d9909fa160b84a4ce7f234a4932fed (backend) Hash of Ricardians latest commit: d120e212bdcd03039037a0a0c76daca5c9c3a350 Ricardian Contracts: http://bit.ly/contracts_abi

14,177,474 EOS voted 25.1%74.9%