Skip to content

BR-3: --handover reports each endpoint's handover step; admin multisig must be 5 of 6 - #12

Merged
dendisuhubdy merged 5 commits into
mainfrom
feat/i2-handover-status
Nov 18, 2026
Merged

dendisuhubdy merged 5 commits into
mainfrom
feat/i2-handover-status

Conversation

@dendisuhubdy

@dendisuhubdy dendisuhubdy commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

Tracks randprotocol/monorepo#2

What main already has

The handover tooling for every chain (evm/script/Governance.s.sol, deploy/tron-ops.js, rand-bridge-cli), each building or checking a step without sending unless told to, and rand-bridge-audit --governance, which judges the end state.

What was missing

A way to see which step an endpoint is at. --governance fails every rule until the last step, so an accept that has served its delay and was never executed reads the same as a handover never started.

rand-bridge-audit --config <file> --handover [--salt 0x…] reads each endpoint and prints one stage (NOT STARTED, TRANSFERRED, ACCEPT NOT SCHEDULED, ACCEPT SCHEDULED, WAITING, ACCEPT EXECUTABLE NOW, ADMIN MOVED, UNEXPECTED, UNKNOWN), who is admin at that stage, and the next command. Read-only, no key. Exits non-zero until every endpoint is at ADMIN MOVED.

Admin multisig: 5 signers of 6 (owner's standing rule)

  • rand-bridge-audit --governance gains a last row on every endpoint, admin multisig is 5 of 6 (owner's rule). PASS only for a Safe with threshold 5 and 6 owners, a Tron account whose owner and every active permission need 5 signatures of 6 keys, or a Squads multisig with threshold 5 and 6 members. Any other readable shape (2 of 3, 3 of 5, 6 of 6, …) is a FAIL that prints the shape; unreadable signers are UNKNOWN; none configured is a FAIL. Not configurable.
  • deploy/tron-ops.js multisig-permissions defaults both thresholds to 5 (was 3). docs/governance.md and daemons/config.example.toml name 5 of 6.
  • Not changed: the 6-of-8 guardian quorum; the pause multisig (the audit does not hold it to 5 of 6, and the doc still suggests 2 of 5 so a pause is quick — whether the rule should cover it is the owner's call); evm/script/Governance.s.sol, whose handover() still accepts any Safe with a threshold of at least 2 (the audit row is what reports the shape); the dated design spec under docs/superpowers/.
  • If the Tron admin account on chain is 3 of 5, as one of the two disagreeing documents records, this row fails there until its permissions are updated.
  • deploy/tron-ops.test.js was not run: it needs tron/node_modules, which is not installed here and CI does not run it. The change there is the two default numbers.

Files

  • daemons/src/handover.rs (new), daemons/src/bin/audit.rs, daemons/src/lib.rs, daemons/src/gov_audit.rs (the 5-of-6 row, +3 tests), deploy/tron-ops.js, daemons/config.example.toml
  • daemons/tests/handover.rs (new, 7 tests; the operation id is held to the one recorded for the Tron endpoint)
  • docs/governance.md §5a: the stages and the per-chain order of work

Tests

cargo test --release in daemons/: all test binaries pass, no failures. Nothing was run against a live endpoint.

Upgrade

--handover is a new flag on a read-only tool. --governance has one more row per endpoint, so its output and its pass condition change: an admin multisig that is not 5 of 6 now fails it.

Left for the owner

  • Running --handover and --governance against the live endpoints, and settling the two documents that disagree about the Tron account permissions (the note at the top of docs/governance.md).
  • Every on-chain step: the multisig signatures for the Tron accept, the Ethereum and BSC handover, the Solana admin and upgrade authority, creating the Safes and the Squads multisig.

🤖 Generated with Claude Code

…handover each endpoint is at

The handover tooling (Governance.s.sol, tron-ops.js, rand-bridge-cli) and
the end-state audit (--governance) exist. Nothing said how far along an
endpoint is: --governance fails every rule until the last step, and a
scheduled acceptAdmin() whose delay has passed looks the same as one never
started, while the single key is still admin.

--handover reads admin(), pendingAdmin(), pauser(), their code, and the
timelock's getTimestamp of the acceptAdmin() operation against the latest
block time (Solana: the Config's admin and pending admin, the upgrade
authority and the configured Squads vault), and prints one stage per
endpoint with the next command of docs/governance.md §4. It exits non-zero
until the admin has moved on every endpoint. It sends nothing and needs no
key.

The operation id is computed as the timelock's hashOperation; a test holds
it to the id recorded for the live Tron endpoint.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YGaYNQ4cvFtg2UmokVgrAN
@codecov

codecov Bot commented Nov 18, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

…eports any other shape

The owner's standing rule: a multisig account is 5 of 6, never 2 of 3.
The audit accepted any admin multisig with a threshold of at least
min_threshold (2), so 2 of 3 and 3 of 5 passed every row.

rand-bridge-audit --governance gains a last row on every endpoint,
"admin multisig is 5 of 6 (owner's rule)": PASS only for a Safe with
threshold 5 and 6 owners, a Tron account whose owner and every active
permission need 5 signatures of 6 keys, or a Squads multisig with
threshold 5 and 6 members. Any other shape it can read is a FAIL that
prints the shape; signers it cannot read are UNKNOWN; no multisig
configured is a FAIL. The row is not configurable. The pause multisig
and the 6-of-8 guardian quorum are not touched.

tron-ops.js multisig-permissions defaults both thresholds to 5, and
docs/governance.md names 5 of 6 with six signers wherever it named 3 of
5 for the admin multisig.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YGaYNQ4cvFtg2UmokVgrAN
@dendisuhubdy dendisuhubdy changed the title BR-3: rand-bridge-audit --handover reports each endpoint's handover step BR-3: --handover reports each endpoint's handover step; admin multisig must be 5 of 6 Nov 18, 2026
dendisuhubdy and others added 3 commits November 18, 2026 14:08
rand-bridge-audit keeps both --handover and --headroom.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YGaYNQ4cvFtg2UmokVgrAN
rand-bridge-audit keeps --handover, --limits and --headroom.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YGaYNQ4cvFtg2UmokVgrAN
@dendisuhubdy
dendisuhubdy merged commit 0389095 into main Nov 18, 2026
2 checks passed
@dendisuhubdy
dendisuhubdy deleted the feat/i2-handover-status branch November 18, 2026 18:58
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.

1 participant