Skip to content

Retire bundle: signer's direct vault roles, after the burn-in - #336

Open
hardyjosh wants to merge 1 commit into
2026-08-29-issue-333-orchestrator-beacon-in-governed-setfrom
2026-08-31-retire-direct-signer-roles
Open

Retire bundle: signer's direct vault roles, after the burn-in#336
hardyjosh wants to merge 1 commit into
2026-08-29-issue-333-orchestrator-beacon-in-governed-setfrom
2026-08-31-retire-direct-signer-roles

Conversation

@hardyjosh

@hardyjosh hardyjosh commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Top of stack: #324 (enable) → #325 (fleet) → #334 (governed beacon set) → this.

The retire half of the enable/retire split: 20260831-retire-direct-signer-roles (run-script registry, per chain) revokes the service signer's direct DEPOSIT/WITHDRAW once the orchestrator has proven itself — closing the parallel burn-in window #324 deliberately opens.

  • Burn-in gate (OrchestratorPathNotEnabled): refuses to author unless the orchestrator holds both vault roles AND the signer holds MINT/BURN on it — retirement can never strand a chain without a working mint path.
  • Untouched: the signer's CERTIFY and the Safe's break-glass action roles.
  • Own deadline 2026-10-15 — two weeks after the enable/fleet deadline, so the burn-in window is honoured by construction rather than by cron pressure.
  • Self-scoping, post-sim row-by-row survival check, n+1 proves the Safe can restore the fallback, signer-side verify(), Fireblocks-style post-execution pin lifecycle.

Unit 7/7, prod walk 3/3 (today every chain pins the world/enable-pending refusals).

🤖 Generated with Claude Code

https://claude.ai/code/session_01KbsbYN4C4YDa8pu9DdudoX

@coderabbitai

coderabbitai Bot commented Aug 31, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: c1915f4c-761d-49ab-b819-afffc9ed7cb7

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Copy link
Copy Markdown
Contributor Author

@hardyjosh
hardyjosh marked this pull request as ready for review August 31, 2026 15:38
@hardyjosh
hardyjosh force-pushed the 2026-08-31-retire-direct-signer-roles branch from 650f281 to bd86161 Compare August 31, 2026 15:54
@hardyjosh
hardyjosh force-pushed the 2026-08-29-issue-333-orchestrator-beacon-in-governed-set branch from a94712a to 2f96db0 Compare August 31, 2026 15:54
20260831-retire-direct-signer-roles (run-script registry): the second
half of the enable/retire split of the old cutover bundle, per review -
the enable bundle grants the orchestrator path while LEAVING the
signer's direct DEPOSIT/WITHDRAW as a parallel emergency fallback; this
bundle revokes them once the orchestrator has proven itself.

The burn-in gate (OrchestratorPathNotEnabled) refuses to author unless
the orchestrator holds both vault roles AND the signer holds MINT/BURN
on it - the retirement can never strand a chain without a working mint
path. Self-scoping; already-retired refuses; post-sim proves the
signer's CERTIFY and every other canonical row survive; n+1 proves the
Safe can restore the fallback under the live threshold. Own deadline
2026-10-15 - two weeks after the enable/fleet deadline, honouring the
burn-in window by construction.

7 unit tests + 3-state prod walk per chain.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KbsbYN4C4YDa8pu9DdudoX
@hardyjosh
hardyjosh force-pushed the 2026-08-31-retire-direct-signer-roles branch from bd86161 to 43d7b34 Compare August 31, 2026 17:01
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