Skip to content

chore: pre-generate v6.0.0 freeze Safe batches for mainnets#80

Open
fakedev9999 wants to merge 1 commit into
mainfrom
fakedev9999/v6.0.0-freeze-safe-batches
Open

chore: pre-generate v6.0.0 freeze Safe batches for mainnets#80
fakedev9999 wants to merge 1 commit into
mainfrom
fakedev9999/v6.0.0-freeze-safe-batches

Conversation

@fakedev9999
Copy link
Copy Markdown
Member

Pre-generates the four mainnet Safe batch JSONs to freeze the v6.0.0 routes (Groth16 selector `0x0e78f4db`, Plonk selector `0xbb1a6f29`) on the Group A multisig gateways.

Generated via:
```
node script/utils/generate-safe-batch.js --version=v6.0.0 --action=freeze
```

Each batch holds 2 `freezeRoute(bytes4)` calls (Groth16 gateway + Plonk gateway). Files:

  • `safe-batches/1_freeze_v6_0_0.json` — Ethereum
  • `safe-batches/10_freeze_v6_0_0.json` — Optimism
  • `safe-batches/42161_freeze_v6_0_0.json` — Arbitrum
  • `safe-batches/8453_freeze_v6_0_0.json` — Base

Network is already on SP1 v6.1.0 (#75 rolled out), so v6.0.0 routes are dead and ready to freeze. Multisig signers can upload these directly to Safe Transaction Builder; no script run needed on their side.

Tracking issue: succinctlabs/apps-ops#3

Generated via 'node script/utils/generate-safe-batch.js
--version=v6.0.0 --action=freeze'. Each batch contains 2 txs:
freezeRoute(0x0e78f4db) on the Groth16 gateway and
freezeRoute(0xbb1a6f29) on the Plonk gateway.

Network is already on SP1 v6.1.0; v6.0.0 routes are deprecated and
ready to be frozen via the multisig signers. Files:
- 1_freeze_v6_0_0.json     (Ethereum)
- 10_freeze_v6_0_0.json    (Optimism)
- 42161_freeze_v6_0_0.json (Arbitrum)
- 8453_freeze_v6_0_0.json  (Base)

Tracking: succinctlabs/apps-ops#3
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