Kaito

Kaito withdrawals are sKAITO redemption requests settled through Base

Kaito withdrawals are completed by unstaking sKAITO on Base, waiting seven full days and submitting a separate withdrawal transaction that releases KAITO to the chosen address. The first transaction starts the cooldown and records the KAITO amount; it does not deliver spendable tokens. After the timer matures, the Withdraw action claims the locked balance. Both steps require a Base-compatible wallet with ETH for gas, while the cooldown itself does not charge a time-based fee.

Bottom line: They are the final step in the staking exit flow, releasing KAITO on Base after users unstake sKAITO, complete the seven-day cooldown, and submit the withdrawal transaction.

From sKAITO balance to a completed KAITO claim

The native workflow converts sKAITO into a pending KAITO claim, waits seven days and then releases that amount on Base. It spans two transactions.

Start the cooldown

Open the Kaito staking portal with the wallet that holds sKAITO and select Unstake. The wallet must be connected to Base Mainnet, identified by chain ID 8453. MetaMask, Rabby and Coinbase Wallet can display Base accounts and request the signature. Review the sKAITO quantity and the previewed KAITO output before signing. Once Base confirms the call, the vault burns the selected shares, sends the corresponding KAITO into the AgingPool contract and records a pending claim for the same wallet.

Wait for maturity

The Kaito staking flow sets the cooldown at 7 days, equal to 168 hours or 604,800 seconds. The contract measures that interval from the Base block timestamp recorded by the cooldown transaction. Closing the portal, disconnecting the wallet or switching devices does not pause the clock. A wallet interface may round its countdown, so the onchain cooldownEnd timestamp decides the first valid claim moment. The contract design allows an administrator to configure a nonzero cooldown up to a 90-day maximum, while Kaito presents the seven-day setting for its native exit flow.

During this interval, the pending KAITO remains locked in AgingPool. It is no longer a transferable sKAITO balance in the wallet.

Claim the locked KAITO

Reconnect the same Base account after maturity and select Withdraw. That action calls claimFromAP and asks for a recipient address. The second signature pays Base gas and releases the recorded KAITO from AgingPool. A successful receipt produces a Claim event and the ERC-20 KAITO balance appears at the recipient. BaseScan or Blockscout can confirm the transaction independently of the portal display. At this point the staking exit is complete; moving KAITO to another Base address or bridging it to Ethereum is a separate operation.

Portal controls and direct contract calls

The Kaito portal wraps the same ERC-4626 exit functions that advanced users can call directly on Base. Direct access changes the interface, not the cooldown.

The portal path suits ordinary wallet use because it assembles calldata and previews the conversion. At contract level, cooldownShares accepts an exact share amount and uses previewRedeem to calculate assets. cooldownAssets starts from the desired KAITO amount and uses previewWithdraw to determine the shares burned. The OpenZeppelin ERC-4626 preview methods make these dimensions explicit. Neither direct method accelerates Kaito withdrawals: each writes the same cooldown record and transfers underlying assets to AgingPool before a later claimFromAP call.

sKAITO also follows ERC-20 transfer mechanics, so sending shares to another Base address moves the staked position without starting an exit. The ordinary ERC-4626 withdraw and redeem entry points work only when the configurable cooldown equals 0. With the active seven-day setting, users start through cooldownShares or cooldownAssets. Staying staked requires 0 exit transactions and preserves the value-accruing share position until a cooldown begins.

How much KAITO will the withdrawal release?

The claim releases the KAITO amount recorded when the cooldown transaction converts sKAITO shares into underlying assets. That amount becomes fixed before the wait.

Share-denominated exits

cooldownShares passes the selected sKAITO quantity through previewRedeem at the current vault conversion rate. That rate reflects rewards already accrued to the staking contract, so a share may represent a different KAITO amount than at deposit. Rewards accrue through the share value; there is no separate reward claim before unstaking. KAITO and sKAITO both use 18 decimal places, so one displayed token equals 1,000,000,000,000,000,000 base units. Wallets format those integers for display, while the contract performs the conversion with integer arithmetic.

Asset-denominated exits

cooldownAssets starts with a requested KAITO asset amount and uses previewWithdraw to calculate the sKAITO shares required. ERC-4626 rounding rules protect the vault by rounding share requirements in the necessary direction. This path is useful when the output target matters more than spending a precise share balance. The vault also enforces a 1 sKAITO minimum total supply whenever supply remains nonzero. That rule concerns the vault-wide remainder, not a one-token minimum for every Kaito withdrawal.

After either cooldown function runs, the assets leave the value-accruing vault and enter AgingPool as locked KAITO. Later reward distributions change the remaining sKAITO conversion rate, not the already recorded lockedAmount. The final claim therefore matches the stored amount, subject only to the token's 18-decimal precision. A partial exit leaves the unselected shares staked, while a full exit burns the wallet's selected balance.

The two gas payments on Base

Kaito withdrawals require two gas-paying Base transactions: one to start cooldown and one to claim KAITO. Both use ETH on chain ID 8453. Each Base fee has 2 components, the L2 execution charge and the L1 security charge tied to publishing data on Ethereum. Kaito does not publish a separate time-based withdrawal fee, and the seven-day interval itself adds no recurring gas charge. The wallet estimate changes with EIP-1559 conditions and Ethereum data costs.

Reading the onchain record when Withdraw stays unavailable

The onchain cooldown record shows whether the claim is immature, mature or already collected for the connected address. Two stored values control that state.

Cooldown state

The public cooldowns(address) view returns cooldownEnd and lockedAmount. Its 2 fields use a 104-bit timestamp slot and a 152-bit token-amount slot. When the current Base timestamp remains below cooldownEnd, claimFromAP reverts with ClaimNotMature. Once the timestamp reaches the stored value, the call releases lockedAmount to the chosen recipient. A zero lockedAmount after a successful claim means no pending balance remains in that record. Reading these fields does not require a gas-paying transaction because it is a view call. The Withdraw button reflects this contract state; refreshing the page cannot alter either stored value.

Receipts and token balances

BaseScan and Blockscout expose the CooldownStarted and Claim events for each confirmed call. CooldownStarted carries 3 relevant values: the holder, KAITO assets and sKAITO shares. Claim records the holder, recipient and amount. An EVM address contains 20 bytes, rendered as 40 hexadecimal characters after the prefix. A transaction hash contains 32 bytes, rendered as 64 hexadecimal characters after its prefix. Matching the full address and hash prevents confusion between the wallet account, staking contract and recipient.

A later unstake request

Each wallet address has 1 cooldown record rather than a separate queue of independent timers. Starting another cooldown updates cooldownEnd to the new transaction time plus the configured duration, then adds the new assets to the existing lockedAmount. Because the single timestamp covers the combined amount, a later unstake request restarts the wait for KAITO already pending under that address. Claim a mature amount before opening another cooldown when preserving the earlier release time matters.

When the native seven-day exit route fits

The native route fits holders who want KAITO on Base and accept a seven-day liquidity gap. It supports partial or full exits and uses 2 signatures. The choice changes when transferable sKAITO remains more useful, because starting cooldown burns those shares and fixes the KAITO claim.

What to know about Kaito withdrawals