Skip to content

sync docs - #381

Open
godzillaba wants to merge 2 commits into
mainfrom
docs/sync-governance-params
Open

sync docs#381
godzillaba wants to merge 2 commits into
mainfrom
docs/sync-governance-params

Conversation

@godzillaba

Copy link
Copy Markdown
Collaborator

No description provided.

Update stale parameters to match current mainnet/constitution:
- L2 core timelock delay 3 -> 8 days (overview, security-council-mgmt)
- Non-emergency Security Council threshold 7-of-12 -> 9-of-12
  (overview, security-council-mgmt, proposal_lifecycle_example)
- Replace fixed 5%/3%-of-votable quorum description with the DVP
  (delegated voting power) model and its min/max clamps; rename the
  "5%"/"3%" governors to Core/Treasury (overview, gotchas)

Also fix propMon output filename (proposalState.json) and scipts typos.
@godzillaba
godzillaba marked this pull request as ready for review July 24, 2026 14:58
@godzillaba
godzillaba requested review from gzeoneth and yahgwai July 27, 2026 15:56

@TucksonDev TucksonDev left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, with a few minor comments

Comment thread docs/overview.md

#### Quorum

Quorum is based on the total delegated voting power of $ARB (excluding tokens delegated to the exclude address). For each governor, quorum is a fraction of the delegated voting power, clamped between a fixed minimum and maximum:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could maybe add that this is calculated based on the snapshot taken when the proposal is created.

Comment thread docs/overview.md

## Proposal delays

All governance activities occur on Arbitrum One. Proposals are made there, as well as delegation and voting. A proposal made to the constitutional governor experiences enough delay to ensure that users can safely exit the chain before the proposal is executed, should they deem it malicious.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we include somewhere that non-constitutional proposals have a 3-day delay, but they don't do the roundtrip?

Comment thread docs/overview.md
#### Arbitrum One L2 Timelock

Proposals can be scheduled here by the 5% governor, or by a 7-of-12 agreement in the Security Council. This timelock enforces a 3-day delay before the proposal can then be executed by anybody.
Proposals can be scheduled here by the Core governor, or by a 9-of-12 agreement in the Security Council. This timelock enforces an 8-day delay before the proposal can then be executed by anybody.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 things here:

  • not sure if worth it, but maybe clarify that both sc multisig can create a proposal
  • maybe add information about the Treasury Timelock too (only the Treasury Governor can propose, and it has a 3-day delay)

Comment thread docs/overview.md
| Contract | Receive proposals scheduled by | Timelock |
| -------- | ------------------------------ | ----------------- |
| Arb One L2 Timelock<br/>(Arb1TL) | the 5% governor / 7-12 in Security Council | 3 days |
| Arb One L2 Timelock<br/>(Arb1TL) | the Core governor / 9-12 in Security Council | 8 days |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here as the previous comment:

  • Maybe specify that both sc multisigs can create proposal
  • Add the Treasury timelock

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants