Skip to content

Submit a Launch v1.9.0

Choose a tag to compare

View all tags
@programmable-infra programmable-infra released this 20 Aug 15:22
· 13 commits to main since this release
Immutable release. Only release title and notes can be modified.
v1.9.0
62c7b75
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Submit a Launch v1.9.0

Version 1.9.0 publishes the complete, open-world Application V3.2 contract for launch submissions while preserving
the byte-unchanged Application V3.1 compatibility path. Requirements remain conditional on the route a project
actually selects; unfamiliar project types and no-market designs are not excluded by a capability allowlist.

What changed

  • Added Application V3.2, Submission 2.1, and the policy-neutral Trade Capability Manifest V2 as the complete current
    application package for the official Programmable route.
  • Added the checker-only launch-readiness profile and an offline, closed Router-readiness document that binds the
    exact reviewed source, route components, manifest-resolved canonical Router, and fee plan.
  • Made the selected Programmable Ethereum-mainnet route require exactly 10 bps (0.10%) of gross canonical-pool
    trading volume for the Programmable treasury at 0x4957f49620AFf3Adbbe8195a4f633E49cc93376c.
  • Required the atomic canonical Router path for Programmable provenance. Direct Classic Factory, Graph Factory, or
    Single Factory calls do not create a canonical Programmable classification.
  • Added the maintainer-owned, finalized launch-stamp promotion contract. A promotion receipt carries the full passed
    launch-readiness decision, exact readiness bytes, application and package bindings, and the closed finalized Router
    evidence needed before Registry, API, indexer, or public terminal classification.
  • Published Applicant Compatibility V2 for discovery of the V3.2 package and its supporting contracts while retaining
    Applicant Compatibility V1 and Application V3.1 as legacy compatibility surfaces.

Authority and compatibility boundary

Application V3.1 remains accepted under its unchanged compatibility contract, but it cannot establish
launch-readiness or the official Programmable Router route. An official-route project must add a new V3.2 revision;
existing V3.1 bytes are not reinterpreted or rewritten.

The enabled launch-readiness profile is checker-only and returns
LAUNCH_READINESS_CHECKED_NOT_AUTHORIZED. The production-launch profile remains disabled. No source validation,
readiness result, receipt, tag, or GitHub release grants signing, deployment, public routing, production discovery,
real-user funds, audit, safety, liquidity, sellability, or launch authority.

The authenticated Universal Admission queue and its SQLite backend remain reference-only-disabled: there is no
public queue endpoint, audience, or worker plane. Publishing a valid finalized promotion receipt makes deterministic
terminal integration possible, but does not guarantee adoption by any third-party terminal, provider, indexer, or UI.

Verify locally

Use Node.js 24.12 or newer:

npm ci --ignore-scripts
npm test
Assets 3
Loading