Skip to main content
Use a versioned deployment manifest as the address source. Never copy KEK.PRO addresses from screenshots, transaction descriptions, or an unqualified environment variable.
Contract topology / responsibility boundariesManifest-pinned addresses + ABI hashes
CreateFactory + deployerDeterministic token, pool, configuration, and launch records.
MarketToken + V3 poolFixed supply, metadata, restrictions, and canonical swaps.
CustodyLocker + compounderPermanent position custody and retained-fee policy.
RightsAuction + executorCapped fee positions and Permit2 limit-order fills.
A protocol-version label alone is insufficient. Runtime code and ABI hashes must match the selected release.

​
Contract responsibilities

​
Recorded testnet development manifest

The checked-in historical manifest for chain ID 46630 records: The manifest labels this deployment development, begins indexing at block 93747023, and pins source revision 1a41aa8d096a4dd6ac298835483850ece8dce02b.
This table reproduces a historical development manifest. It is not a live-status attestation, and it predates later source hardening. Verify chain ID, runtime hashes, ABI hashes, ownership, and dependencies before use.
There is no checked-in KEK.PRO deployment manifest for Robinhood Chain mainnet chain ID 4663.

​
ABI versioning

Current source-generated ABI artifacts cover:
  • KekproLaunchFactory;
  • KekproLaunchLocker;
  • KekproLauncherToken;
  • KekproFeeCompounder;
  • KekproFeeRightsAuction;
  • KekproLimitOrderExecutor.
Pin each ABI file hash with the deployment manifest. The current ABI hashes do not match the hashes recorded by the historical testnet deployment, even though both identify the same protocol-version family. Do not use the current tuple shapes against that deployment without release evidence. Use onchain events for the indexing sequence, event topics, snapshots, and reorg rules. Use reading token state for canonical getters and relationship checks.

​
Verify a manifest

1

Bind chain and block

Confirm eth_chainId, deployment block availability, and the manifest’s finality profile.
2

Hash runtime code

Read eth_getCode for every contract and compare its runtime hash.
3

Verify immutable links

Confirm factory, locker, deployer, router, Permit2, position manager, and block-provider relationships.
4

Verify mutable policy

Read launch and DEX configs, fee allocation, recipients, compounding policy, fee-right policy, and ownership.
5

Confirm the event range

Read canonical events from the manifest deployment block.
Last modified on August 2, 2026