Technical FAQ

Two contracts, both on Ethereum mainnet: KolanHook, the Uniswap v4 hook that holds the liquidity and the windows, and KolanToken, the token it deployed. Their source is verified on Sourcify, and the three files it is built from, KolanHook.sol, LiquidityBook.sol and KolanToken.sol, are byte for byte the ones in the public repository.

No. There is no owner, no admin key, no proxy and no pause. The parameters are fixed in the constructor, and the hook reverts any attempt by someone else to open a pool on it, add liquidity, remove it or donate. The hook moves its own positions only to open and close windows.

In block 26,148,271, in four transactions. The first deploys the hook, which deploys the token with its whole supply, 1,000,000 KLN. The second, launch, opens the pool at a $10,000 market cap with the whole supply in it and no ETH; the deployer sends 1,000 wei and never holds a token.

The last two are plain swaps from two of the team's wallets, 0.1 ETH each, for about 4.75% of the supply between them. They had no window, and nothing locks those tokens.

Yes. Over 4,100 transactions had paid it by the snapshot. It is booked during the swap as ETH owed to DEV, and anyone can call claimDev to send it there. It had been claimed four times. The dev receives nothing else: no token, no liquidity, no window's ETH or premium.

Yes. 35 windows had been opened by the snapshot: 19 undone, 11 kept, 5 not closed yet. Window #3 is the home page's example: 0.5 ETH spent on tokens and 0.05 ETH of premium, for a six-hour window.

Yes. cancel sends the owner exactly the ETH the window spent on tokens, in the same transaction, and puts the tokens back into the pool. For window #14, the eth field of its WindowOpened event and the transfer its undo made back to the owner are the same amount, both read from the one value the hook stored. The tax and the premium are not refunded.

Both have run on mainnet: ten windows were kept before their end and one received after it. The tokens went to the owner and the ETH into the pool. Every one so far was sent by the window's owner; a third party sending it after the expiry is the same function, and no one has needed to yet.

Yes. When a window closes, undone or kept, its premium buys KLN from the pool and the hook burns them; the amount is in the burned field of every WindowClosed event. By the snapshot, 8,763.67 KLN had been burned this way, and the supply was 991,236.33 KLN instead of 1,000,000.

For plain swaps, yes: the pool is an ordinary v4 pool. Over 4,100 swaps had gone through it by the snapshot, through Uniswap's Universal Router and many other contracts, each paying the tax.

The hook keeps the ETH and tokens of every open window in held, and every buy, cancel and accept ends by checking it still holds at least that much. A transaction that would leave it short reverts.

Yes, on Ethereum since 10 October 2026. Anyone launches a token in one transaction: it opens on its own Uniswap v4 pool with the whole supply in it and liquidity nobody can pull, and any purchase of it can carry a window, as on Kolan.

Each launch is a Kolan hook of its own. The 1% fee goes half to the token's dev and half to the launchpad's treasury, in ETH. Each premium buys back KLN on Kolan's pool with one half and the token with the other, and burns both. Its how it works page has the detail. Like Kolan, it is tested and not audited.

Not yet. These integrations are the step after the launchpad, and they are being built now, through an open SDK; none is live today. Until then, a window opens from this app, from the launchpad, or from any contract or script that calls buy on a hook.

That is the long-term aim: any token on Ethereum trading on Kolan's hook, so that any purchase of it can come with a window. Every window, wherever it opens, would feed the KLN buyback. Nothing is built for it yet.