0x289d3b1b…1489sent to0xdbd38f7e…0e0c·#18,762,443·view on Etherscan
# DIP-76(a) DAO Accounts Consolidation
**Summary:**
With DopeLabs up and running bringing structure to DOPE DAO now is the time to move ownership of our communications and tech platforms away from their centralised position and into the decentralised structure we have created. The intent is to take the possession or custody of the platforms and accounts away from individual Member responsibility and place them within the custody of the DopeLabs structure in a way that best protects against single points of failure. To create a system, as best as we currently can, that makes our DAO protocols as strong and durable as possible. The key is that the DAO should survive and be functional independent of any individual actions, inactions and/or personal events etc. The accounts in question are detailed below.
**How:**
Overall the method will be to transfer the base email for the accounts away from personal Member emails and to @dopewars.gg email account that will be officially controlled by the Operations Core Unit but accessible by each of the Core Unit Members. The move away from singular access will prevent system failure should anything unforeseen happen to any individual Member. It will also route custody of the communication and tech accounts in an Official DOPE DAO email account, these are then part of the DopeLabs structure. As we know DopeLabs Members will be elected through DAO vote, the structure stays extant as Members come and go filling positions that need to be filled. With this being the foundation principle there are slight differences between some of the platforms.
***
**Discord:**
Current server owner: Dennison Bertram Proposed: 2FA held by the Operations Unit Considerations: A cold account to be provisioned and kept offline on a separate device. Only to be used in emergencies. All existing roles and structures will be audited and lowest privileges will be granted to ensure a compromised “elevated” account can do minimal damage.
***
**Telegram:** Current account owner: 2FA held by the Operations Unit Proposed: No change Considerations: The ownership rights can be transferred to a new administrator if/when the Operations Manager is changed. The fail safe mechanism is if the owner account becomes inactive for 3 months it will be automatically deleted by Telegram and the Ownership Rights for the Official Group and Portal Group will be transferred to the next admin in the hierarchy. In this instance it will be set to transfer to the Operations Capo, following that the Diffusion Don.
***
**Google Suite and Cloud** Current: Faces Proposed: 2FA held by Operations and Engineering Unit
Considerations: Currently billed to Faces credit card and reimbursed by the DAO. Upon receipt of the DAO credit card (DIP 77), this will be used for billing. The workspace and cloud management will be joint by the Operations and Engineering unit.
***
**Dopewars.gg Domain:**
Current: Faces Proposed: 2FA held by Protocol Unit
Considerations: Currently billed to Faces credit card and reimbursed by the DAO. Upon receipt of the DAO credit card (DIP 77), this will be used for billing.
***
**Alchemy:** Current: Faces Proposed: 2FA held by Engineering Unit.
Considerations: Currently billed to Faces credit card and reimbursed by the DAO. Upon receipt of the DAO credit card (DIP 77), this will be used for billing.
***
**Figma:** Current: Faces \*\*\*\*Proposed: 2FA held by Engineering Unit.
Considerations: Currently billed to Faces credit card and reimbursed by the DAO. Upon receipt of the DAO credit card (DIP 77), this will be used for billing.
***
**Vercel:** Current: Faces \*\*\*\*Proposed: 2FA held by Engineering Unit.
Considerations: Currently billed to Faces credit card and reimbursed by the DAO. Upon receipt of the DAO credit card (DIP 77), this will be used for billing.
***
**Notion:**
Current: Faces Proposed: 2FA by the Operations Unit
Considerations: Currently billed to Faces credit card and reimbursed by the DAO. Upon receipt of the DAO credit card (DIP 77), this will be used for billing. Additional Workspace members to be assigned to other DopeLabs core units to manage guest access to pages for collaboration
***
**GitHub:** Current admin: dennison, perama, rafael and tarrence Proposed: Tarrence and a Cold account for ownership access.
Considerations: Account contact email to be changed from <dopewarsdao@protonmail.com> to an @dopewars.gg address. Tarrence Van Eva, as a doxed individual active in the crypto ecosystem, and a founder of DOPE, plus a cold account as a redundancy to hold owner access to GitHub.
Additional teams within the org to be created,
one for the Engineering Unit to be able to review, push directly onto master (hot hotfixes only), approve PRs, manage repositories (permissions/members/teams) etc.
One for Contributors with ability to do PRs.
***
**Security Protocols:**
We have to create a method until such time as DAO tools are built to plug these gaps, if we leave the accounts in control on single Members then we expose the DAO to the risk that we lose our Communications and Tech platforms altogether. But the requirement to have access by multiple Members brings risk. A core email address @dopewars.gg will be in the official custody of the Operations Manager as elected by the DAO. Each member of DopeLabs will have password access to this email address and will be required to both keep the password secure and forbidden to share access with any other person. In the event of new members being elected to DopeLabs or if a Member steps down or is removed from DopeLabs then the password will be changed.
<https://snapshot.org/#/dopedao.eth/proposal/0xd8a51edcfd0f46214f9e18aaee210097fdf8819d799b385cc4a1b7316ffc8437>