pin(tokens): hydrate the Ethereum token table + add RKLB to the canonical set

[hardyjosh]

Pins the full Ethereum production token table and completes the canonical set with RKLB (previously an accidental omission from every table in this repo). PINS ONLY — the RKLB operational scripts live in the follow-up ops PR (#271).

Ethereum table hydration. The 20260706-deploy-tokens-ethereum broadcast executed 2026-07-22 (run 29921218929): 28 tokens deployed via the 0.1.1 unified deployer, each wired onto the Ethereum V4 authoriser and handed to the Ethereum token-owner Safe — 84 txs, zero failures. productionTokensEthereum() is hydrated from the run's logged (underlying, receipt, receiptVault, wrapped) tuples; first + last vaults spot-verified live.

RKLB pins. Live production on Base (Safe-deployed at block 41704399, Safe-owned, V1-address production beacons) but absent from every table — so no invariant covered it, the V4 swap batch skipped it (still on the V3 authoriser), and the Ethereum broadcast never deployed it. This PR adds the LibProdTokenConfig row + Base table row 29 (validated against the live Base vault), and the Ethereum row 29 pinned from the executed gap-fill broadcast (run 29924926246), verified wired live.

The full 29-token Ethereum parity leg passes against live mainnet. The strict Base uniform-authoriser invariants stay red until the two pending Safe bundles (6-vault + RKLB single-tx, authored via #271's scripts) execute — the intended forcing function.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VPs1hCTxusmaSeFKvoc4Kr

Summary by CodeRabbit

• New Features
  • Added Rocket Lab USA Inc. (RKLB) token support across production environments.
  • Added the RKLB token with symbol tRKLB to cross-chain token configurations.
  • Updated production token listings and deployment records to include the new token.

[coderabbitai]

📝 Walkthrough

Walkthrough

The production token configuration and invariant tables now contain 29 entries. RKLB is added with its receipt-vault metadata and Base contract constants, while the Ethereum table is populated with pinned addresses and includes the RKLB entry.

Changes

Production token expansion

Layer / File(s)	Summary
Add RKLB production configuration src/lib/LibProdTokenConfig.sol	The configuration table grows to 29 entries and adds RKLB with its receipt-vault name and symbol.
Synchronize Base and Ethereum token inventories src/lib/LibTokenInvariants.sol	Base constants and token arrays include RKLB, and the Ethereum table is expanded to 29 pinned deployed token instances.

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

Possibly related PRs

• S01-Issuer/st0x.deploy#230: Introduced the production token tables that this change extends.
• S01-Issuer/st0x.deploy#228: Refactored the token-table-based invariant machinery.
• S01-Issuer/st0x.deploy#263: Expanded the Base production-token inventory with another pinned token entry.

Suggested reviewers: thedavidmeister, thedavidmeister

Poem

I’m a rabbit with RKLB in sight,
Adding one token to tables so right.
Base holds its vaults, Ethereum its row,
Twenty-nine entries now neatly glow.
Hop, deploy, and let the addresses flow!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main changes: hydrating the Ethereum token table and adding RKLB to the canonical token set.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch pin/ethereum-token-table

---

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]

• pin(tokens): hydrate the Ethereum token table + add RKLB to the canonical set #259 : 2 dependent PRs (#270 , #271 ) 👈 (View in Graphite)
• feat(script): deploy the Ethereum production tokens via the deploy key, matched to Base #231 : 1 other dependent PR (#257 )
• test(parity): cross-chain deployment parity pin + scheduled CI #230
• pin(ethereum): hydrate the V4 authoriser clone address #258
• feat(deploy): Ethereum V4 authoriser clone — chain-parametric deploy script + per-chain pin selector #229
• feat(tokens): add MU/AMD/AVGO/AMAT/LRCX/TTWO to the Base production token list #265
• fix(test): assert ownership of the IN-USE production beacons per chain #266
• feat(lib): chain-aware token-owner Safe assertion #267
• fix(test): retire executed-migration simulations, repoint authoriser truth #268
• main

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

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

src/lib/LibTokenInvariants.sol (1)

335-345: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Stale doc counts and placeholder narrative after the 28→29 hydration. The tables were expanded to 29 and the Ethereum table fully hydrated, but surrounding documentation still describes the old 28-entry, all-placeholder state, which now contradicts the code.

• src/lib/LibTokenInvariants.sol#L335-L345: productionTokensEthereum docstring still declares the table is **ALL PLACEHOLDERS** (address(0)) and "28 production token instances" — rewrite to reflect the pinned/deployed 29-token state (the @return at L345 also still says 28).
• src/lib/LibTokenInvariants.sol#L296-L301: the @return for productionTokensBase still says "28 production token instances on Base"; update to 29.
• src/lib/LibProdTokenConfig.sol#L44-L45: the @notice still says "28 production token deploy configs"; update to 29.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/lib/LibTokenInvariants.sol` around lines 335 - 345, Update documentation
for the 29-token hydrated state: in src/lib/LibTokenInvariants.sol lines
335-345, revise productionTokensEthereum’s notice to describe pinned/deployed
entries, remove the all-placeholders narrative, and change the return count to
29; in src/lib/LibTokenInvariants.sol lines 296-301, change
productionTokensBase’s return count to 29; and in src/lib/LibProdTokenConfig.sol
lines 44-45, change the production token deploy config count to 29.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@src/lib/LibTokenInvariants.sol`:
- Around line 335-345: Update documentation for the 29-token hydrated state: in
src/lib/LibTokenInvariants.sol lines 335-345, revise productionTokensEthereum’s
notice to describe pinned/deployed entries, remove the all-placeholders
narrative, and change the return count to 29; in src/lib/LibTokenInvariants.sol
lines 296-301, change productionTokensBase’s return count to 29; and in
src/lib/LibProdTokenConfig.sol lines 44-45, change the production token deploy
config count to 29.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 476827d9-a8dc-4cf5-af15-aeee7a8ef7ef

📥 Commits

Reviewing files that changed from the base of the PR and between 567d7e6 and 844f488.

📒 Files selected for processing (2)

• src/lib/LibProdTokenConfig.sol
• src/lib/LibTokenInvariants.sol

[thedavidmeister]

Reviewed 844f488: approve

Fresh run 29984980625 (06:25 UTC, after the Safe bumped RKLB's Base authoriser) leaves one test failure — testDeployTag (0_1_8 != 0_1_22) — plus git-clean. Both inherited main-red. The three ReceiptVaultAuthoriserMismatch failures from the earlier run are gone.

The Ethereum hydration verified against mainnet, not taken from the broadcast log. I sampled four rows — first, middle, last, and RKLB — and all four are clean:

row	owner	authorizer	receipt	wrapped.asset
[0] MSTR	ok	ok	ok	ok
[13] QQQM	ok	ok	ok	ok
[27] TTWO	ok	ok	ok	ok
[28] RKLB	ok	ok	ok	ok

Every sampled receipt vault is owned by the Ethereum Safe, wired to the Ethereum V4 clone, its receipt() matches the pinned receipt, and each wrapped vault's asset() points back at its vault. Zero mismatches.

RKLB was the interesting part of this review. Its Base receipt vault 0xf6744Fd9… was still on the V3-era authoriser 0x35f9fA9d… when this PR was opened, so adding it to productionTokensBase() enrolled it in the uniform-authoriser invariant it was failing. That has now been fixed on-chain rather than in the test — I read 0x315b16… on three independent Base RPCs before this run.

Worth recording for whoever picks up the RKLB thread: it is absent from st0x.registry's Base token list, st0x.liquidity disables trading/rebalancing/recovery for it, and st0x.issuance references it only from a test fixture — while st0x.pricing notes the oracle server already resolves orders to it. So "an accidental omission from every table in this repo" is not quite the whole story; its absence from the canonical registry looked deliberate. st0x.registry#42 adds it with a new test tag so that status is expressible rather than inferred from an absence, since without it productionReceiptVaults() returning 29 against the registry's 28 would render as a permanent "governed vault not in the registry" discrepancy on the health dashboard.

This also arms the last pending leg of the cross-chain parity suite: with the Ethereum token table hydrated, testCrossChainParity should log no PARITY PENDING at all and compare all three legs on both chains for the first time.