Skip documentation navigation

Integrate Programmable launches

Verify Router-stamped tokens and pools, or index new launches from the canonical Ethereum Router.

Choose a path

Start with the task your product needs. Both paths use the same manifest, Router and verification rules.

Before you start

Bind your integration to the live manifest before you read a token, pool or event.

Network
Ethereum mainnet · chainId 1
Start block
25717612
Launch kinds
1 is Programmable Custom; 2 is Programmable Classic. Kind 0 is invalid.

Return an explicit result

Keep negative results separate from missing or inconsistent evidence.

STAMPED
Every required binding, lookup and cross-check succeeds.
NOT_STAMPED
A canonical token or pool lookup succeeds and returns zero.
UNAVAILABLE
The Router is outside its live block range, the chain is inactive or activation data is incomplete.
INDETERMINATE
RPC, ABI, runtime, block, decoding or cross-check evidence is incomplete or inconsistent.

Use the published source set

Resolve the current Router from the manifest and verify the exact ABI bytes before the first lookup.

Integration checklist

  • Load the live manifest and verify the Router binding.
  • Use one canonical block for every read in a verification.
  • Return INDETERMINATE when required evidence fails or disagrees.
  • Validate the implementation against the finalized PCAN vector.

Machine-readable docs

The same source set is available as Markdown, compact model context and raw contract artifacts.

Open machine-readable documentation