Prop4: Participation Agreement

A vote of "yes" accepts all 4 of these changes. A vote "no" votes against accepting these 4 changes.

1.) Please review the section titled OG DAO Agreement Terminology located in the section after this list. This vote is not to opt-in or out but to agree to the terms. After this proposal has been passed Members Stinky and SwaHili will donate their time to code the DAO’s new dApp. The dApp will allow members to interact with the contract through a user-friendly webpage. Please review screenshots further down this proposal, from an early prototype.

A section has been added by member Stinky with data on what it costs to deploy the smart contract on the Rinkeby Testnet. These numbers are just an estimate of what it could cost to deploy on the Ethereum Mainnet. We will do our best to time deployment for gas cost efficiency.

2.) The newly formed OG DAO will update their consensus voting. Members who do not opt-in, will not lose voting power. The DAO however, will assume they are inactive, we need adjustments to the consensus on snapshot proposals. In order to pass any proposal after our agreement contract has gone live, you will need to receive 51% of the votes for all opt-in addresses. This will solve the DAO’s participation problem.

3.) The DAO will also like to achieve consensus on our name. A vote in favor of this proposal also makes the official name of the DAO: OG DAO. This clears up the naming confusion between EBOG DAO and OG DAO.

4.) The DAO would like to update their logo to something friendlier to design around. Please review the images for the proposed new logo.

                         Agreement Terms
Please read this participation "agreement" carefully before confirming your intent to be bound by it and participating in the OG DAO. This agreement includes the terms of participation in the OG DAO. You understand, agree, and confirm that:

The OG DAO is an experiment in the field of decentralized governance structures, in which participation is entirely at your own risk.
This agreement has legal consequences and by entering into this agreement you release all rights, claims, or other causes of action whether in equity or law you may have against OG DAO service providers or other OG DAO participants. You also agree to waive and limit any potential liability of OG DAO service providers or other OG DAO participants.
You are sophisticated and have a sufficient technical understanding of the functionality, usage, storage, transmission mechanisms, and intricacies associated with cryptographic tokens, token storage facilities (including wallets), blockchain technology, and blockchain-based software systems.
There are 2 options:
I, the owner of this address, Opt-out completely from the OG DAO.
I, the owner of this address, Opt-in to the OG DAO. I have read and agreed to the participation agreement below.

If you do not opt-in or out, you are still a member of the OG DAO. You still have the same voting power, however, you will not receive airdrops, payments, or other benefits. This is to protect the OG DAO, its members, and its assets.

Explainer Video:

Logo: Screenshot: Gas Estimation for Deployment: These numbers are only estimates based on deployments to the Rinkeby network. This does not guarantee the price to deploy will be the same on Mainnet. The cost could be lower or higher when deployed to Mainnet. A goal for the deployment team will be to time it as best as possible to save the DAO as much ETH as possible.

Deploying Terms and Agreement Contract: contract deployment at 38 gwei, 0.11 ETH.

Adding 775 members to Contract Function call at 38gwei, cost 0.77 ETH The contract only allows members to call it, in order to add members we have to call the addMembers function. This is a modified function from Open Zeppelins addMember. It allows us to pass an array of addresses once vs. calling the function 775 times. This saves the DAO on gas fees.

After this, the contract is fully operational for all 775 members to call. Opt-in and Opt-out functions will cost some gas to call, at the cost of the member calling it. This contract also gives us the ability to return an array of opt-in and opt-out addresses. The DAO can vote to turn on and off the opt-in ability, with a function call.