Mainnet deployment plan

This page describes how KIMP is deployed on GIWA mainnet. The date is to be announced. The sequence is rehearsed end to end on GIWA Sepolia first, and every step leaves on-chain evidence.

Four principles apply. Contracts deploy from a public script. The deployer keeps no lasting power. Every parameter, including the initial ones, passes the 48-hour timelock. Markets open only after the index has run cleanly.

Order of operations#

1. 1Guardian Safe. Create the 4-of-7 Safe on GIWA mainnet. Publish the seven signer addresses and the threshold. Its only role is pause.
2. 2Timelock and governor. Deploy the timelock with a 48-hour minimum delay and the governor. The governor is the permanent proposer. The deployer is a temporary proposer. Execution is open to anyone.
3. 3$KIMP token. Deploy the fixed-supply token. The full 1,000,000,000 supply is minted once to the fair launch contract, the incentives rewards contract, the treasury timelock and the contributor vesting contract, in the amounts listed in Distribution.
4. 4Core contracts. Deploy in dependency order: KimpIndex, KimpReporterRegistry, KimpVerifiedGate, KimpPool, KimpStaking, KimpBuyback, then KimpMarket.
5. 5Wiring. Connect the contracts: registry into index, index, pool and gate into market, market into pool, staking and buyback. References known at construction are immutable constructor arguments. Circular references are set through one-time initializers that lock after the first call. KimpVerifiedGate receives the mainnet DojangScroll address and Upbit Korea attester ID published by GIWA as immutable constructor arguments.
6. 6Roles. Set the timelock as owner of every setter and the guardian Safe as pause role. Confirm the deployer holds no role on any core contract.
7. 7Source verification. Verify the source of every contract on the GIWA explorer. Publish the address list in these docs and on X at @KimpGiwa.
8. 8Initialization batch. The deployer schedules one timelock batch containing all launch parameters. The batch is public for 48 hours before it can execute.
9. 9Market-open operation. The deployer schedules a second operation that switches markets from reduce-only to active. It has the initialization batch as predecessor and a longer delay, so it cannot execute first.
10. 10Renounce. The deployer renounces its temporary proposer role. From this point only the governor can propose.
11. 11Fair launch. The $KIMP fair launch contract opens on launch day, with the mechanism and parameters published beforehand. There is no presale and no whitelist.
12. 12Reporter onboarding. Once the initialization batch executes, reporters bond $KIMP, acquired on the same terms as everyone, and begin submitting.
13. 13Index warm-up. The index publishes every 60 seconds. Markets remain reduce-only, so no exposure can be opened.
14. 14Markets open. When the market-open operation matures and the go-live checks pass, anyone executes it. The guardian can hold markets paused if a check fails.

Initialization batch contents#

Go-live checks#

After opening#

The bug bounty opens at mainnet. Later changes go through governance. See the Roadmap.