Preview19.6: bounded Livepeer production opt-in

Preview19.6 adds explicit Livepeer production configuration for approved providers, with existing payer, recipient, native binding and cap checks. Free public spot and future offers retain ordinary execution. Native START reuses the Control-owned obligation admission rather than issuing another priced ticket.

Payments remain disabled in the shipped defaults. Operators must configure the matching Control19.6 and exact provider/payer/recipient limits before enabling paid operation. This release does not configure a wallet, fund an account, enroll another identity, or enable production payments automatically.

Upgrade an existing19.4/19.5 Provider using the same identity and state directory at an idle boundary; retain the prior executable, unit and config for rollback. See the installation guide in this source revision. The separately installed native31bb2224 binary is unchanged; the payer signer stays separate from the orchestrator.

CLI artifact source: private b5ae4479be6b8c0f87847977cb15578158a22dd2; public 2f07e87. SHA256: 1b6b2c4b99b66e9b811be3d67e185de904769e81535736f33aee32af975754ab.

Validation includes direct production/free-FUTURE/START regressions, old-code failure and fixed-code success, existing public install/docs validation, and archive checks. Final hosted Control CI passed415/415 with no failures or skips on sourcecc24cf3; the interactive, legacy release, bootstrap and runtime/PG jobs also passed. That source differs from the artifact source only in required-test wiring and two corrected test assertions. The new20-minute Buyer-to-Pon paid acceptance has not yet run. Native ticket acceptance and on-chain redemption are distinct proof states.

Punch CLI 0.1.0-preview.19.5

Linux/x64 Buyer and Provider CLI update. Provider hosts remain Ubuntu 24.04 LTS.

• Preserves existing identities, sessions, configuration, offers and state during a versioned upgrade.
• Documents configuration updates and installation of Punch beside an existing Livepeer orchestrator, including the shared network namespace requirement for loopback endpoints.
• Includes optional Livepeer commands for isolated staging. Public production payments remain disabled; the CLI does not install a native wallet or payer signer.

Download the archive and SHA256SUMS from this release, verify the exact archive line reports OK, then follow the attached INSTALL.md. Keep the prior version for rollback and wait for active jobs to finish before upgrading a running Provider service.

Archive SHA-256: d18f8e6586f6333610f3ef33e13c27c571dbc30bdbf34f7038908283069892ae.

The release binding identifies private source 1f244682860d973295d0041c588d7336ad85f073 and built public source 4073d86fd84e2ce8a1d382dc9a2902640a0c9596. The release tag also includes subsequent documentation corrections; the archive is unchanged. Package version is 19.5; existing Provider help/readiness wire labels retain 19.4 for compatibility.

Verified: archive install/uninstall and command help, Buyer/API/SSH regressions, release metadata and required build checks. This publication does not claim fresh provider onboarding, an automated external GPU workflow, or new live-money acceptance. Preview 19.4 remains available for rollback.

Install and upgrade instructions · Optional Livepeer staging setup.

Documentation correction — 2026-09-13

Use the corrected native installation guide and security scope, merged in PR20. These supersede the earlier wording for native distribution, service management and archive extraction.

The compatible native orchestrator staging build is now separately downloadable. Punch CLI19.5 does not bundle it or the payer's signing backend/wallet. The provider keeps its own native wallet/config; payer signing remains separate. Follow the documented idle upgrade and rollback boundary.

This is a documentation update: the19.5 CLI archive, release tag and seven original assets are unchanged. Native staging publication does not enable production payments or perform a Pon-host upgrade. Existing security checks are scoped; no independent comprehensive audit is claimed.

Punch CLI 0.1.0-preview.19.4

Punch CLI Preview.19.4

This Linux/x64 prerelease adds explicit Provider offer-create --duration-seconds 18000 --network-outbound RESEARCH_EGRESS --future-terms-file /absolute/path/future-terms.json requests. Before activation, the CLI reads back the exact pending offer and rejects mismatching duration, network or future terms. Control keeps administrator-approved creation intent separate from resident identity/refresh; a retired offer does not authorize its successor.

Keep the existing machine identity, state directory and configuration. A software-only upgrade does not require retiring a working offer. After verifying/installing the archive, use the new CLI's service-install with the same machine/state/config to regenerate an existing version-pinned service unit, then restart and verify its heartbeat. There is no automatic Provider upgrade. See the bundled COMMANDS.md and repository INSTALL.md for the complete procedure.

Free pilot only: no billing, charges or commercial SLA guarantees. FIXTURE_ONLY future terms are not a commercial compensation promise. This release does not introduce Buyer slicing.

The owner reports production Control19.4 deployment accepted. Stage/Pon native acceptance of the new offer remains pending; publication does not claim it passed.

Exact release binding

