Skip to main content
The maintained Node SDK exports EVM support under the additive evm namespace. Existing Solana exports remain separate.
TypeScript SDK / EVM namespaceOne chain per client · wallet-free core
ABIsVersioned interfacesFactory, token, locker, fee-right, pool, and router definitions.
BuildersWallet transactionsLaunch, swap, fee-right, and limit-order payloads.
Precisionbigint boundariesAtomic contract values stay exact across reads and writes.
ChainsTyped identityRobinhood Chain profiles stay explicit at every boundary.
Builders return transaction requests. Your wallet remains responsible for signing and submission.

Install

The checked-in package version is 1.0.0 and pins viem 2.55.8.
@kekpro/integration-sdk is the checked-in package identity. Confirm the approved distribution channel and release version for your environment before installing it in a separate project.

Use the EVM namespace

The public EVM surface includes:
  • versioned contract ABIs;
  • Robinhood Chain descriptors;
  • exact fixed-point and atomic-amount helpers;
  • pure wallet transaction builders;
  • transaction and contract-state types.
Use direct RPC reads for canonical contract state. Bind each client to the expected chain ID before reading or building a transaction.

Read canonical state

Cross-check token, factory, pool, and locker relationships before treating a contract as a KEK.PRO launch.

Keep amounts exact

Keep contract-sized integers as bigint.
Never pass a balance, Q64.96 price, token supply, timestamp, or nonce through JavaScript Number.

Build wallet transactions

Transaction helpers are pure. They return:
Available builders cover:
  • launch and TGE checkpoint;
  • position-fee collection;
  • fee-right auctions, bids, claims, listings, purchases, and closure;
  • ERC-20 approval;
  • exact-input V3 swaps;
  • WETH wrapping and unwrapping;
  • limit-order nonce cancellation.
The caller chooses slippage, deadline, account, nonce, and broadcast policy.

Launch example

Simulate the returned request from the sending account before broadcasting.

Fee-right example

Re-read the active round and allowance between approval and bid submission.

Safety rules

  • Pin the SDK, ABI, manifest, and protocol versions together.
  • Reject unsupported chain IDs.
  • Re-read mutable policy immediately before writes.
  • Show exact addresses and values in wallet confirmation.
  • Preserve transaction receipt and canonical event identity.
  • Never add implicit slippage or silently change a user’s deadline.
Last modified on August 2, 2026