Title: Audit of the Governance tools and procedures of BanklessDAO: Emergency Protocol
Draft Authors:
Working Group:
SUMMARY
TLDR;
The title of this post includes the words Emergency Protocol. Acknowledging that although this proposal, as all that have gone through the forum/have links to external google docs, Emergency Protocol was introduced as Appendix A, stating:
“APPENDIX A - Emergency Scenarios
An “Emergency Scenario” would refer to a proposal/motion that needs to fast track consensus and would likely consolidate power into the hands of a few for a short period of time, often the multisig signers 7. Examples could include:
- Liquidating positions due to black swan events
- Legal action against the DAO
- Smart contract hacks
- Immediate changes to governance (IE closing a governance loophole)
Emergency proposals would be titled with “Emergency Protocol” in the heading, which fast tracks soft and hard consensus by increasing quorum + voting requirements and removing all time requirements.
Since inception, BanklessDAO has used google docs to draft proposals and temp checks, the forum to gauge sentiment of and then vote on proposals and Snapshot to ratify the proposals.
All of these tools that have been used to ratify and store all proposals are able to be edited. Many proposals drafted on snapshot, have important details, specifications and implementations of the proposals linked via a google sheet. As you will see below, all of these methods have allowed our Governing Documents to be edited - During the voting period and after the results have been ratified.
The decision model at BanklessDAO is based with “quorum” being the deciding factor. There was the quorum removal vote, however, it always seemed no one really knew what quorum was and countless hours have been spent trying to figure it out.
The quorum removal vote was based on the proposal to ratify quorum itself didn’t meet quorum, however it didn’t have to.
These flaws in our governance system that either have led or could lead to our governance being corrupted.
There are also many other flaws within the systems, procedures, tooling, permissions, and has led to a build up of consolidated power, access and permissions, as you will see below.
BACKGROUND
Ratified Governance has been edited
The snapshot vote that ratified this Season 5 specification went live on July 29,2022 however the google doc that is linked in the Season 5 Specification Snapshot was edited 8/2/22, which was after the snapshot vote went live. It is important to note that we don’t know what was edited. It could have been as simple as adding a period to the end of the sentence. This can be seen in figures 1 and 2.
Forum pages have been deleted
The original BanklessDAO Wiki instructs to read more here about levels and roles within the DAO. This page has been deleted or is private.
The above demonstrates how 2 of the 3 methods that we use to store our Governance methods are accessible and editable and delectable. If we conducted an audit of our Governance docs, how many more documents would we find have been edited?
These documents and any documents that use either of these documenting and storage methods should all be considered void, as it has been proven that they have been edited. This either has led or could lead to our governance being corrupted. Almost every single snapshot vote is linked to a google doc.
All of BanklessDAO’s documentation is fragmented
Our governance documents have been so fragmented, that hours of research is needed to determine what has previously been put into place. We have seen above and the detrimental effects links within documents have caused to all of the documents that govern BanklessDAO. This also extends to the BanklessDAO notion.
The forum post Decentralization of Notion permissions This proposed model will decentralize Notion permissions by re-ordering the underlying page structure, groups, and permissions.
It gave minimal background information about the Bankless DAO Notion workspace being hacked. Other than:
“The hacker changed the content on the Mission, Vision and Values 23, and more concerning, the bank token address on the Gnosis Safe CSV Airdrop How-To 7 document.
Notion security hasn’t been a priority, so there isn’t a DAO-wide policy yet. Notion includes some tools to help us solve this issue, including groups, pages, page groups, and permissions.”
So we consolidated the power via administrative permissions. These permissions consolidated even more after upgrading the Notion package to have the ability to see what changes have been made to pages, and by who. What we are not able to see now are the tremendous amounts of deleted pages and who the pages were deleted by.
Such as the (L2): 35,000 BANK + Nomination/Vote process.
Or the member page or the this page.
Important information has been lost, like Guilds should have been adhering to KPI’s and filling out a budget request form, as seen in this proposal template or the funding template that voting to reduce the BANK minimum to join here and here. Incorrect Gnosis safe addresses are listed.
There is a project page and a project repo page. The project repo does not connect to the project pages as it should/did
Shouldn’t we have an overview of what has been funded? To see what has worked and what hasn’t.
Here is an overview of some important permissions along with relevant current initiatives being worked on.
Fragmenting vital records affects the treasury.
BANK-ETH SLP Bond
Fractured information could be the cause of the treasury reports only being on the eth chain.
With deleted and edited pages, we miss LP pools of the DAO such as the 80/20 balancer pool on polygon that holds 454,853 20 WETH 80 BANK, 80/20 Balancer pool on eth, BANK-ETH slp Bond or the How many other token swaps from other DAOs, Pools
Uploading: 2D6779F6-75EE-4CCA-AA46-519BA085844B.jpeg…
Fragmenting the notion seems to have also omitted proposals like the forefront Treasury Diversification Proposal that allocated 1,000,000 tokens seen here
Or the partnerships established with FTW DAO, HumanDAO or the many others.
Draft 3 of Firming up Governance noting below is a table for quorum. Numbers are a weighted average of the results from the previous vote. Each season, quorum & voting requirements can be updated as part of the Seasonal Specwas ratified in this snapshot vote. The vote itself did not have to meet quorum, as this was the vote to set quorum.
Permissions of our discord are also numerous and questionable. L2’s should be able to have
access to discord permissions and the ability to create categories and whatever this deleted page should say.
Right now, collab.land in the #collabland-join channel isn’t working correctly. There are no clear answers as to why. [image]
If you notice the title of this post includes the words Emergency Protocol. Acknowledging that although this proposal, as all that have gone through the forum/have links to external google docs, Emergency Protocol was introduced as Appendix A, stating:
“APPENDIX A - Emergency Scenarios
An “Emergency Scenario” would refer to a proposal/motion that needs to fast track consensus and would likely consolidate power into the hands of a few for a short period of time, often the multisig signers 7. Examples could include:
- Liquidating positions due to black swan events
- Legal action against the DAO
- Smart contract hacks
- Immediate changes to governance (IE closing a governance loophole)
Emergency proposals would be titled with “Emergency Protocol” in the heading, which fast tracks soft and hard consensus by increasing quorum + voting requirements and removing all time requirements.
We have just seen how all of our internal documents and governing documents have been compromised and should be considered invalid. We have no choice but to start over,
We need new Governance Documents, we need them stored in a manner so they are not able to be edited, but can have portions altered when a vote has indicated to do so.
We need documentation of our processes and administrative control over our community, our work and our treasury spread.
There is a proposal currently on snapshot to switch multisig holders after 18 months with no change or issues.
4 months ago, the Coordinape administrator for the DAO admitted to altering records.
Everyone has different values, based on their background. We all should value the BANK token however. We should also portray the Bankless name with credibility, honesty and integrity.
Choose integrity.
SPECIFICATION
| Current Form | Proposal |
|---|---|
| Remove | Unclear at this time /or see Grants Committee…. |
EXPECTED IMPACT
This emergency protocol proposal seeks to pause any current snapshot and forum votes, clarify the status of our governance documentation, provide a timeline for interim governance documents, and provide clarity over the multisig.
ANALYTICS
Unclear at this time
NEXT STEPS
initiate emergency protocol
WORKING GROUP BACKGROUND
There was no working group I did this on my own. This was due to the vote on snapshot to change the multisig signers.
But as far as I can tell there is no crisis, no emergency, and nothing presented, when combined, rises to the level of something that, as