bDIP Standard

Tags

Related to:

Owner

Created Date

Mar 31, 2022

Last Updated

Apr 12, 2022

Problem Statement

The GSE board needs to be able to work together in a way that leverages both our individual knowledge, experience, interest, and collective influence.

Our DAO governance system needs to be updated incrementally and compartmentally making specific changes to specific areas at a time.

The DAOs governance self-improvement system should be a system that continues to exist independently and in the absence of any particular GSE board or GSE role holder.

Our current governance cycle seem low compared to other similarly aged DAOs

Proposed Solution

The introduction of the BanklessDAO Improvement Proposal (bDIP) Standard. It’s a mechanism to introduce incremental changes and improvements to the DAOs operated system. A sibling to the DAOs grants application system, it’s a template for DAO OS upgrades and patches. 

The language of “improvement proposal” is intentionally being taken from Ethereum Improvement Proposals (EIPs) and other similar language used to describe proposals for blockchain protocol upgrades. Many will be most familiar with the famous EIP-1559 that introduced Ethereum's deflationary mechanics. Numerous other DAOs have adopted a similar proposal scheme. 

Like any living and growing system, there must be a path for self-improvement and experimentation. bDIPs would represent bDAOs mechanism for such change. The idea is to strongly draw upon this pattern that has proven to be effective in protocol governance. Any deeper insight into that process will prove valuable as we apply it in the layer zero context. 

Submission Candidates

Anyone in the bDAO *community can submit a bDIP and the community must ratify all bDIPs through the existing governance pipeline. Right now, this means x% approval on the community forum and then final approval on Snapshot. 

Role of GSE Board

The GSE board are individuals entrusted to identify, create, review, research, and comment on bDIPs. While a GSEs individual approval or disapproval of any particular bDIP holds no greater technical weight than other bDAO community members, their expertise, familiarity, and informal influence in the community may prove to have great informal weight. 

Every value-generating system must identify its primary units of value and engineer around the efficient production of those units. The bDIP standard would be the GSE’s primary unit of delivery. bDIPs should be GSE’s bread and butter. All workshops, working groups, and research initiatives would serve to create and implement these proposals. 

Each GSE has their own mindset and individual creative bandwidth. The improvement proposal allows for greater individual autonomy and creative freedom while not sacrificing team strength. 

This would mean revolving the GSE kanban board around the creation and evolution of these proposals through successive levels of maturity. A theoretical workflow could be:

Idea (Backlog) → Draft (Rough outline of the problem statement and possible solution set) → Research (Working group, Feedback, Research) → Review (GSE endorsement listed) → Forum → Snapshot

Create a public submission form that allows anyone to submit proposals to be added to the GSE kanban board backlog providing a means for the community to voice concerns and request the GSE board for attention. It also acts as a window for research groups’ feedback on their findings to the GSE board. This also serves to prevent duplication of efforts if other groups are traveling down certain paths. 

Next Steps

Create the first bDIP (bDIP-0) that consists of this very specification. (Draft)

Solicit a group of trusted advisors to review and offer feedback on this spec. (Research)

List each GSEs endorsement or lack of on the final proposal. (Review)

Post to the Community Forum. (Forum)

This would also represent the very first official action taken by the GSE board. An action that is more in line with building a system that builds a system rather than any particular governance action. 

Strategy

Write a checkpoint calendar with seasonal length in mind.

Write DAO handbook as the starting point of the bDIP standard. Each new IP creates a new version of the manual that follows a semantic versioning (semver) naming convention. This can be written in markdown and eventually controlled by radicle.

The dip standard with allows the community to validate the first edition and stipulate the mechanism for future revisions.

Notes from previous meeting (April 12): 

Decided to break apart the improvement proposal process from creating the initial handbook.

bDIP-1

The BanklessDAO Governance Improvement Proposal Framework

Purpose: The purpose of this first governance improvement proposal is to introduce a format for transparent and efficient changes to our community governance system. It will do this by introducing a DAO handbook. This handbook will be regularly updated to include changes to our processes and procedures. Each new version of the handbook with indicate its version using a semantic versioning system and publication date. Links to previous versions with available diffs will also be readily available.

Will list the structures and processes of the DAO.

Will not list specific entity names and members and will try to be somewhat tool agnostic.

Baseline on Strategy, Org, and Ops.

Explicitly no announcement on how this document is updated.

Manual now, IP process later.

Manual implemented in the onboarding process. (Plan for existing members. Director Education.) Director education is the key as we all (community members) find ourselves in the director's chair.

Include the strategy statement?

How do we include dissent? (mechanisms for this)

Can it be worse than what we have now?

Can we gate this process to GSEs as stewards of IPs? (GSE is similar to GC)

What does it take to be an IP proposer?

Some changes can come from the community

*Anyone in the community that meets a minimum leveled threshold. This may mean only L2’s and above can submit new bDIPs for consideration. 

