Overview

TNT is distributed via a one-time migration from the legacy (Substrate) chain to Tangle’s EVM deployment.

The canonical distribution inputs are produced from an audited snapshot and published alongside the deployment (Merkle root, totals, and carveouts).

To verify:

• Snapshot metadata is checked into dapp/scripts/migration/tangle_migration_snapshot_8116528.json.
• You can independently query the legacy chain RPC for the block hash at 8116528 (e.g. chain_getBlockHash(8116528)).

What’s Included

TNT distribution is built from three artifact types:

• Substrate claims (SS58): a Merkle tree of (pubkey, amount) entries, claimed on EVM via TangleMigration using an SP1/ZK proof of key ownership.
• EVM claims (0x…): an explicit recipient list used for a batch airdrop distribution.
• Carveouts: allocations intentionally removed from the claim set and transferred at deploy time.

Claimable Substrate Allocations

For Substrate snapshot holders, TNT is claimed on EVM through the on-chain migration contract:

• The claim is validated by (1) a Merkle proof and (2) a ZK proof that the claimant controls the Substrate public key.
• By default, claims are split into 10% unlocked (transferred immediately) and 90% locked in a per-recipient cliff lock until the configured unlock timestamp (commonly deployTime + 180 days).

Carveouts (Non-Claimable → Fully Liquid at Deploy)

Some allocations cannot (or should not) be claimed via the Merkle/ZK flow, so they are removed from the Merkle tree and transferred during deployment:

• Treasury carveout: legacy Substrate module accounts (pubkeys starting with modl…) do not have private keys, so they are non-claimable and are transferred to the EVM treasury recipient at deploy.
• Foundation carveout: the foundation allocation (tangle-foundation, ≈15.04M TNT) is transferred to a designated EVM recipient at deploy and is fully liquid at launch.

Configuration Notes

The lock configuration (unlock timestamp and unlocked/locked split) can be configured before the first claim. After claims begin, parameters are fixed to prevent changing terms mid-stream.

Distribution Table