Skip to content

ops: testnet round trip per chain (Sepolia, BSC testnet, Nile, devnet) before mainnet #2

Description

@dendisuhubdy

From the 2026-09-17 security review and the pre-deploy audit's before-mainnet list. Each endpoint should be deployed through its script and exercised lock → attest → mint → burn → release, then a guardian-set rotation, before any mainnet deployment:

  • Sepolia via deploy/eth.sh
  • BSC testnet via deploy/bnb.sh
  • Tron Nile via deploy/trx.sh — the only environment that exercises the TVM assumptions the Foundry suite cannot: ecrecover returning the 0x41-prefixed address form the migration stores as guardian keys (tron/migrations/2_deploy.js), the zero-address form in _checkKeys, SELFDESTRUCT availability for SafeTransfer's code check, and the deliberately no-op fork guard. A wrong assumption fails closed (every release reverts WrongGuardian), but on mainnet that means releases and rotations bricked until a governance rotation and possible redeploy.
  • Solana devnet via deploy/sol.sh — needs the Solana CLI for cargo build-sbf (unexercised on the build machine so far). Also confirm the release transaction fits the 1,232-byte packet limit at the launch guardian-set size (about seven signatures of headroom with the current account list).

The guardian/relayer daemon issue tracks the end-to-end loop; this issue tracks the per-chain deployment and contract-level round trips that precede it.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions