Skip to main content
Quickstart · Data API · Financial equations

Execution profile

Pin kaia-earnusdt-2026-07 in the integration release.
  • Disable writes on any profile mismatch. Upgrade addresses and ABIs through a reviewed integration release.
  • Use chain-qualified IDs from the Data API for data joins.

Minimal ABIs

Quotes and minimum output

For quoted output q in raw token units and chosen slippage tolerance s in basis points:
  • Set tolerance through an explicit product/user policy; refresh the quote before signing.
  • Use integer arithmetic. A 100 bps tolerance equals 1%.
  • Validate chain, wallet balance, allowance and KAIA for gas before submission.

Deposit

Cautions
  • Stop an attempt after a rejected signature. Offer approve-plus-deposit as a separate user action.
  • User-facing deposits and redemptions MUST use the Router.
  • Retain receipt amounts and transaction hashes for reconciliation.

Redemption

Cautions
  • Quotes and headroom can change before inclusion. Preserve transaction failures for the user to review.
  • Queue shares uses seCDV units; filled EarnUSDT comes from the Router receipt.
  • Keep request IDs scoped to their queue contract and chain.

Claim lifecycle

  • The keeper normally settles fully funded requests, including before cooldown expiry.
  • Earlier FIFO requests reserve liquidity first. Funding gaps can persist after expiry.
  • Each claimability observation carries basis: fully_funded_fifo, maxLossBps: 0, observedAt and blockNumber.

Optional direct claim

Cautions
  • A direct-claim client MUST simulate immediately before submission. Clock status and previewClaim alone provide insufficient execution evidence.
  • A ready observation can change before transaction inclusion.
  • SHOULD_WAIT, INSUFFICIENT_ASSETS or EXCESSIVE_LOSS requires a fresh user decision; preserve the selected tolerance.

Release checks

  • Test decimals, partial evidence, cursor continuation and inactive holdings.
  • Test rejected signatures, allowance, gas, debt-cap races and partial fills.
  • Test early funding, post-cooldown funding gaps, FIFO reservations and claimed receipts.
  • Save API request IDs, observation times and transaction hashes for support.