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:
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.
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:
deploy/eth.shdeploy/bnb.shdeploy/trx.sh— the only environment that exercises the TVM assumptions the Foundry suite cannot:ecrecoverreturning the0x41-prefixed address form the migration stores as guardian keys (tron/migrations/2_deploy.js), the zero-address form in_checkKeys,SELFDESTRUCTavailability forSafeTransfer's code check, and the deliberately no-op fork guard. A wrong assumption fails closed (every release revertsWrongGuardian), but on mainnet that means releases and rotations bricked until a governance rotation and possible redeploy.deploy/sol.sh— needs the Solana CLI forcargo 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.