Deploy workflow for the audited 0.1.30 orchestrator set

[hardyjosh]

Why

The ST0xOrchestrator has no deploy workflow. manual-sol-artifacts-0-1-1.yaml ships only the audited 0.1.1 bootstrap set — which predates the orchestrator — and the current-source deploy path was deliberately removed (5680253: deploys must be audited versions only). This blocks shipping the orchestrator set to the bootstrap networks for the multichain rollout.

What

Follows the documented process for deploying a later audited version: freeze its numbered snapshot and give it its own version-specific deploy script.

• src/generated/0_1_30/ — the frozen audited snapshot, deliberately PARTIAL: only the orchestrator's six-contract dependency closure (facet, receipt, receipt vault, OARV beacon-set deployer, orchestrator, orchestrator beacon-set deployer). The wrapped-token-vault chain, authorizers and unified deployer stay 0.1.1-only — their production instances come from the audited 0.1.1 bootstrap set. Each file extracted byte-identical from tag sol-v0.1.30 (= candidate at that commit). The tag's commit 4f126183 is the exact commit Protofire's st0x.deploy 6.0 report (Aug 2026) reviews — all issues marked fixed. Because the H01 remediation's optimizer change moved every address, there are no 0.1.1 twins: all six suites deploy fresh on every network, Base included.
• src/generated/LibProdDeployV4.sol — regenerated by BuildPointers to emit the _0_1_30 alias set (+68 lines, no other changes; git-clean CI pins the regeneration).
• script/DeployProdV4_0_1_30.sol — mirrors DeployProdV4_0_1_1.sol: stored _0_1_30 creation bytecode, _0_1_30 address/codehash pins, one suite per dispatch. Covers exactly the orchestrator's on-chain dependency closure, in deploy order: corporate-actions facet → receipt → receipt vault → OARV beacon-set deployer → orchestrator → orchestrator beacon-set deployer. Dependency pointers enforce the order structurally (including orchestrator → OARV set-deployer, since initialize hard-reverts via the vault-logic version lock until the set-deployer it was built against has code).
• .github/workflows/manual-sol-artifacts-0-1-30.yaml — mirrors the 0.1.1 workflow; networks base / ethereum / hyperevm, --legacy on HyperEVM, verify: false (stored-bytecode deploys stay verifiable from the tag even after source drifts; verify manually).
• Tests — frozen-redeploy coverage for the all six 0.1.30 contracts (no 0.1.1 twins exist at this release), and the 0.1.30 block in testTaggedRuntimeHashesToCodehash.
• CLAUDE.md — documents the 0.1.8 deploy surface.

Current on-chain state (checked 2026-08-25)

Nothing at the 0.1.30 addresses on any chain — the optimizer change moved every address, so Base's 0.1.8-era closure does not carry over. All six suites are real deploys on base / ethereum / hyperevm.

Verification

• LibProdDeployV4.t.sol: 39 pass.
• slither .: 0 results. forge fmt --check, reuse lint, BuildPointers regeneration all clean/idempotent.
• Fork simulation of a fresh suite against Ethereum: simulates the Zoltu deploy cleanly.
• Full forge test locally: only failures are public-RPC 429s / missing private RPC env vars for fork tests (no logic failures).

Out of scope

Creating an orchestrator instance (ST0xOrchestratorBeaconSetDeployer.deploy(owner)) is a non-deterministic operation with a per-chain owner decision — that stays an ops step (dated script / runbook), not a suite.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KbsbYN4C4YDa8pu9DdudoX

Summary by CodeRabbit

• New Features

  • Added deployment support for the audited 0.1.30 ST0x orchestrator contract suite across Base, Ethereum, and HyperEVM.
  • Added selectable deployment suites with dependency-aware deployment ordering and network validation.
  • Added a manually triggered deployment workflow with network and suite selection.

• Tests

  • Added coverage verifying frozen 0.1.30 deployments, runtime bytecode, and code hashes for six orchestrator components.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 307715a4-5cc7-458d-9074-155253e5604a

📥 Commits

Reviewing files that changed from the base of the PR and between 1c7e986 and 511811c.

⛔ Files ignored due to path filters (7)

• src/generated/0_1_30/ST0xOrchestrator.pointers.sol is excluded by !**/generated/**
• src/generated/0_1_30/ST0xOrchestratorBeaconSetDeployer.pointers.sol is excluded by !**/generated/**
• src/generated/0_1_30/StoxCorporateActionsFacet.pointers.sol is excluded by !**/generated/**
• src/generated/0_1_30/StoxOffchainAssetReceiptVaultBeaconSetDeployer.pointers.sol is excluded by !**/generated/**
• src/generated/0_1_30/StoxReceipt.pointers.sol is excluded by !**/generated/**
• src/generated/0_1_30/StoxReceiptVault.pointers.sol is excluded by !**/generated/**
• src/generated/LibProdDeployV4.sol is excluded by !**/generated/**

📒 Files selected for processing (3)

• .github/workflows/manual-sol-artifacts-0-1-30.yaml
• script/DeployProdV4_0_1_30.sol
• test/src/lib/LibProdDeployV4.t.sol

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The PR adds a 0.1.30 deterministic deployment script and manual workflow for six contracts across three networks. It also adds runtime-codehash assertions and frozen redeployment tests for the 0.1.30 dependency closure.

Changes

0.1.30 Frozen Deployment

Layer / File(s)	Summary
Deployment script and dependency ordering script/DeployProdV4_0_1_30.sol	The script validates networks and suites, then deploys six contracts with pinned bytecode, addresses, code hashes, and dependencies.
Manual deployment workflow .github/workflows/manual-sol-artifacts-0-1-30.yaml	The workflow exposes suite and network choices, enables legacy transactions for HyperEVM, disables verification, and forwards deployment secrets.
Runtime and frozen redeployment validation test/src/lib/LibProdDeployV4.t.sol	Tests verify six runtime codehashes and frozen redeployments. The 0.1.30 snapshot covers the receipt, receipt vault, corporate-actions facet, OARV beacon-set deployer, orchestrator, and orchestrator beacon-set deployer.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Merge Risk: ⚪ Minimal · up to 51181

This change adds the audited 0.1.30 orchestrator deployment workflow and its frozen artifacts; the listed checks and simulations pass, so no actionable merge-blocking risk remains beyond normal checks and review.

Sequence Diagram(s)

sequenceDiagram
  participant Operator
  participant ManualWorkflow
  participant Deploy
  participant LibRainDeploy
  participant TargetNetwork
  Operator->>ManualWorkflow: Select suite and network
  ManualWorkflow->>Deploy: Run Deploy.run()
  Deploy->>LibRainDeploy: Deploy pinned contract and dependencies
  LibRainDeploy->>TargetNetwork: Broadcast deployment transaction
  TargetNetwork-->>LibRainDeploy: Return deployed code and address

Loading

Poem

A rabbit checks the bytecode bright
Six frozen contracts stand just right
The workflow hops from choice to chain
Hashes match through sun and rain
“Deploy,” says Bun, “then test again!”

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main changes: adding a deployment workflow for the audited 0.1.30 orchestrator set. It matches the version and deployment focus shown in the changed files…

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.)

Full details: Title check

Explanation

The title clearly and concisely describes the main changes: adding a deployment workflow for the audited 0.1.30 orchestrator set. It matches the version and deployment focus shown in the changed files.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 2026-08-17-orchestrator-manual-sol-artifacts

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[hardyjosh]

• Fleet upgrade bundle: receipt + receipt-vault beacons to audited 0.1.30 #325
• Cutover bundle: mint/burn to the orchestrator, signer via MINT/BURN #324
• Orchestrator beacon-owner migration to the chain Safe #317
• Orchestrator instance deploy script + pinned invariants #316
• Deploy workflow for the audited 0.1.30 orchestrator set #314 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.