Every transaction,
with its reason.
Two keys run this project. Everything they have ever signed is below, in order, each one linked to the chain so you can check that the description matches what happened. Nothing is left out: a script compares this page against both accounts on every run, and it fails if the chain knows a transaction this page does not.
klv1…5y0nrzIssued GOHAN-SUTV and owns the asset. Holds the supply that has not been distributed.
klv1…2r8geqDeployed and owns the claim vault, its break-glass twin and the token factory. Owns no tokens.
- Token owner
The fee pool is funded
Ten thousand KLV, about three thousand transfers. A wallet holding GOHAN and no KLV can now transact, which it could not do at all before: even swapping GOHAN for KLV needs a fee in KLV.
- Token owner
The fee pool is switched on
One KLV of network fee costs 720 GOHAN, which was 50% above the market that day. Holders can pay their fees in rice; what the pool collects will be withdrawn and burned.
fee 4.00 KLV159873685d9d22ce… - Token owner
The key is topped up
Ten thousand KLV, from the owner’s own funds, to fill the fee pool below.
- Token owner
The settlement, 0.5% of the supply
Paid to the account that surrendered the legacy asset, under section 12.3 of the migration plan. It is excluded from the airdrop, and the plan records how the payment differed from what was written: there was no liquidity pool to put it in yet, so it went to the address directly.
- Token owner
The vault is funded with 40 billion
The migration pool, out of the owner’s hands and into a sealed contract that pays it out by proof. This is the transaction that made the claim real.
- Contracts owner
The claim list is written into the vault
The Merkle root of the 1,392 rows, set once. The contract refuses a second root, and it was sealed before this, so nobody can replace the list, including us.
fee 10.13 KLV3713468f876a7b32… - Token owner
GOHAN-SUTV is issued
One transaction, a thousand KLV to the factory, a hundred billion GOHAN back. The flags were fixed in this instant and can never be edited: no mint, no wipe, no pause. Whatever the supply is now is what it will always be.
- Token owner
The key is topped up
Two thousand KLV: the factory charges a thousand to issue, and the rest paid the fees.
- Token owner
Ten KLV, sent as a test
The first transaction this key ever signed, to prove the key worked before it was trusted with a hundred billion tokens.
- Token owner
The key is funded
A thousand KLV, to pay for issuing the token.
- Contracts owner
The break-glass twin is deployed
A second contract carrying the vault’s bytecode and holding nothing. If we delete it, the vault stops answering at once, which is the only emergency stop the migration has, meant for the day something is detected that must be stopped mid-flight. Only its own owner can delete it: a stranger deleting their own copy of the same bytecode was tested and left the vault untouched. Nothing is lost either way, and redeploying the same bytecode brings the vault back with its state and its 40 billion intact.
fee 210.02 KLV317b83e3cdda48ec… - Contracts owner
The key is topped up
Two and a half thousand more, for the twin below and the root.
- Contracts owner
The key is topped up
Five hundred KLV.
- Contracts owner
The vault is sealed
One minute after the deploy, and the order matters: sealed before the root was set, so that "the list cannot be changed" is a fact about this account and not a promise about our intentions. Nobody can upgrade this contract now, ourselves included.
fee 210.11 KLVa4e2851e9dea9b0f… - Contracts owner
The claim vault is deployed
The contract that pays out the migration. It was deployed from a container build, so a stranger can rebuild the same bytecode and compare it with the chain.
fee 210.02 KLV2a5ecc76d862ba2c… - Contracts owner
Factory upgrade
The last of them. After this the factory could issue the token the plan called for.
fee 251.16 KLV0136c4196190c2a8… - Contracts owner
Factory upgrade
Same work, next revision.
fee 246.26 KLV9943e6203ec66334… - Contracts owner
Factory upgrade
Same work, next revision.
fee 246.43 KLVcff8d9c8c0a5048d… - Contracts owner
Factory upgrade
Same work, next revision.
fee 252.65 KLV2069adb3814ba3fb… - Contracts owner
Factory upgrade
Same work, next revision.
fee 241.27 KLV297a397ff57d4e0c… - Contracts owner
Factory configuration
A call rather than an upgrade, which is why it cost seven KLV instead of two hundred.
fee 6.98 KLV92719a54f90079df… - Contracts owner
Factory upgrade
Same work, next revision.
fee 240.91 KLV371e499fd487d852… - Contracts owner
The key is topped up
Three thousand KLV, because each factory upgrade costs about 240 and the key was running out.
- Contracts owner
Factory upgrade
Same work, next revision.
fee 240.04 KLVed2294e2fcaf2922… - Contracts owner
Factory upgrade
Same work, next revision.
fee 232.91 KLVb440357229fd6045… - Contracts owner
Factory upgrade
One of nine upgrades that day and the next, while the factory was being made to issue the token the design required.
fee 234.33 KLV35f3ec58e9b3addd… - Contracts owner
The token factory is deployed
The contract that issues KDA tokens for anyone, GOHAN-SUTV among them.
fee 236.45 KLV799cc7a9ed2169cd… - Contracts owner
The snapshot is committed on chain
A zero-value transfer to the burn address carrying block H, its hash, the Merkle root and the checksum of the manifest. Everything the migration owes anybody was fixed by this transaction, before the result was published.
- Contracts ownerfailed, fee still paid
The commitment, refused
The first attempt to write the snapshot commitment on chain. It failed and cost the fee; the next one, a minute later, is the real one.
fee 5.22 KLVd91ce3aecabbaec1… - Contracts owner
The key is funded
A thousand KLV arrives to pay for what follows. The key held nothing before this.
30 transactions, 3475.60 KLV of fees paid so far. The token owner also holds the supply that has not been distributed; where it is meant to go is on the tokenomics page, and what each address is on the facts page.