• Public source: 1d7af6f92c7ec36fca95eabd29c8f57e6a172228
• Private release source: 6bc3d1dd4c9bc1e241f3d04cf4a9ad6f8a37f3a0
• Archive: punch-cli-0.1.0-preview.19.4-linux-x64.tar.gz
• Archive SHA-256: ae7bfbb5c9e9b278e45e025853f35833997525b595a5ab6abaef54544f7450ac

Download the archive and SHA256SUMS from this release and verify the exact archive line before installation. RELEASE-BINDING.json and BUILD-MANIFEST.txt retain the source/runtime identities. Source prose identifying this revision as a candidate predates this publication; these release assets and their verified binding define the published artifact.

Validation: focused lifecycle/CLI gate 4/4, hosted private CI 120/120, Linux locking 2/2, readiness 9/9, builder 6/6; public hosted validation passed. Test-only fixture fixes were merged separately without rebuilding or changing this artifact's source binding.

Punch CLI Preview19.3 — free future-compute pilot

Punch CLI Preview19.3 enables the tested future-compute free pilot. There are no charges, payment settlement or commercial SLA guarantees. USDC_TEST and FIXTURE_ONLY remain test semantics.

Use the attached Linux/x64 archive and verify its exact SHA256SUMS entry before installation. Provider support is Ubuntu24.04. The archive's RELEASE-BINDING.json records private source c7b19f768447b75a967e57b6f2e28dc2eae9629c and public packaging source 97098af; proven runtime is e3c1cc027910350d4b389b0543e8f748af9d11aa. Later tag-source changes are documentation/test-only; the accepted archive has not been rebuilt. The attached COMMANDS.md and INSTALL.md are the updated release instructions and supersede the older candidate wording inside the archive.

Provider upgrades must regenerate the existing systemd unit using the newly installed CLI's service-install command with the SAME machine ID and state directory, then restart and verify the loaded executable/heartbeat. Preserve identity, credentials, configuration, working offers and rollback payloads. Reinstall-and-restart alone can leave the unit pinned to the old binary.

Existing providers can optionally create a future GPU offer using --future-terms-file; COMMANDS.md contains complete JSON and commands. Flat offer-create inherits duration, audience, transfer and internet policy from the approved existing intent, overlaying only future terms. It does not change those authorizations through duration/network/audience flags. GPU UUID/CDI must come from fresh inventory. Software-only upgrades do not require offer retirement. If electing new terms on an occupied single-GPU offer, unlist, wait for terminal cleanup, then retire and create under the same identity; verify the resulting offer receipt.

Native AWS staging acceptance: future accept/claim, RTX5080 CUDA sum32640 as UID65532, NONE outbound denial, matching result download, STOP cleanup and fresh SSH denial; same-identity/GPU retire/create passed. Production acceptance: new Buyer with unchanged19.2 Provider reached ACTIVE, nonroot shell execution and file creation/download matched, then STOP reached CLEANUP_COMPLETED with access denied. These measured paths are not a commercial reliability or SLA promise.

Archive SHA256: 710907e56186da9c53c5b180e4993d96509725124785e3f550a23a951476cada.
Packaged Buyer SHA256: 01e84cb129967574856534c2112bfa6adfce7b5b1b54c9684ebae94d21f8dede.
Packaged Provider SHA256: 6a22016a36590a211a731d3509603cc981f87d837eaac2626f3d2d5ecff7ad84.
Both entrypoint hashes exactly match the accepted native canary. Readiness v1 wire remains19.2 for old-provider compatibility; binary version is19.3.

Preview.19.2 — Ubuntu 24.04 GPU offer recovery

GPU offer recovery and provider upgrade guidance for Ubuntu 24.04 LTS (Linux/x64).

• Control now permits reuse of an exact GPU after its former offer is retired, including when the current provider identity differs. Active/nonterminal allocations remain exclusive.
• offer-create reports actionable CAPACITY_CONFLICT guidance without exposing server details. Public help and command docs include GPU UUID/CDI selectors.
• Upgrade docs explicitly regenerate the existing machine-scoped service using the new CLI. Keep the same identity, credentials, configuration and state.
• Validated against the affected GPU provider: offer listed, buyer order ACTIVE, normal gateway SSH, exact RTX 4000 Ada visible in the workload.

The tag suffix ubuntu24.3 is our third Ubuntu-24 packaging revision, not an Ubuntu OS version. The supported provider OS is Ubuntu 24.04 LTS. The CLI version remains Preview.19.2; when replacing the same-version program directory, retain its previous payload as rollback before installation. Never delete provider state.

Verify the archive against this release's SHA256SUMS before installation. Control compatibility is deployed before this CLI publication. No new onboarding is required.

Preview.19.2 Ubuntu24 — existing-provider renewal recovery

Existing-provider recovery

This Ubuntu 24.04 Linux/x64 preview preserves an existing provider identity when upgrading from Preview.19.1. A stale, failed renewal proof can refresh automatically once, but only after authenticated Control confirms that the request was not committed. Generic authentication failures and ambiguous requests do not reset identity or state.

