Session Client 0.1.1

Session Client 0.1.1 corrects fresh Base channel initialization when the receiver has already completed a previous channel. Historical receiver counters remain part of the saved baseline; finalized receipt, channel, token-transfer and refund checks are unchanged.

The owner controller still serializes activity for a receiver/token pair. An outstanding payout or unrelated receiver activity remains outside this qualification workflow and fails closed. This release does not add concurrent receiver settlement coordination.

Install the exact qualified archive:

npm install https://github.com/402signalhq/402signal/releases/download/session-client-v0.1.1/402signal-session-client-0.1.1.tgz

Node 24 is required. This is a GitHub archive release, not an npm registry publication. The package includes Base and native Solana session clients; this correction changes Base receiver reuse only.

Validation: 32 synthetic session tests, including six new receiver-reuse/concurrency cases; fresh installed Base/Solana consumers; strict TypeScript checks for all five exports and eight expected refusals. The archive and its SHA256 are recorded in the attached provenance file.

Source and receiver-serialization limits.

@402signal/route-guard 0.7.0

Verify routing evidence against the exact request, payment challenge and buyer limits before authorizing a merchant payment.

This version adds evidence checks for supported native Base and Algorand MPP charge profiles alongside the existing exact-payment, session and Algorand manifest profiles. Payment selection stays explicit; ambiguous offers are refused. Verification does not sign, submit a payment or guarantee API fulfillment.

This exact archive passed fresh-consumer runtime and strict TypeScript checks using synthetic payments. Live qualification is tracked separately from these package checks. This is a GitHub release archive; no npm-registry publication is implied.

Supported scope and storage requirements.

Download the archive and its SHA256SUMS file into a new directory. Verify the checksum before installation:

sha256sum --check SHA256SUMS && npm install ./402signal-route-guard-0.7.0.tgz

Source: 65371be, tree c497068376b1712989fbaad19a4e00c455319929.

@402signal/mpp-client 0.1.0

Explicit Base USDC native MPP and Base x402 adapters for applications that control their own wallet, budget and transport.

The native Base adapter checks supported EIP-3009 offers and routing evidence before producing a credential. It does not automatically fetch, broadcast or retry a payment. The separate base-x402 export retains the exact-payment adapter. Native Algorand remains a repository reference adapter, not an additional package in this release.

This exact archive passed fresh-consumer runtime and strict TypeScript checks using synthetic payments. Live qualification is tracked separately from these package checks. This is a GitHub release archive; no npm-registry publication is implied.

Supported scope and storage requirements.

Download the archive and its SHA256SUMS file into a new directory. Verify the checksum before installation:

sha256sum --check SHA256SUMS && npm install ./402signal-mpp-client-0.1.0.tgz

Source: 65371be, tree c497068376b1712989fbaad19a4e00c455319929.

@402signal/algorand-batch-buyer 0.2.0

Explicit Algorand batch and invoice clients for merchants implementing the documented manifest contract.

Alongside the original two-item interface, this version supports 2–15 ordered payments plus a sponsor, or a 2–64-job aggregate invoice paid with one transfer plus a sponsor. Buyer-pinned job hashes, amounts, recipient and fee limits remain part of the authorization. Ordinary single-payment APIs are not automatically compatible.

This exact archive passed fresh-consumer runtime and strict TypeScript checks using synthetic payments. Live qualification is tracked separately from these package checks. This is a GitHub release archive; no npm-registry publication is implied.

Supported scope and storage requirements.

Download the archive and its SHA256SUMS file into a new directory. Verify the checksum before installation:

sha256sum --check SHA256SUMS && npm install ./402signal-algorand-batch-buyer-0.2.0.tgz

Source: 65371be, tree c497068376b1712989fbaad19a4e00c455319929.

@402signal/route-guard 0.5.0

Route guard 0.5.0

Adds local verification of signed batch and session observations alongside the existing routing client and exact-payment guard.

• Explicit profiles for Base x402 batch settlement, Solana MPP push sessions, and Algorand two-item same-payee USDC groups.
• Binds the original request, raw challenge and buyer limits before the caller's authorization callback.
• Includes TypeScript declarations, private response recovery and the buyer-owned HTTP client, with zero runtime dependencies. Requires Node.js 22 or newer.

This package verifies observations; the buyer's wallet still controls each payment. Server profile availability, merchant settlement and network/provider costs are separate. A session capital limit is not its per-request price. This release note makes no claim that live paid batch qualification is complete.

Verify the attached SHA256SUMS before installing:

sha256sum --check SHA256SUMS
npm install ./402signal-route-guard-0.5.0.tgz

The package remains distributed as a release tarball; it has not been published to the npm registry.

@402signal/route-guard 0.4.0

Installable client support for private request recovery, customer API credentials, and guarded pre-spend handoffs. Customer credentials authenticate access to 402Signal; wallet signing remains buyer-owned.

The compatible server is deployed. Cloud package checks and client tests passed, and a live Base workflow confirmed the routing and seller payments and received the seller response. Delivery quality is not assessed by this client.

Supported offers must meet the guard's request and payment-term constraints. Challenge-specific changing recipients require a separate integration design. Native batch and session profiles are not included in this release.

Install the attached package and verify its SHA-256 against the attached SHA256SUMS. Integration instructions and the buyer-owned reference workflow are in the repository.

@402signal/route-guard 0.3.0

Installable Node/TypeScript routing client, local evidence verifier and optional private file store. Includes a web-search integration example with buyer-owned wallet, budget and confirmation callbacks.

Download the tarball and SHA256SUMS, verify the digest, then install:

npm install ./402signal-route-guard-0.3.0.tgz

Requires Node 22 or newer. The supplied private file store requires POSIX storage (including WSL). This release is distributed through GitHub; it is not an npm registry publication.

The client requires a compatible HTTP /route server and saves private request scope before submission. Recovery retrieves existing evidence without granting another payment. Seller execution and independent payment confirmation remain with the buyer.

Qualified through fresh-package installation, strict TypeScript compilation, seven synthetic example scenarios, SDK tests and PostgreSQL HTTP restart checks. External seller observations establish unpaid compatibility; paid external fulfillment is not claimed. Routing remains $0.003 per qualifying route, with seller payment separate.

SHA-256 (402signal-route-guard-0.3.0.tgz):
775b14ace3079e458518a0981bd39277dc22c4ad6e3eab2e1e9b4df44cfc537b