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.
Choose an integration path
Lifecycle boundary
Robinhood Chain uses one Uniswap V3 pool from launch onward:
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:
- assert the RPC-reported chain ID;
- load an approved deployment manifest and matching ABI manifest;
- verify runtime code and immutable contract relationships;
- read mutable launch, DEX, fee, and compounding policy;
- 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. 
Solana
Robinhood Chain