Title – High Council x Arbitrum Launch Non-Constitutional Proposer: simona.eth Authors & reviewers: simona.eth bhuptani.eth charlesstlouis.eth alim.eth osumi.eth charlesstlouis.eth hatsprotocol.eth villanuevawill.eth
TL;DR
This proposal looks at the potential of a High Council partnership with Arbitrum to advance decentralized collaboration and governance. Working with the Arbitrum community, the High Council can provide a decentralized governance rollup enabling teams to share resources and develop the future of governance, with the High Council serving as the top-level governing body responsible for managing the state of the rollup.
We believe this collaboration will unlock a flurry of governance innovation, as DAOs will now be able to easily and trustlessly ship and utilize voting vaults and multichain voting from the rollup itself.
In terms of next steps, we would like to discuss being the first group to request a license from the Arbitrum DAO to run the L2 software for the High Council rollup. Additionally, this includes discussing details of a budget request in order to help with paying a team and running the infrastructure for High Council. The budget will be included in this proposal before it goes to a vote.
Motivation
On-chain organizations enable people to exercise the principles of the open-source movement by openly collaborating to accomplish shared visions and goals. DAOs aim to formalize coordination efficiently and openly. Lately, many DAOs have been seen as mechanisms for value capture rather than value creation. There is a distinct difference between value creation and value capture. Value creation is not focused on monetary gain but on establishing better systems through public goods infrastructure. Value creation is inherently additive and not extractive.
As the High Council considers partners in its goal to facilitate a new framework for DAO governance, we feel that Arbitrum also aligns with these principles. We are excited to announce that we have decided to launch the High Council on Arbitrum. As such, we’re excited to open up this discussion to the Arbitrum community and initiate discussions around collaboration opportunities.
Rationale
This is a collaborative effort by long term experts in the open-source crypto movement committed to bringing open-source organizations to life. High Council will launch a public infrastructure rollup dedicated to governance and collaboration. It represents a unified community effort to standardize and advance decentralized collaboration by facilitating the sharing of contracts, tools, resources, and network effects.
The High Council aims to act as a hub for DAOs to govern across multiple chains, utilizing voting vaults to redefine how voting occurs. By doing so, High Council aims to further decentralize governance in a manner that prioritizes inclusivity and transparency.
As mentioned, the High Council will comprise DAOs utilizing and building on the network. The High Council members will be responsible for developing the governance contracts, the rollup and bridging security mechanisms, and sharing resources.
High Council will use a voting vault that gives each member-DAO represented on the rollup collectively, 1 vote. Community members of each DAO can vote for their respective DAOs, with votes collectively propagating as a single DAO vote on the rollup.
Why Arbitrum?
We believe Arbitrum would be a great launch partner for the High Council governance rollup. Multi-round fraud proofs allow validators to challenge only a particular transaction instead of an entire batch of transactions, resulting in lower transaction fees, making Arbitrum one of the most cost-effective L2 networks in regard to transaction fees.
Arbitrum’s EVM compatibility provides a great developer experience, as does the ability to execute EVM code directly, without needing to recompile smart contracts. We also like that the open-source validator software includes a pre-built Docker image allowing anyone to easily engage in active, defensive, and watchtower validator strategies (realizing that validators are currently whitelisted but we anticipate this will be opened up).
It’s also not lost on us that Arbitrum has been advancing research in this area in collaboration with Offchain Labs and Cornell Tech to develop the first decentralized fair sequencing algorithm. The success of a truly decentralized L2 requires fair decentralized Sequencers, and Arbitrum’s commitment to advancing toward this vision loudly resonates with us.
Specifications
What is High Council?
High Council is a standalone governance rollup that DAOs can use and build on top of. High Council aims to become the go-to place for governance, and collaboration, creating a unified approach for advancing decentralized governance.
Through the use of voting vaults, protocols/DAOs running and building on the governance rollup are awarded a vote in the High Council. The voting vaults will collectively give each DAO 1 vote (E.g., if there are 12 DAOs, that’s 12 votes). The High Council will approve new DAO participation to avoid Sybil attacks. Cross-chain voting and DAO proposal execution are also a core part of the rollup; a protocol may have products or assets deployed in multiple chains governed from one place.
Key Structure
The High Council Organizational Structure
Currently, there are six working groups, each representing different key focus areas of bringing the Governance rollup to life. The system is leaderless, and we’re self-organized into different roles. We can’t emphasize enough; this effort is about providing liberty to bring organizational efforts on-chain, not value capture or financial incentives.
The initial six working groups are as follows:
High Council is comprised of an ecosystem of open source, battle-tested infrastructure that works together to create a seamless governance experience:
Council kit is an SDK for launching and managing your DAO, with an out-of-the-box, themeable UI and deployment starter kit to launch immediately. The tooling includes video tutorials, code samples, and getting-started guides.
The Council Kit offers the following benefits:
High Council will support Council Kit out of the gate as its initial governance framework, but expects to allow for DAOs to bring their own frameworks eventually as well.
Zodiac is a modular collection of tooling for DAOs built by the Gnosis Guild according to an open standard on top of the Safe. Zodiac enables adding common security and functionality patterns to DAOs, such as adding timelocks for decision-making, Snapshot vote execution using UMA’s oSnap module, and cross-domain governance using Connext.
Connext is a protocol for secure cross-domain (crosschain & crossrollup) communication. Connext takes a radically different approach than other messaging bridges, layering on top of canonical bridges (e.g. rollup bridges) to secure crosschain messages rather than implementing its own oracle or validator set. Messages that are passed through Connext are batched, aggregated, and posted to Ethereum L1 every 1-2 hours, where they can be disputed using fault proofs if fraud is detected.
Connext and Zodiac together form part of a Crosschain Governance Stack, that provides the following benefits to DAOs deployed to High Council:
To enable crosschain governance, DAOs deploying on High Council set up “Avatars” - Safes on each domain that control admin rights for protocol, treasury, or other contracts that the DAO would want to interact with. Then, they install the Zodiac app and Connext module in each Safe Avatar, which restricts the Avatar to only be callable by the DAO’s Governor contract on High Council.
Hats is a protocol for tokenized contributor roles & credentials for DAOs, which we call “hats”. Hats are connected together in a tree structure, which enables the creation of flexible governance structures that are ultimately controlled by the DAO itself. Hats are represented on-chain by tokens that conform to the ERC-1155 interface.
How will Hats support the High Council? Implementing Hats will address three key challenges for the High Council:
A note on composability: Hats Protocol is fully composable with other tools, as Hats are non-transferable tokens that can be combined with tools like Metropolis Pods (eg pods could wear the working group hats), Karma and UMA data for determining eligibility to wear a given hat (hats are revoked automatically if they no longer fulfill eligibility criteria), hat-gating Coordinape circles for compensation, hat-gating snapshot votes, and anything else that incorporates token gates.
Steps to Implement
We are currently inviting the community to provide feedback on this proposal and share any questions and ideas they may have. We also invite any service providers in the Arbitrum ecosystem to make themselves known if they feel they could support us from an infrastructure angle.
We aim to post a Snapshot in the next five days and then move this to a vote including a budget in order to help with paying a team and running the infrastructure with High Council.
Title – High Council x Arbitrum Launch Non-Constitutional Proposer: simona.eth Authors & reviewers: simona.eth bhuptani.eth charlesstlouis.eth alim.eth osumi.eth charlesstlouis.eth hatsprotocol.eth villanuevawill.eth
TL;DR
This proposal looks at the potential of a High Council partnership with Arbitrum to advance decentralized collaboration and governance. Working with the Arbitrum community, the High Council can provide a decentralized governance rollup enabling teams to share resources and develop the future of governance, with the High Council serving as the top-level governing body responsible for managing the state of the rollup.
We believe this collaboration will unlock a flurry of governance innovation, as DAOs will now be able to easily and trustlessly ship and utilize voting vaults and multichain voting from the rollup itself.
In terms of next steps, we would like to discuss being the first group to request a license from the Arbitrum DAO to run the L2 software for the High Council rollup. Additionally, this includes discussing details of a budget request in order to help with paying a team and running the infrastructure for High Council. The budget will be included in this proposal before it goes to a vote.
Motivation
On-chain organizations enable people to exercise the principles of the open-source movement by openly collaborating to accomplish shared visions and goals. DAOs aim to formalize coordination efficiently and openly. Lately, many DAOs have been seen as mechanisms for value capture rather than value creation. There is a distinct difference between value creation and value capture. Value creation is not focused on monetary gain but on establishing better systems through public goods infrastructure. Value creation is inherently additive and not extractive.
As the High Council considers partners in its goal to facilitate a new framework for DAO governance, we feel that Arbitrum also aligns with these principles. We are excited to announce that we have decided to launch the High Council on Arbitrum. As such, we’re excited to open up this discussion to the Arbitrum community and initiate discussions around collaboration opportunities.
Rationale
This is a collaborative effort by long term experts in the open-source crypto movement committed to bringing open-source organizations to life. High Council will launch a public infrastructure rollup dedicated to governance and collaboration. It represents a unified community effort to standardize and advance decentralized collaboration by facilitating the sharing of contracts, tools, resources, and network effects.
The High Council aims to act as a hub for DAOs to govern across multiple chains, utilizing voting vaults to redefine how voting occurs. By doing so, High Council aims to further decentralize governance in a manner that prioritizes inclusivity and transparency.
As mentioned, the High Council will comprise DAOs utilizing and building on the network. The High Council members will be responsible for developing the governance contracts, the rollup and bridging security mechanisms, and sharing resources.
High Council will use a voting vault that gives each member-DAO represented on the rollup collectively, 1 vote. Community members of each DAO can vote for their respective DAOs, with votes collectively propagating as a single DAO vote on the rollup.
Why Arbitrum?
We believe Arbitrum would be a great launch partner for the High Council governance rollup. Multi-round fraud proofs allow validators to challenge only a particular transaction instead of an entire batch of transactions, resulting in lower transaction fees, making Arbitrum one of the most cost-effective L2 networks in regard to transaction fees.
Arbitrum’s EVM compatibility provides a great developer experience, as does the ability to execute EVM code directly, without needing to recompile smart contracts. We also like that the open-source validator software includes a pre-built Docker image allowing anyone to easily engage in active, defensive, and watchtower validator strategies (realizing that validators are currently whitelisted but we anticipate this will be opened up).
It’s also not lost on us that Arbitrum has been advancing research in this area in collaboration with Offchain Labs and Cornell Tech to develop the first decentralized fair sequencing algorithm. The success of a truly decentralized L2 requires fair decentralized Sequencers, and Arbitrum’s commitment to advancing toward this vision loudly resonates with us.
Specifications
What is High Council?
High Council is a standalone governance rollup that DAOs can use and build on top of. High Council aims to become the go-to place for governance, and collaboration, creating a unified approach for advancing decentralized governance.
Through the use of voting vaults, protocols/DAOs running and building on the governance rollup are awarded a vote in the High Council. The voting vaults will collectively give each DAO 1 vote (E.g., if there are 12 DAOs, that’s 12 votes). The High Council will approve new DAO participation to avoid Sybil attacks. Cross-chain voting and DAO proposal execution are also a core part of the rollup; a protocol may have products or assets deployed in multiple chains governed from one place.
Key Structure
The High Council Organizational Structure
Currently, there are six working groups, each representing different key focus areas of bringing the Governance rollup to life. The system is leaderless, and we’re self-organized into different roles. We can’t emphasize enough; this effort is about providing liberty to bring organizational efforts on-chain, not value capture or financial incentives.
The initial six working groups are as follows:
High Council is comprised of an ecosystem of open source, battle-tested infrastructure that works together to create a seamless governance experience:
Council kit is an SDK for launching and managing your DAO, with an out-of-the-box, themeable UI and deployment starter kit to launch immediately. The tooling includes video tutorials, code samples, and getting-started guides.
The Council Kit offers the following benefits:
High Council will support Council Kit out of the gate as its initial governance framework, but expects to allow for DAOs to bring their own frameworks eventually as well.
Zodiac is a modular collection of tooling for DAOs built by the Gnosis Guild according to an open standard on top of the Safe. Zodiac enables adding common security and functionality patterns to DAOs, such as adding timelocks for decision-making, Snapshot vote execution using UMA’s oSnap module, and cross-domain governance using Connext.
Connext is a protocol for secure cross-domain (crosschain & crossrollup) communication. Connext takes a radically different approach than other messaging bridges, layering on top of canonical bridges (e.g. rollup bridges) to secure crosschain messages rather than implementing its own oracle or validator set. Messages that are passed through Connext are batched, aggregated, and posted to Ethereum L1 every 1-2 hours, where they can be disputed using fault proofs if fraud is detected.
Connext and Zodiac together form part of a Crosschain Governance Stack, that provides the following benefits to DAOs deployed to High Council:
To enable crosschain governance, DAOs deploying on High Council set up “Avatars” - Safes on each domain that control admin rights for protocol, treasury, or other contracts that the DAO would want to interact with. Then, they install the Zodiac app and Connext module in each Safe Avatar, which restricts the Avatar to only be callable by the DAO’s Governor contract on High Council.
Hats is a protocol for tokenized contributor roles & credentials for DAOs, which we call “hats”. Hats are connected together in a tree structure, which enables the creation of flexible governance structures that are ultimately controlled by the DAO itself. Hats are represented on-chain by tokens that conform to the ERC-1155 interface.
How will Hats support the High Council? Implementing Hats will address three key challenges for the High Council:
A note on composability: Hats Protocol is fully composable with other tools, as Hats are non-transferable tokens that can be combined with tools like Metropolis Pods (eg pods could wear the working group hats), Karma and UMA data for determining eligibility to wear a given hat (hats are revoked automatically if they no longer fulfill eligibility criteria), hat-gating Coordinape circles for compensation, hat-gating snapshot votes, and anything else that incorporates token gates.
Steps to Implement
We are currently inviting the community to provide feedback on this proposal and share any questions and ideas they may have. We also invite any service providers in the Arbitrum ecosystem to make themselves known if they feel they could support us from an infrastructure angle.
We aim to post a Snapshot in the next five days and then move this to a vote including a budget in order to help with paying a team and running the infrastructure with High Council.
Well, partnering to launch on Arbitrum is a collaborative step - concomitantly engaging multiple parties is near impossible, especially with a volunteer team up until this point. The value add is that the teams on the list would effectively become part of the Arbitrum community via this. So it's important to weight value from various angles.
Of course, reaching out to current Arb teams and protocols to join as well is on our list - as you can see, the proposal already includes a call to collab for infra
And + @Franklin - Not everyone on the list is a DAO member. Some are just contributors or contributor groups. Contributors have volunteer status now so there is no need for off boarding since no one is really getting paid at this moment.
Members can be offboarded automatically when their Hat (token) is revoked at the point they no longer meet the minimum criteria set for membership. Specific membership criteria will be set by governance and will become active once this group opts to be funded beyond payment for infra support
Yes, as mentioned in the proposal, we're hoping to start conversations with infra service providers in the Arbitrum ecosystem so that we may evaluate what a monetary commitment would be to ensure support and state it before a vote
Well, partnering to launch on Arbitrum is a collaborative step - concomitantly engaging multiple parties is near impossible, especially with a volunteer team up until this point. The value add is that the teams on the list would effectively become part of the Arbitrum community via this. So it's important to weight value from various angles.
Of course, reaching out to current Arb teams and protocols to join as well is on our list - as you can see, the proposal already includes a call to collab for infra
And + @Franklin - Not everyone on the list is a DAO member. Some are just contributors or contributor groups. Contributors have volunteer status now so there is no need for off boarding since no one is really getting paid at this moment.
Members can be offboarded automatically when their Hat (token) is revoked at the point they no longer meet the minimum criteria set for membership. Specific membership criteria will be set by governance and will become active once this group opts to be funded beyond payment for infra support
Yes, as mentioned in the proposal, we're hoping to start conversations with infra service providers in the Arbitrum ecosystem so that we may evaluate what a monetary commitment would be to ensure support and state it before a vote
Is this image a list of current High Council members, or what is it in reference to?
How do you handle offboarding of members?
Is this image a list of current High Council members, or what is it in reference to?
How do you handle offboarding of members?
Again: feels like you want to spearhead the way for other protocols/companies/daos/layers/whatever into arbitrum (which, tbh, can be a good thing if done correctly), without having no one, on your team, being able to talk to you about what has been done so far in arbitrum and having a tab on what both community and currently builders wants and needs to grow and scale.
This is a big gap in my opinion that should be addressed, otherwise you will have a disconnection between your deliverables and what the end users really need.
Again: feels like you want to spearhead the way for other protocols/companies/daos/layers/whatever into arbitrum (which, tbh, can be a good thing if done correctly), without having no one, on your team, being able to talk to you about what has been done so far in arbitrum and having a tab on what both community and currently builders wants and needs to grow and scale.
This is a big gap in my opinion that should be addressed, otherwise you will have a disconnection between your deliverables and what the end users really need.
if you wanna talk more in depth about this, reach me on tg, @ jojothecow
Hi! thanks for the proposal!
One question: If I got it right, this is a tooling for governance, and you guys are applying for a grant to deploy it on Arbitrum.
Is there any Arbitrum protocol that signalized that would like to use it, or is there a plan to use it as the tool for the Arbitrum governance itself?
Sorry let me rephrase. Why there is no native arbitrum entity (dao/protocol/whatever) in there?
Feels like having a council for a country with no native people from that country. Quite odd to be honest.
Again: feels like you want to spearhead the way for other protocols/companies/daos/layers/whatever into arbitrum (which, tbh, can be a good thing if done correctly), without having no one, on your team, being able to talk to you about what has been done so far in arbitrum and having a tab on what both community and currently builders wants and needs to grow and scale.
This is a big gap in my opinion that should be addressed, otherwise you will have a disconnection between your deliverables and what the end users really need.
Again: feels like you want to spearhead the way for other protocols/companies/daos/layers/whatever into arbitrum (which, tbh, can be a good thing if done correctly), without having no one, on your team, being able to talk to you about what has been done so far in arbitrum and having a tab on what both community and currently builders wants and needs to grow and scale.
This is a big gap in my opinion that should be addressed, otherwise you will have a disconnection between your deliverables and what the end users really need.
if you wanna talk more in depth about this, reach me on tg, @ jojothecow
Hi! thanks for the proposal!
One question: If I got it right, this is a tooling for governance, and you guys are applying for a grant to deploy it on Arbitrum.
Is there any Arbitrum protocol that signalized that would like to use it, or is there a plan to use it as the tool for the Arbitrum governance itself?
Sorry let me rephrase. Why there is no native arbitrum entity (dao/protocol/whatever) in there?
Feels like having a council for a country with no native people from that country. Quite odd to be honest.
I actually have the same questions on these: why these names? How do names get added or offboarded from this? Why there are not native arbitrum protocols here?
...why Canto?
I actually have the same questions on these: why these names? How do names get added or offboarded from this? Why there are not native arbitrum protocols here?
...why Canto?
