From launch to application
Each layer answers a different question. Do not use market state as proof of origin, or a provenance record as proof of current market behavior.
Launch execution
Model-specific contracts create the token, initialize its Uniswap v4 market and apply the selected launch rules.
Onchain market
PoolManager and poolId identify the v4 market. Its currencies, fee, tick spacing, hook and current state must be read separately.
Launch provenance
For a launch executed and stamped through Router V1, the Router records the token, hook, market, launch kind and component proofs.
Application label
A terminal, wallet, scanner or indexer can show a Programmable label after it verifies the Router address, runtime, bindings, lookups and record cross-checks.
Router verification applies only to stamped launches
Start with a token address or with PoolManager and poolId. Resolve the launch ID, read the recorded stamp and cross-check the returned identity at the same canonical block.
The published start block is the first block to scan for this Router. It does not add provenance to earlier launches. A direct factory call remains outside the Router record even when it occurs at or after that block. Do not infer a stamp from a name, symbol, shared hook or legacy event.
A verified record establishes Router provenance. It is not a safety guarantee. It is also not an audit, approval or endorsement.
Public resources
Use these resources together. The manifest identifies the deployment, the ABI defines the reads, and the reference explains how to verify the result.
- Live manifestCurrent Ethereum deployment, Router range, runtime hash and immutable bindings.Opens in a new tab
- Router ABIThe exact interface used to read and verify Launch Stamp Router V1.Opens in a new tab
- GitHub referenceVerification algorithm, terminal guidance and runnable examples.Opens in a new tab
What verification proves
- It establishes
- The recorded Router origin, token, hook, market, launch kind and component proofs for that stamped launch at the verified block.
- It does not establish
- Current safety, tradability, liquidity, price, terminal support, audit coverage or the behavior of an external interface.
- It does not cover
- Launches created before Router activation and every direct factory call outside the canonical Router path, including calls made at or after the published start block.