Your launches

Manifest sha256:95f9e22e1cb6f3677ee921eecebcbaffbb24aa92836811892dfb4101772e611a

Manifest digest: sha256:95f9e22e1cb6f3677ee921eecebcbaffbb24aa92836811892dfb4101772e611a

Use the normal Programmable API key with custom-launch:create and custom-launch:read. Never place it in a URL, source file or log.
Fetch /v4/chains/4663/custom-launch-contract/manifest.json and /v4/chains/4663/custom-launch-credentials/me before building. Check the returned chain, controller, scopes, limits and manifest digest.
Use /v4/chains/4663/custom-launch-contract/request-packer.mjs with --input plan.json --out request.canonical.json --report pack-report.json. The plan is programmable.custom-launch-plan.v1. The source/compiler bundle is the existing exact-source V2 bundle.
POST exact canonical request bytes to /v4/chains/4663/custom-launch-plans:preflight. Inspect every finding: code, stage, blockingAxis, jsonPointer, actual, constraint, witness, repair, retry and resumeUrl.
Only local declarative repairs from the same published parser may be applied with --repair. Repack and use the new reported idempotency key whenever any byte changes. Never rewrite source to satisfy an unproved claim.
POST the same packed bytes and Idempotency-Key to /v4/chains/4663/custom-launch-plans only when that operation is available. After an ambiguous response inspect or retry the exact same bytes and key; never start a second launch.
An existing exact replay remains readable after a manifest change or disabled release under the same current principal, controller, key, bytes and predecessor. A lookup miss still needs current admission. HTTP 409 means the original idempotency binding differs.
Open the stored resumeUrl, review each exact controller/chain/target/data/value/gas/nonce/deadline transaction and use the user's authorized wallet handoff. The API key itself cannot sign, broadcast or pay gas.
After broadcast submit only the transaction hash to the bound step proof route, then poll the plan. Preserve finalized steps when replanning. Continue through independent finality, source/runtime readback, feed and website visibility.
Replan creates a fresh immutable successor and returns a server-generated replan binding to the predecessor hashes and finalized prefix. Review that binding; do not resubmit finalized transactions as new wallet steps or treat their stored evidence as fresh admission.
Components, tags, unknown economics, optional publication and audit/routing/Hooklist status do not select launch eligibility. Unresolved behavior reduces assurance. Provider failures are analysis_pending and retryable.
20 bps is pool_enforced only with reproduced immutable enforcement; otherwise it applies to Programmable-built/routed qualifying swaps. No qualifying swap flow is not_applicable. Never claim all_routes without enforcement.
Display Programmable execution, source/assurance, public indexing, Hooklist, Uniswap API and Uniswap Labs routing separately. External submissions require stored user opt-in. Show generic claim controls only for bound verified descriptors.
An explicit platform stamp action is an optional terminal call placeholder: authority launch_stamp/stampPlanV1, released target, data 0x and value 0. Use your own action ID outside the reserved platform: namespace. The protected issuer constructs the final stamp bytes from the finalized controller prefix.