bDIP Standard

Tags

Related to:

Owner

Created Date

Mar 31, 2022

Last Updated

Apr 12, 2022

Problem Statement

The GSE board needs to be able to work together in a way that leverages both our individual knowledge, experience, interest, and collective influence.

Our DAO governance system needs to be updated incrementally and compartmentally making specific changes to specific areas at a time.

The DAOs governance self-improvement system should be a system that continues to exist independently and in the absence of any particular GSE board or GSE role holder.

Our current governance cycle seem low compared to other similarly aged DAOs

Proposed Solution

The introduction of the BanklessDAO Improvement Proposal (bDIP) Standard. It’s a mechanism to introduce incremental changes and improvements to the DAOs operated system. A sibling to the DAOs grants application system, it’s a template for DAO OS upgrades and patches. 

The language of “improvement proposal” is intentionally being taken from Ethereum Improvement Proposals (EIPs) and other similar language used to describe proposals for blockchain protocol upgrades. Many will be most familiar with the famous EIP-1559 that introduced Ethereum's deflationary mechanics. Numerous other DAOs have adopted a similar proposal scheme. 

Like any living and growing system, there must be a path for self-improvement and experimentation. bDIPs would represent bDAOs mechanism for such change. The idea is to strongly draw upon this pattern that has proven to be effective in protocol governance. Any deeper insight into that process will prove valuable as we apply it in the layer zero context. 

Submission Candidates

Anyone in the bDAO *community can submit a bDIP and the community must ratify all bDIPs through the existing governance pipeline. Right now, this means x% approval on the community forum and then final approval on Snapshot. 

Role of GSE Board

The GSE board are individuals entrusted to identify, create, review, research, and comment on bDIPs. While a GSEs individual approval or disapproval of any particular bDIP holds no greater technical weight than other bDAO community members, their expertise, familiarity, and informal influence in the community may prove to have great informal weight. 

Every value-generating system must identify its primary units of value and engineer around the efficient production of those units. The bDIP standard would be the GSE’s primary unit of delivery. bDIPs should be GSE’s bread and butter. All workshops, working groups, and research initiatives would serve to create and implement these proposals. 

Each GSE has their own mindset and individual creative bandwidth. The improvement proposal allows for greater individual autonomy and creative freedom while not sacrificing team strength. 

This would mean revolving the GSE kanban board around the creation and evolution of these proposals through successive levels of maturity. A theoretical workflow could be:

Idea (Backlog) → Draft (Rough outline of the problem statement and possible solution set) → Research (Working group, Feedback, Research) → Review (GSE endorsement listed) → Forum → Snapshot

Create a public submission form that allows anyone to submit proposals to be added to the GSE kanban board backlog providing a means for the community to voice concerns and request the GSE board for attention. It also acts as a window for research groups’ feedback on their findings to the GSE board. This also serves to prevent duplication of efforts if other groups are traveling down certain paths. 

Next Steps

Create the first bDIP (bDIP-0) that consists of this very specification. (Draft)

Solicit a group of trusted advisors to review and offer feedback on this spec. (Research)

List each GSEs endorsement or lack of on the final proposal. (Review)

Post to the Community Forum. (Forum)

This would also represent the very first official action taken by the GSE board. An action that is more in line with building a system that builds a system rather than any particular governance action. 

Strategy

Write a checkpoint calendar with seasonal length in mind.

Write DAO handbook as the starting point of the bDIP standard. Each new IP creates a new version of the manual that follows a semantic versioning (semver) naming convention. This can be written in markdown and eventually controlled by radicle.

The dip standard with allows the community to validate the first edition and stipulate the mechanism for future revisions.

Notes from previous meeting (April 12): 

Decided to break apart the improvement proposal process from creating the initial handbook.

bDIP-1

The BanklessDAO Governance Improvement Proposal Framework

Purpose: The purpose of this first governance improvement proposal is to introduce a format for transparent and efficient changes to our community governance system. It will do this by introducing a DAO handbook. This handbook will be regularly updated to include changes to our processes and procedures. Each new version of the handbook with indicate its version using a semantic versioning system and publication date. Links to previous versions with available diffs will also be readily available.

Will list the structures and processes of the DAO.

Will not list specific entity names and members and will try to be somewhat tool agnostic.

Baseline on Strategy, Org, and Ops.

Explicitly no announcement on how this document is updated.

Manual now, IP process later.

Manual implemented in the onboarding process. (Plan for existing members. Director Education.) Director education is the key as we all (community members) find ourselves in the director's chair.

Include the strategy statement?

How do we include dissent? (mechanisms for this)

Can it be worse than what we have now?

Can we gate this process to GSEs as stewards of IPs? (GSE is similar to GC)

What does it take to be an IP proposer?

Some changes can come from the community

*Anyone in the community that meets a minimum leveled threshold. This may mean only L2’s and above can submit new bDIPs for consideration. 