The stateful regression test covers an existing identity, a retired offer, an old pending renewal, renewed session, fresh capacity, and a new listed offer. The matching Control is deployed. The archive has also been installed on an existing Ubuntu test provider with identity preserved and fresh heartbeat verified. This does not claim a physical GPU job test on every provider's hardware.

Download the archive and SHA256SUMS from this release; verify the exact archive entry before extraction. Follow the included installation documentation. Keep existing identity, credential, configuration, and state directories; do not repeat onboarding. Existing Preview.19 hosts must also follow the documented host-helper update when their helper predates the quota-cleanup correction.

CLI archive SHA-256: 587257c9c2f7f0989be331abcde7181778e31cb6365562ff853bdc4fd52d497e.

Changes: punch-cli PR13 and punch-compute PR55.

Punch Preview19.2 — Ubuntu 24.04

Punch Preview19.2 — Ubuntu 24.04 release

Invitation-only, operator-approved, zero-price preview for Ubuntu 24.04 LTS x64. This is a distinct Ubuntu24 release; the older Preview19.2 release is not retagged or replaced. Runtime version remains 0.1.0-preview.19.2.

Archive SHA-256: 689ab42998509b5335663d174b616fc76a42022380529e2a3c0e08345f5ec8b3. Verify the archive and both provenance files using the attached SHA256SUMS before installation. Upgrade both Buyer and Provider for automatic per-contract gateway routing. Existing Providers must also update the separately installed root host helper following docs/INSTALL.md; preserve identity, configuration and state. Do not repeat onboarding to upgrade an existing identity.

Verified product path

• Two controlled Buyers exercised six Buyer-to-Provider combinations across three Ubuntu24 Providers: actual SSH, stop/cleanup, order replay, occupied/offline admission rejection, cross-Buyer denial, Provider restart/reconnect and held-session closure.
• The final archive additionally passed two simultaneous Buyer workloads on one Ubuntu24 machine: independent SSH keys and workspace markers, enforced CPU/memory/process limits, no capabilities, no Docker socket, seccomp and no-new-privileges.
• Direct gateway routing with the wrong Buyer's SSH key was denied in both directions. Stopping one workload preserved the other's live SSH connection; stopping the second closed that session.
• A 9-GiB quota-backed machine admitted two 4-GiB offers and rejected a 4+6-GiB over-allocation. Both final jobs reached cleanup-completed; workload containers, gateway listeners, quota allocations and active bindings were absent afterward. Test offers were retired without deleting history.

Repairs

Per-contract lifecycle journals and gateway routing replace the single-active-workload assumption. Quota readback now selects the exact project rather than another remaining row. A signed, completed STOP cleanup can finish the lifecycle even when workload execution failed; failure history is retained without leaving capacity stuck.

Provenance and limits

Private runtime source: 9d7e73fca7a2e5367afb7c44a2c8ca14387bc65f. Archive public-source snapshot: 77cd9f5e7f5495c345cad748baf2dfb75875440c. The matching AWS Control archive is separately deployed and verified. Later public documentation records these completed live checks; candidate/pending wording in the immutable archive's earlier documentation is superseded by this release receipt, not by changed runtime bytes.

This is scoped acceptance, not a guarantee that no provider will encounter a new issue. Fresh Ubuntu onboarding evidence and final installed-upgrade evidence are distinct. Payment settlement, GPU execution, other distributions, arbitrary networking and general availability are not claimed. No provider notification is implied by publication.

Punch CLI v0.1.0-preview.19.2

Preview.19.2 adds capacity-aware Provider offer creation and lifecycle commands.

Linux/x64 archive SHA-256: e4792f48d798efdec309dbbf9b7ff7b2d42346d81d11f4bd84756cf40e597d30
Private runtime source: 4e8e0f3c138db22e349b183f1306b511e8705c48
Public source: d7151e6

Zero-price Preview boundary remains unchanged; no payment settlement is enabled.

Punch CLI 0.1.0-preview.19.1 offer-capacity replay-fixed

Verified Preview19.1 replay-fixed CLI candidate.

Public source commit: 22cf389
Public source tree: 5913ac3d0c5d6f27c4afda6f869687b619ee330d
Archive SHA-256: 980c4972954f6564a92752252b3082897d24816bff141e23f3f7f2aa99e3fa15

Includes offer-create and same-key replay compatibility. See RELEASE-BINDING.json and BUILD-MANIFEST.txt for binding and build proof.

Punch CLI Preview.19.1 Offer Capacity 1

Fixed Provider offer-create CLI for capacity-slot, unlist-retention, retire-release, and multi-offer resource enforcement. Internal CLI version remains 0.1.0-preview.19.1; this unique prerelease tag binds the exact reviewed offer-capacity build. Verify SHA256SUMS before installation.