Protocol Deployment (tnt-core)
This page is for protocol and infrastructure engineers deploying the Tangle EVM contracts. Blueprint operators do not need these steps for day to day service operation.
The source of truth for deployment is the tnt-core repo, which uses Foundry scripts and writes manifest JSON outputs
for downstream tooling.
Source of Truth
What To Document in Runbooks
If you operate a production environment, keep these items in your internal runbook so deployments stay reproducible:
- the
FULL_DEPLOY_CONFIGJSON you used (and any env var overrides) - the manifest output path and the produced manifest JSON
- role handoff targets (timelock, multisig, treasury) and whether bootstrap roles were revoked
- any cross-chain slashing wiring (Hyperlane or LayerZero) and the connector and receiver manifests. On
L2SlashingReceiver, the bootstrapsetMessenger/setSlashercalls (when the current value isaddress(0)) take effect immediately. Subsequent rotations are timelocked: the owner queues the new address withsetMessenger/setSlasher, then callsactivateMessenger()/activateSlasher()afterSENDER_ACTIVATION_DELAY(2 days) elapses. Document the queue/activate pair as two transactions in your runbook so operators know to schedule the activation tx before the delay window closes.
Related Docs
- Protocol architecture overview:
/developers/protocol-architecture - Network parameters and contract addresses:
/network/network-parameters