> For the complete documentation index, see [llms.txt](https://programmable.market/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://programmable.market/docs/developers/machine-readable/launch-stamps.md). # Launch stamps What a Custom Launch stamp records A launch stamp records that a Programmable Router executed a Custom Launch. It binds the token, hook, pool and supporting contracts to that launch. ## Which launches use stamps? Robinhood Custom launches with separate token and hook contracts use Router V1. A shared token and hook contract uses MultiRole V2 and Router V2. Ethereum Router launches follow their published deployment manifest. Module Mode uses its own factory events and records. It does not need a Custom Launch stamp. Foundation and earlier Native or Engine releases must be verified with their respective interfaces. ## Verify the record Use the source's manifest to find the Router address, code hash, ABI, start block and finality rules. Match the successful transaction, emitted events and contract lookups at the same canonical block. The API request ID and the onchain launch ID are different identifiers. A shared token and hook address is valid under MultiRole's role rules. A stamp proves the recorded origin and contract relationships. It does not prove an audit, present liquidity, sellability or external terminal support. A direct factory call outside the Router does not acquire a stamp later. [Verify a launch](/docs/developers/verify.md) explains the checks and source-specific references. ## Direct Ethereum Custom Hooks An Ethereum CustomGraph can be prepared outside the launch API. The official stamp requires a fresh launch through the canonical Router and a valid authorization accepted by its permit authority. Prepare the graph, predicted addresses, runtime hashes and permit before deployment. A separately deployed token cannot acquire this Router stamp later. [Direct Ethereum Custom Hook inputs and files](/docs/developers/machine-readable/launch-stamps/ethereum-direct-custom-hook.md) provides the exact tuples, ABI, request template and read-only verifier. The [downloadable bundle](https://programmable.market/developers/ethereum-custom-hook-indexing.zip) contains the complete files. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://programmable.market/docs/developers/machine-readable/launch-stamps.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.