| | "DAPP Network Governance Bootstrap"
| "We are proud to introduce a community governance that will further decentralize the DAPP Network by distributing the keyholders and decision-makers, making it a truly immortal, open protocol that can continue to evolve in many ways, with the community at the helm.\n\nThe proposal system is at the core of DAPP Network governance. Anyone can submit a proposal and all DAPP token holders are able to vote on it.\n\nThe detailed model can be found here:\nhttps://medium.com/the-liquidapps-blog/introducing-dapp-network-governance-model-b90541ac7682\n\nThis is a governance bootstrap proposal that should be approved by the community. It will be followed by DAPP Network Guardians candidates in a separate proposal\n\nThe code for the DAPP Network Governance can be found here\nhttps://github.com/liquidapps-io/dappgovernance"
| "https://medium.com/the-liquidapps-blog/introducing-dapp-network-governance-model-b90541ac7682"
| | | | | | | | |
| | "Change DAPP max supply from 20 billions to dynamic supply"
| "Currently the maximum supply of DAPP tokens is 20 billions. \nThe purpose of this proposal is to change the supply parameter to dynamic so that it will mirror the circulating supply at every block."
| | | | | | | | | |
| | "Allow staked DAPP tokens to vote in DAPP governance"
| "Currently one needs to UN-stake DAPP tokens in order to vote on dappgovernance. This is counterproductive. \n\nAllowing tokens to be staked and also vote in governance is more beneficial, as it would encourage staking instead of discouraging staking.\n\nMake it so staked DAPP tokens can also vote in governance."
| | | | | | | | | |
| | "Vote \"Yes\" to approve the proposed 21 genesis DAPP Network Guardians!"
| "It has only been a week since the DAPP Network Governance Model was announced, and the community is buzzing with excitement! The brand new DAPP Governance Telegram channel is full of fascinating and infringing discussions, and three governance proposals have already been brought forward (with the first two already approved! ).\n\nFollowing the approval of the DAPP Network Governance Model by a recent community vote, it’s now up to the community to decide and vote upon one of its core elements - the MSIG of DAPP Network Guardians!\n\nAs stated in the DAPP Network Governance Model, \"The keys for the DAPPSERVICES smart contract will be held by an MSIG of DAPP Network Guardians, in charge of deploying and signing changes based on approved governance proposals passed by the DAPP Network community.\"\n\nIt is hereby proposed to appoint 21 genesis DAPP Network Guardians, that bring diverse expertise, experience, and skills to the table, across disciplines. \n\nAmong the proposed group are executives of reputable DSPs (Yves La-Rose, Raman Bindlish, Jason Kemp, Ross Dold and others), executives of leading EOS Block Producers (such as Roman Skaskiw and Igor Lins e Silva), DAPP token holders, veterans in the cryptography and blockchain startup ecosystem, along with some of the most prominent members of the DAPP Network community (including myself, Myra Wang & Pakkz) and members of the LiquidApps team. \n\nThe proposed accounts to be included in the MSIG of DAPP Network Guardians: \n\ncbrftbkrwwbo@active\ncodeguardian@active\ncryptolions1@gov\ndappnetworkk@active\ndappprovider@active\ndoobiegalnew@active\neospheredapp@active\neverythngeos@active\nigorlseosrio@guardian\nihaveadejavu@active\ninvestingwad@active\nkawrrsytrsbq@active\nkobybenaroya@active\nlarosenonaka@active\nmithrilalnce@active\nmwguardian12@active\nprjyzjtgxuku@active\ntalmuskaleos@active\nx452ifggq5va@active\nxhfq33vt3fg2@active\nzkwshzdsgdiv@active\n\nPlease note: The accounts are alphabetically ordered, so as not to be associated with any of the Guardians (although sometimes it is very clear who the account belongs to...)\n\nWhat are you waiting for? - Vote \"Yes\" to approve the proposed 21 DAPP Network Guardians!"
| | | | | | | | | |
| | "DAPP Network Guardians should not be anonymous"
| "As explained in the Proposal #0 description the DAPP Network Guardians play a significant role in safeguarding the DAPP ecosystem and its vital interests. They will hold a MSIG over the dappservices smart contract which comes with the power to change ANYTHING in the smart contract and also to veto approved proposals if they deem it being harmful for the DAPP Network. When choosing the Guardians we are trusting them to each individually follow the governance process and to not abuse their power.\n\nIn Proposal #3 only 12 out of the 21 candidates for Guardians have been publicly identified. The rest wish to stay anonymous. Even if these people are vetted by LiquidApps and therefore probably trustworthy I find this a poor foundation for the emerging governance system. For the sake of example consider a supreme court of 21 judges. They are all required to follow the law and interpret it in their best ability but collectively they can change the law. Half of these judges appear to the court room with a Guy Fawkes mask and refuse to tell anything about themselves. Would you trust this court?\n\nThe amount of 21 Guardians was probably chosen for sufficient decentralization. However, I would rather trust this power to a smaller group of known and trusted entities than a bigger group including many anonymous entities. In theory I have no way to even verify that these anonymous accounts are not controlled by one entity.\n\nIndividual community members need to be able to 1) know that the Guardians are unique persons 2) verify that they are trustworthy and reputable 3) contact them in case the Network is being attacked. Therefore Guardians should at least have an online identity. A real name is not required as long as the conditions listed are met.\n\nIf this proposal gets approved after proposal #3 is approved the anonymous Guardians should be removed from the multisig. We can grow back to 21 Guardians over time through additional proposals as publicly identifiable good candidates are found.\n\nIf this proposal gets approved before proposal #3 then a new proposal should be made with no anonymous Guardian candidates.\n\nIf this proposal gets rejected then the community has voiced that it is fine to have anonymous guardians.\n"
| | | | | | | | | |
| | "Establish DAPP Governance Fund"
| "With the DAPP Network now being governed by its token holders, it is essential to empower the community with tools and mechanisms to ensure its continued growth and self sustainability. One of these tools is a dedicated Governance Fund. \n\nThis proposal is to seek consensus on whether or not the DAPP Network community would like to establish a DAPP Governance Fund (account: dappgovfund), which could be funded through a portion of the DAPP inflation and can be spent at the discretion of the DAPP Network community itself, through its governance system. The dappgovfund account is already under the DAPP Guardian MSIG (account: dappgovernor).\n\nIf DAPP Governance Fund is to be established, the community could propose to spend the DAPP tokens in its account to fund grants, bounties, worker proposals, impermanent loss protection, or other incentives that the community may wish to promote. \n\nBy approving this proposal, you indicate your wish to direct a portion of a portion of inflation towards such a fund. If approved, the amount of inflation to be used will be determined in a future proposal which will include additional changes to inflation as part of the planned liquidity mining incentive initiative that has been discussed in recent weeks."
| | | | | | | | | |
| | "Designate 0x0e14dd85e20af249e8182caf868f1a658e3aa2e9 Ethereum Contract as Official DAPP ERC20"
| "Vote YES for this proposal to accept the DAPP Account DAO bridge as the DAPP Network community’s choice for DAPP token interoperability between EOS and Ethereum and for 0x0e14dd85e20af249e8182caf868f1a658e3aa2e9 to be the official DAPP ERC20 token of the DAPP Network which will be used for liquidity mining and rewards on Ethereum.\n\nThe DAPP token will utilize the DAD Ethereum bridge contracts at ‘dadethbridge’ on EOS and 0xce9b04bE4e87548D34B8a2180b85310424c84518 on Ethereum, which will be used for sending DAPP bi-directionally cross-chain.\n\nVote NO if you do not want to adopt this bridge and token contract.\n\nDAPP ERC20 Token Contract\nhttps://etherscan.io/token/0x0e14dd85e20af249e8182caf868f1a658e3aa2e9 \n\nDAD ETH Bridge Contracts\nhttps://bloks.io/account/dadethbridge \nhttps://etherscan.io/token/0xce9b04bE4e87548D34B8a2180b85310424c84518 "
| "https://gateway.pinata.cloud/ipfs/QmTP731Sc83n5NSd9WbHDeS1825FvwzAVsDXRkFYC7UG17"
| | | | | | | | |
| | "Increase DAPP Network inflation to fund future liquidity incentives, IL Protection, and DAPP Governance initiatives"
| "Vote YES for this proposal to increase the DAPP inflation parameter to 15% and to initially split the DAPP emissions in the following proportions:\n\n2.71% - DSP staking\n12.29% - flows into dappgovfund1\n\nThe new inflation parameter will not have an immediate effect on DSP staking because its rate of inflation remains the same as it’s always been.\n\nThe inflation that is not being directed towards DSP staking will flow into the dappgovfund1 EOS account and will be under the direction and control of DAPP Network governance and its guardians. Any future usage of the funds in this account must first be approved through DAPP Network governance proposals.\n\nThe intention of this proposal is to initiate the immediate steps required prior to proposing liquidity incentives for DAPP LPs on Bancor and potentially other AMMs on Ethereum or other blockchains such as EOS, Binance Smart Chain, or Polkadot.\n\nThe majority of the DAPPs accumulated in dappgovfund1 prior to the mining initiatives launching are to be used as a backstop of reserve funds that may be used for providing impermanent loss protection insurance for DAPP LPs staking into a single sided token pool on Bancor. After the liquidity mining incentives begin, new inflation will be split up between mining rewards and a percentage of constant flow into the IL reserve. Specific percentages and amounts for liquidity incentives will be made in a separate proposal.\n\nThe funds in dappgovfund1 may also be used to fund governance led initiatives such as bounties or worker proposals."
| | | | | | | | | |
| | "Enable third party staking for DSP services while staked/locked into DAPP Governance"
| "Rich Text Formatted Proposal on IPFS: https://gateway.pinata.cloud/ipfs/Qmatn2QKS36uH8abhMsuLdVVr9upCwPafgE2Q6pzkR5VGz\n\nVote YES on this proposal to enable third party staking for DAPP tokens locked inside the DAPP Governance contract (dappgovernor). Integrate a new parameter that defines the % of total DAPPs locked in the governance vault which can be staked to DSP services. Default setting of the parameter will be 85%.\n\nVote NO on this proposal to NOT enable third party staking for DSP services via the DAPP Governance contract and to keep the governance vault the same as it is today.\n\n------\n\nThis proposal is to enable third party DSP staking that would allow end users to stake their DAPP tokens for DSP services after they’ve been deposited AND locked in the DAPP governance contract (dappgovernor). Third party staking should increase voter participation by significantly reducing the opportunity cost for participating in governance. \n\nThe rules for passing a DAPP Governance proposal require a voter majority with a minimum of 2% of the total DAPP supply AND 10% of the locked tokens in the governance vault to participate in the consensus/voting for a particular proposal.\n\nTo ensure that DAPPs locked in the governance vault do not sit dormant without participating in governance, and thereby make the 10% of locked token voting threshold very difficult to attain, a mechanism is needed to disincentivize such behavior. As a way to achieve this, this proposal suggests that 85% of a user’s locked DAPP tokens in the governance vault would be able to be staked to DSP services while maintaining their full vote weight. This mechanism ensures that there is a small cost to participating in governance so that users interested in earning maximum passive rewards without regular participation in governance will be incentivized to stake their tokens outside of the governance vault.\n\nWith this mechanism in place, if a user were to lock, for example, 100k DAPP tokens into the governance vault contact, then they would retain their voting power equal to 100k DAPP tokens but they would only have permissions to stake 85k of those DAPPs for DSP services via the third party staking mechanism.\n\nThird Party Staking Developer 100k DAPP Bounty\n\nTo enable third party staking with DAPP Governance, modifications to the ‘dappgovernor’ contract are required. As part of this proposal, a 100k DAPP bounty is to be offered for completing this work which will be funded by the ‘dappgovfund1’ account.\n\nIf a bounty submission is made, it will only be rewarded if it meets all of the requirements outlined below and is deployed into production by the DAPP Guardians.\n\nScope of Work / Features\nUsing the code samples below from the airhodl contracts below as a reference, integrate third party staking into the DAPP governance smart contract.\nAdd a new parameter that can be updated through a smart contract action that controls the total amount of locked DAPP that is stake-able via third party staking inside the governance vault. Default should be set at 85%.\n\nDAPP Governance Contract\nhttps://github.com/liquidapps-io/dappgovernance/tree/main/contract \n\nCode examples for third party staking from the airhodl contract can be found here:\nhttps://github.com/liquidapps-io/zeus-sdk/blob/master/boxes/groups/dapp-network/dapp-services/contracts/eos/dappservices/dappservices.cpp#L627\n\nhttps://github.com/liquidapps-io/zeus-sdk/blob/master/boxes/groups/economics/airhodl/contracts/eos/airhodl/airhodl.cpp#L194 "
| "https://gateway.pinata.cloud/ipfs/Qmatn2QKS36uH8abhMsuLdVVr9upCwPafgE2Q6pzkR5VGz"
| | | | | | | | |
| | "Amendment to Prop #6: 0x939B462ee3311f8926c047D2B576C389092b1649 Ethereum Contract as Official DAPP ERC20"
| "After passing Proposal #6 to designate 0x0e14dd85e20af249e8182caf868f1a658e3aa2e9 as the official ERC20 for the bridged DAPP token, the contract underwent an audit by the Bancor community, which provided several recommendations for compliance with Bancor's whitelisting guidelines. After reviewing the suggestions from the Bancor community, it was decided that the ERC20 contract would need to be refactored and then re-deployed, which requires a new token address due to the immutable nature of smart contracts on Ethereum. An updated DAPP ERC20 contract was deployed to 0x939B462ee3311f8926c047D2B576C389092b1649.\n\nVOTE 'YES' to this proposal to amend Proposal #6 to designate 0x939B462ee3311f8926c047D2B576C389092b1649 as the official DAPP ERC20 token which will be used for all liquidity mining initiatives and any future DAPP Network utility on Ethereum.\n"
| | | | | | | | | |
