Skip to main content
KEK.PRO launches on Robinhood Chain are self-describing onchain. You can build from contract events and direct reads. The KEK.PRO EVM SDK provides typed transaction builders and exact arithmetic without replacing the chain as the final authority.
The repository contains a Robinhood Chain mainnet profile, but it does not contain a KEK.PRO mainnet deployment manifest. The only checked-in KEK.PRO EVM deployment is a historical development manifest for Robinhood Chain testnet. Do not enable mainnet writes without an approved, verified release.
Integration surfaces / authority mapCanonical state ยท typed construction
AuthorityContracts + eventsCanonical launch, market, custody, and lifecycle state.
ReadsDirect RPCToken, pool, factory, locker, and fee-right state.
ClientTypeScript SDKWallet transaction builders, ABIs, and exact math.
PrecisionAtomic valuesInteger amounts and Q64.96 prices stay exact.
Bind every read and write to one verified chain, contract release, and ABI set.

Choose an integration path

Lifecycle boundary

Robinhood Chain uses one Uniswap V3 pool from launch onward:
Integrator lifecycle boundaryPersistent venue identity
01LaunchDiscover token and canonical pool
02Protected V3Apply the configured opening policy
03CheckpointRead live and latched state separately
04Same poolKeep indexing the original venue
There is no bonding curve, migration event, replacement venue, or normal LP withdrawal path.
There is no bonding curve, migration event, second liquidity venue, or normal LP withdrawal path. The launch position NFT remains in KekproLaunchLocker. TGE is an irreversible checkpoint. It does not automatically change the live fee allocation. Read pricing and TGE before mapping lifecycle state.

Configuration first

Before reading or writing:
  1. assert the RPC-reported chain ID;
  2. load an approved deployment manifest and matching ABI manifest;
  3. verify runtime code and immutable contract relationships;
  4. read mutable launch, DEX, fee, and compounding policy;
  5. disable writes when any authority disagrees.
Do not borrow addresses or settings from another chain. Do not treat reviewed defaults as immutable protocol constants.

Integration map

Safety and attribution

Treat creator metadata as untrusted input. Keep addresses chain-qualified. Preserve atomic integers until display formatting. Require user-selected slippage and deadlines for trades. Read the security model and the KEK.PRO Terms of Service. Onchain data and public interfaces do not imply endorsement, partnership, or token quality.
Last modified on August 2, 2026