SDK 0.7.0 — October 8 launch deployment

Updates Robinhood mainnet launch defaults to the mined October 8 deployment. Includes config V6 / parameters V2, exact token allocation and burn accounting, unified protected preparation, and examples reviewed against abyss-app and its standalone scripts. Verification: 265 unit tests passed; one separately provisioned AMM integration skipped; three real API read tests passed; clean package consumer and live five-profile discovery passed. Read-only planning correctly refuses execution when the source RPC rejects eth_simulateV1. No mainnet transactions were sent.

SDK 0.6.0

Native Nitro execution admission no longer requires absent optional RPC or wallet policies. Pinned protocol compute limits, exact validated replay, separate poster budgeting, and immediate read-only submission preflight remain mandatory safety boundaries. Offline verification: 102 passed, 1 live-chain test skipped; typecheck and build passed. No financial signing or broadcast was performed.

SDK 0.4.0

Breaking SDK cutover: five-member LaunchBoundsV2, creator-selected per-market oracle and external-liquidity choices, removed profile trading-fee ceilings, clean hook identities and exports, and canonical Abyss discovery. Regenerate profile identities and author consent. See README migration notes. No production contract deployment is included.

0.3.1 — lifecycle SDK cutover

Breaking lifecycle cutover

• Replace historical Atomic/Unified builders and template catalogs with explicit lifecycle plans and signed V2 registry profiles; old aliases are removed.
• Shared V4 config 4 and pool-bound V4 config 5 freeze author terms and require an explicit developer fee rate. Retired configurations are rejected, not converted.
• Registry admission is registerProfile; reads use profileEnvelope and profileId. Author consent uses EIP-712 domain Black Market Launch Registry, version 2, and must be regenerated for the exact new graph.
• Pool-specific contract/ABI names and LaunchEnvelope/Bounds/Graph types have clean names. Current economic tuples and profile/dependency hash preimages remain unchanged.
• Includes lifecycle commitment codecs, explicit planning/recovery and stable-author V3 fee operations. No production launch deployment or author authorization is bundled.

Verification

Release-commit CI passed. Clean installs of the built packages reproduced the shared economic commitment bytes, plan hash and launch identity. Node: 61 tests passed, one chain-dependent test skipped. Python: 220 tests passed.

Publishing metadata

Declares the canonical GitHub repository URL required by npm trusted publishing. Previous v0.2.0 and v0.3.0 tags are preserved; their npm publication failed.

0.3.0 — lifecycle SDK cutover

Breaking lifecycle cutover

• Replace historical Atomic/Unified builders and template catalogs with explicit lifecycle plans and signed V2 registry profiles; old aliases are removed.
• Shared V4 config 4 and pool-bound V4 config 5 freeze author terms and require an explicit developer fee rate. Retired configurations are rejected, not converted.
• Registry admission is registerProfile; reads use profileEnvelope and profileId. Author consent uses EIP-712 domain Black Market Launch Registry, version 2, and must be regenerated for the exact new graph.
• Pool-specific contract/ABI names and LaunchEnvelope/Bounds/Graph types have clean names. Current economic tuples and profile/dependency hash preimages remain unchanged.
• Includes lifecycle commitment codecs, explicit planning/recovery and stable-author V3 fee operations. No production launch deployment or author authorization is bundled.

Verification

Release-commit CI passed. Clean installs of the built packages reproduced the shared economic commitment bytes, plan hash and launch identity. Node: 61 tests passed, one chain-dependent test skipped. Python: 220 tests passed.

The previous Node v0.2.0 GitHub release and tag are preserved; their npm publication failed.

v0.2.0

Current Unified Launcher support, active Uniswap V4 V3 launch path, optional launch API lifecycle, and executable launch examples.