Across Governance Operating Manual

Overview

The Across governance process will evolve to meet the needs of Across DAO as it grows, and this is a living document. Anyone can participate in the Across Governance process, and anyone with ACX voting power can vote on proposals.

Presently, tokenholders control treasury spending and updates to governance.

Governance Components

The Across Governance process follows the pathway from ideation, to draft, to proposal, to implementation. Anything subject to governance will follow this path and be decided on by ACX tokenholders.

Governance Toolkit:

  • Forum: A platform for discussion and deliberation on governance proposals
  • Snapshot: A platform for where all governance proposals are submitted for vote
  • Optimistic Governance (future implementation): A mechanism for trustless execution of snapshot votes.

Governance Participants:

Voters - anyone who holds ACX, or ACX representative tokens that hold voting power, and participates actively in governance. See list below for voting eligible tokens

Across Council - The Council executes approved Snapshot proposals prior to the implementation of optimistic governance. The current signers are Risk Labs representatives.

  • Accross DAO Safe: 0xB524735356985D2f267FA010D681f061DfF03715
  • Threshold: 3/5
  • Signers (eth):
    0x1d933Fd71FF07E69f066d50B39a7C34EB3b69F05
    0x1f11D8B72fc1B534448436BA60B4B371276DAb33
    0x837219D7a9C666F5542c4559Bf17D7B804E5c5fe
    0x996267d7d1B7f5046543feDe2c2Db473Ed4f65e9
    0xcc400c09ecBAC3e0033e4587BdFAABB26223e37d

Committees - Subject matter experts that consider and pursue goals specific to their domain, acting in the best interests of the Across DAO. Committees are able to make updates to parameters without the need for a full tokenholder voting cycle, allowing the bridge to remain adaptive. Shortly after launch, RL will upgrade the protocol to allow for committee implementation.

Proposal Types:

  • Treasury Funding
  • Governance Updates
  • Committee implementation or replacement (future)
  • Protocol upgrades (future)
Type Description Submission requirements Vote Duration Quorum Approval Threshold
Treasury Funding ACX distributions to proactively encourage the growth and development of the Across ecosystem Forum + Snapshot 7 days + time required for steps 1 and 2 in voting cycle 20M 51%
Governance Updates A vote to update a component of Across governance system. Forum + Snapshot 7 days + time required for steps 1 and 2 in voting cycle 20M 51%

Note: Risk Labs has historically acted as the only builder of Across Protocol. In order to enable others to contribute at a protocol level, we are in the process of outlining the protocol parameters and requirements for a protocol upgrade template. Stay tuned for more details.

Process

Step 1: Request for comment (Forum)

Post a proposal draft in Ideas and Feedback in Forum. Collect feedback from the community and update the proposal as needed. There is no hard timeline on this step, but proposals that donโ€™t take this step seriously are not likely to pass. Once your idea is ready to submit as a proposal, it will need to follow the template below, so you should consider drafting your idea in this format to start. You can also find this template here.

Header

Title: (enter proposal title)

Author(s): (enter name(s) of associated authors)

Status: (RFC, Proposal, Vote)

Related Discussions: (optional - paste link here)

Submission Date: (Enter Date)

Body

Summary:
Give us a TL;DR on your proposal; no more than 2-3 sentences.

Motivation:
What problems will this proposal address/solve? Whatโ€™s the value-add?

Specification & Implementation:
Describe the proposal in as much detail as is necessary. Explain the vision for the proposal. How will this affect the protocol both technically, socially, financially (if applicable), and governance-wise? What steps need to be taken to implement this proposal?

Rationale:
Explain any decisions above that were chosen over an alternative. Why is this the best way to do it? How will the implementation of this proposal advance the protocol?

Downside (Cons):
Are there any disadvantages with implementing the proposal? Are there any security considerations or potentially negative financial exposures to consider?

Voting:
Define what a โ€œyesโ€ and โ€œnoโ€ vote entails. Once the proposal moves to a vote, please include the link to Snapshot here.

Step 2: Request to proceed (Forum)

After implementing any changes to the proposal based on feedback received in step 1, you should present a final draft in the Proposal section of forum and request to proceed to snapshot. If applicable, you should include the appropriate tag for your proposal when creating your post. You will also want to make sure to include a link to your discussion draft in the final proposal.

Any Forum admin can review the proposal for format compliance and provide an indication that the proposal can move to snapshot. This is not an indication of support for the ideas in the proposal, but rather an indication that the proposal meets the requirements needed to move to a vote. Proposals that are not properly formatted should not move to a formal vote.

Step 3: Formal vote (Snapshot)

Proposals that have been approved in step 2 are ready to be voted on and may be posted to snapshot with a 7 day voting period. A proposer must have a voting weight of at least 20,000 ACX in order to submit a proposal. If you do not meet the requirement for submitting a proposal, a qualified voter may post the proposal on your behalf if they wish to do so.

Step 4: Results

If a proposal passes Snapshot, it will be executed by the Across DAO Safe. The Across Council executes approved Snapshot proposals prior to the implementation of optimistic governance (more on optimistic governance once it is ready to be implemented).

2 Likes