@piprail/sdk 2.15.1 → 2.16.1

package/CHANGELOG.md

@@ -4,7 +4,213 @@ All notable changes to `@piprail/sdk` are documented here. The format
 follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the
 versions follow [Semantic Versioning](https://semver.org/).
 
-## [Unreleased]
+## [2.16.1] — 2026-09-06 — GoPlausible settles Solana, live-proven
+
+### Added
+
+- **GoPlausible is now seeded as a keyless Solana facilitator.** They told us directly that they
+  settle Solana as well as Algorand and Base, and they were right: their `/supported` advertises
+  `solana:5eykt4Us…` `exact` with a sponsor fee payer, and PipRail's own `facilitatorCoverage()`
+  reads the same.
+
+  **Live-proven on Solana mainnet 2026-09-06** rather than taken on trust. A real
+  `402 → pay → verify → 200` round trip on the `exact` rail: the merchant received exactly
+  0.01 USDC, the **buyer paid 0 SOL**, GoPlausible's sponsor `8a8fFNfk…RAYi` paid the
+  10,001-lamport fee (confirmed by reading `accountKeys[0]` on the settled transaction), and a
+  replay of the same proof was rejected. Tx
+  `3DEGg6Lue8471meBH8hbLxV1bLmZGKvmvmSY3tjg7tQFnxzE9GQXUXokjQnZgTqaEU4SaXuY9F7v3m7JsX5xDgrZ`.
+
+  Solana previously seeded only PayAI and OpenFacilitator, so this is a third keyless option on
+  that chain. No default changes: the seed list is a convenience, and the SDK still depends on no
+  facilitator.
+
+## [2.16.0] — 2026-09-06 — the XRP Ledger `exact` buyer, and paying the 91% of the x402 web we could not
+
+### Added — the XRP Ledger `exact` buyer (stage 04, first family)
+
+- **A PipRail agent can now pay a standard x402 `exact` rail on the XRP Ledger** — 1,732 live rails,
+  and as far as we can tell the only open-source buyer on that chain. `drivers/xrpl/exact.ts`
+  implements `scheme_exact_xrpl.md` in both directions: the buyer signs a complete `Payment` and
+  broadcasts nothing; the gate decodes the blob, re-derives every checked field from its own trusted
+  accept, submits, and waits for a validated `tesSUCCESS`.
+
+  XRPL is the family where **the payer pays the fee** (it is a field inside the signed transaction),
+  so there is no sponsor, no co-signature, and no fee-drain guard. The scheme replaces those with a
+  list of MUST-NOTs the settler enforces — no `Memos`, no `Paths`, no `tfPartialPayment`, no
+  `Delegate`, never `Amount` and `DeliverMax` together — each of which is a way a hostile blob could
+  underdeliver, and each of which has a test.
+
+  The challenge binds through `InvoiceID = SHA-256(extra.invoiceId)`, **not** a memo: the scheme has
+  settlers reject `Memos`, which is exactly what PipRail's `onchain-proof` XRPL path uses for its
+  nonce. The two paths deliberately share no code.
+
+  **`extra.areFeesSponsored` is required by the scheme and absent from 100% of live rails**, so it is
+  read as *false unless present*. Requiring it would have rejected the entire deployed XRPL x402 web
+  — the third instance of that bug class this release cycle, and the reason it now has a test of its
+  own.
+
+  **Native XRP only, deliberately.** The two XRPL asset forms use different wire amount conventions
+  (native is an integer *drops* string, an issued currency is a *decimal* `value` — both verified
+  against live merchant challenges). The SDK prices and spend-caps in base units, so reading an
+  IOU's `"12"` as base units would understate a 12-RLUSD payment by 10^15 and slip it under any
+  policy cap while the buyer signed the real amount. Issued currencies are therefore dropped at
+  gather rather than mispriced; the RLUSD half waits until that decimal path is threaded through
+  quoting and the policy.
+
+- **`ResolvedNetwork.exactPayableAsset?(asset)`** — a new optional driver hook. The buyer's gather
+  used to hard-code "any recognised token is exact-payable, the native coin never is", which was
+  true until XRPL, where it is wrong in *both* directions. A driver that declares the hook is
+  authoritative for all of its assets; every other family omits it and behaves exactly as before.
+
+- **Three conformance fixes found by pointing the buyer at real merchants**, each of which made a
+  live XRPL rail unpayable on its own:
+  - `describeAsset` and `recipientReady` only knew the native coin as `'native'`. The XRPL x402 web
+    writes it `'XRP'` — all 863 native rails do. The first miss dropped every rail at gather ("no
+    compatible accept" on a chain we fully support); the second then demanded a **trustline** for a
+    coin that cannot have one. Both now go through one `isXrpNative()` predicate.
+  - `LastLedgerSequence` was a fixed 20-ledger window. The settler checks it is "within policy
+    window", and the merchant's policy is what `maxTimeoutSeconds` announces — so a rail offering
+    60s was getting an ~80s blob, one that outlives the merchant's own quote. Now derived, clamped.
+  - `Flags` was hard-set to `0`. `tfPartialPayment` is a different bit, so zero was never needed to
+    exclude it — but it made our transactions the only ones on the ledger without
+    `tfFullyCanonicalSig`. Now set, matching what every other XRPL client sends.
+- `extra.sourceTag` is mirrored into the transaction's `SourceTag`. Not in the scheme's `extra`
+  table, but present on **1,728 of the 1,732** live rails — it is how deployed vendors correlate a
+  payment back to their own quote.
+- Live-proven on mainnet: settle tx
+  `F673064D2E0D982481844A769E829FD8B486EB9FB7B014F866C92F1C49770505` — 0.01 XRP through our own
+  gate on the `exact` rail, payer debited 0.010012 XRP (the amount **plus its own 12-drop fee**),
+  merchant credited 0.010000, and a genuine replay of the same signed blob refused with a 402.
+- Buyer-side errors are mapped per `ERRORS.md` §9: an unactivated payer account (XRPL reports it as
+  `actNotFound`, but on that ledger "does not exist" means "unfunded") becomes
+  `InsufficientFundsError` with the base-reserve fix in the message; an `xrpl.js` validation failure
+  at signing becomes `UnsupportedSchemeError` carrying the library's reason; any other RPC failure is
+  rethrown unchanged rather than disguised as an affordability problem. All three are tested.
+- **Not proven, and it is NOT our bug: a paid round-trip against a THIRD-PARTY XRPL merchant.**
+  Two live vendors refuse our payload with `invalid_payload` — from **their own pre-check**, before
+  their facilitator ever sees it (proven by routing a v1-shaped body past that pre-check, which then
+  returned the facilitator's own schema error: it wants exactly the `{x402Version: 2, accepted,
+  payload}` envelope we already send). The decisive test: **the same client, envelope and header pay
+  one of those same gateways successfully on its Base rail** (0.001 USDC, HTTP 200). So our envelope
+  is correct and the fault is XRPL-specific on their side. Our transaction also matches, field for
+  field, a payment that merchant has accepted from another client. Working conclusion: the deployed
+  XRPL dialect has drifted from `scheme_exact_xrpl.md` — worth raising upstream.
+  **No funds were lost across ~10 refused attempts** — every vendor rejects before settling, and the
+  ledger confirms no payment ever left the wallet.
+
+
+### Fixed — the buyer required a field the spec makes optional, and so could not pay 91% of the x402 web
+
+- **`schemes: ['exact']` clients now pay the standard x402 web: 26.3% → 98.8% of the resources
+  listed on the CDP Bazaar** (15,686 resources / 40,388 `exact` rails, measured 2026-09-06 by
+  `npm run x402:coverage`; the figures live in `scripts/x402-corpus/coverage.json`, which owns
+  them). Rail-level coverage went 9.2% → 88.9%.
+
+  The buyer's gather predicate required `extra.assetTransferMethod` on every `exact` rail. The
+  ratified scheme says the opposite — `scheme_exact_evm.md`: *"If no `assetTransferMethod` is
+  specified in `PaymentRequired.extra`, clients should default to `"eip3009"`"* — and the SVM,
+  Algorand, Aptos, NEAR and Hedera schemes never define the key at all (their required extra is
+  `feePayer`). Only **9%** of live rails carry it; **79%** carry just the EIP-712 domain. So a
+  PipRail agent silently refused every Solana rail, every Arbitrum rail and 85% of Base rails —
+  including textbook canonical-USDC EIP-3009 rails it was perfectly able to sign.
+
+  This was never a pay-path bug: the EVM driver already defaulted to EIP-3009 and re-derives the
+  token's EIP-712 domain on-chain. Only the gather refused. A rail that NAMES a method we don't
+  implement (the spec's `erc7710`) is still skipped rather than signed blind.
+
+  Found by probing seven real third-party 402s and paying none of them, while 1,636 unit tests were
+  green. The tests agreed with their own hand-built fixtures; nothing checked the fixtures against
+  the world. That gap is now closed by `sdk/test/x402-corpus.test.ts` — 62 REAL challenges captured
+  from the live index, replayed through the real client.
+
+### Fixed — the Solana buyer required `extra.decimals`, which the SVM scheme never defines
+
+- **99.3% of live Solana rails planned as payable and then threw at signing time.**
+  `payExactSolana` required `extra.decimals` for the TransferChecked and raised
+  `UnsupportedSchemeError` without it — but `scheme_exact_svm.md` doesn't define `decimals` at all
+  (its one required extra is `feePayer`), and only **41 of the 5,760** live Solana rails carry it.
+  The same "we require a field the spec makes optional" mistake as `assetTransferMethod`, one layer
+  deeper, and worse because it broke the plan-vs-pay contract: the rail gathered, `planPayment`
+  said `payable`, and the payment then failed.
+
+  The decimals now come **from the mint on-chain**, which is also the safer source — a server that
+  understated them could otherwise have the buyer sign a transfer 10^n larger than the quote, and
+  TransferChecked would accept it. A rail that states decimals disagreeing with the mint is refused;
+  `extra.decimals` survives only as a fallback if the mint read fails.
+
+  Found by paying a real Solana merchant. No unit test could have caught it — every fixture in the
+  suite carried `extra.decimals`, because our own gate always emits it.
+
+### Live-proven on mainnet (2026-09-06)
+
+Real payments to real third-party merchants, one per wire shape this release unlocks:
+
+| shape | merchant | proof |
+|---|---|---|
+| v2 · Base · domain-only (no marker) | `api.onesource.io/api/chain/block-number` | 200, 0.001 USDC, `0x44e9fed18bf9…` |
+| v2 · Base · slug network | `coil.trade/api/crypto/gate` | 200, 0.001 USDC, `0xc38e6da9cbc2…` |
+| **v1** · Base · `X-PAYMENT` wire | `x402factory.ai/base/coinprice` | 200, 0.001 USDC, `eip3009-nonce:0xb6c321fa…` |
+| v2 · Solana · `feePayer`, no marker | `hypernatt.com/api/m2m/liq-radar` | 200, 0.001 USDC, `solana-nonce:3g3Wj5G6G7D…` |
+
+Every row is a real body from a real stranger's endpoint, re-run against the FINAL build of this
+release (an earlier run on the same day proved the same four shapes).
+
+Own-gate regression, also on mainnet and also re-run on the final build: Base USDC + EURC
+round-tripped gasless via EIP-3009 — payer ETH delta **0**, merchant received, **replay rejected**
+(settle `0x85dfcc2b480f…` / `0x41fa1bdf5ea1…`); Algorand settled live with the enriched receipt and
+a rejected replay (`TBRSSLNUJGCUS6…`).
+
+### Added — x402 **v1** challenges on the buyer path
+
+- **A v1 server can now be quoted and paid.** PipRail's stated posture has always been "emit strict
+  v2, accept liberal v1 + v2", and the gate honoured it — but the buyer's `isValidChallenge`
+  hard-required `x402Version === 2`, so every v1 server was an `InvalidEnvelopeError`, and no v1
+  header emitter existed to answer one with. 251 of the 15,686 catalogued resources are v1.
+  `normalizeV1Challenge` lifts a v1 body (`maxAmountRequired`, slug network, per-accept `resource`
+  string) into the standard shape, and `buildV1PaymentHeader` frames the answer on the v1 wire.
+  Probed live: a v1 server ignores `PAYMENT-SIGNATURE` and reads only `X-PAYMENT`, so the network
+  slug is echoed back exactly as the server sent it (v1 verifiers string-compare it).
+  The slug is remembered on a synthetic `wireNetwork` field, which is **stripped from every
+  outgoing `accepted` echo** — that block is documented as the merchant's rail returned verbatim,
+  and facilitators compare (some hash) it, so a key the merchant never published must not appear
+  in it.
+
+### Added — the Algorand CAIP-2 id the spec actually uses
+
+- `scheme_exact_algo.md` gives Algorand mainnet as the base64 genesis hash **truncated to 32 chars**
+  (`algorand:wGHE2Pwdvd7S12BL5FaOP20EGYesN73k`), and the deployed web follows it — 874 live rails on
+  the spec form vs 589 on the padded 44-char id PipRail binds. Both forms are now accepted on parse.
+  What PipRail *emits* is unchanged (switching that would break deployed 2.x Algorand buyers; it is
+  queued for the next major).
+
+- **The GATE now matches an echoed network id through the same canonicalisation.** It compared
+  `accepted.network` to its own rail with `===`, so a conformant buyer that canonicalised the id
+  before echoing it — the Algorand spec form, or TON's superseded `ton:-239` — had a perfectly
+  valid payment refused. All three selector sites (`onchain-proof`, `exact`, `upto`) now compare
+  through `normalizeNetwork`. This can only widen which of the gate's OWN rails is selected: payTo,
+  amount and asset are re-derived from the gate's spec either way, so a wrong network still cannot
+  redirect a payment. The Algorand driver's `supports()` accepts both spellings directly too,
+  mirroring TON.
+
+### Added — coverage is now measured, not asserted
+
+- **`npm run x402:coverage`** (`scripts/x402-corpus/audit.mjs`) pages the live CDP Bazaar, classifies
+  every rail against the SDK's own exported predicates, and writes `scripts/x402-corpus/coverage.json`.
+  Every coverage figure in this repo cites that file. `--live` runs a real read-only `quote()` against
+  live third-party 402s (8/9 quotable, the 9th a merchant whose `upto` rail omits the spec-mandated
+  `facilitatorAddress`); `--fixture` regenerates the regression corpus.
+- `PayOption.method` reports the transfer method the buyer would actually sign, appending
+  `' (default)'` when the rail named none — so the inference is visible instead of implicit.
+- New exports: `exactTransferMethod`, `isSettleableExactMethod`, `KNOWN_EXACT_TRANSFER_METHODS`,
+  `DEFAULT_EXACT_TRANSFER_METHOD`, `normalizeV1Challenge`, `buildV1PaymentHeader`.
+
+### Changed — types now admit what the wire allows
+
+- `X402ExactAcceptEntry.extra` and `extra.assetTransferMethod` are **optional**. A conformant rail may
+  ship `extra: {}` or omit the block entirely, and the type said otherwise, which is how a
+  bare-`extra` deref came to look like a real hazard. Every read on the buyer path optional-chains.
+  Defaults are unchanged: `schemes` still defaults to `['onchain-proof']`, so a zero-config client
+  behaves byte-identically.
 
 ## [2.15.1] — 2026-08-28 — a dead Sui RPC, an RPC failure blamed on the token, and fuzz hardening
 
@@ -1924,6 +2130,8 @@ straight into your wallet. The API is small and self-contained.
   to your wallet; PipRail never holds funds.
 - `viem ^2.21` is a peer dependency. Node 20+ or a modern browser.
 
+[2.16.1]: https://www.npmjs.com/package/@piprail/sdk
+[2.16.0]: https://www.npmjs.com/package/@piprail/sdk
 [2.15.1]: https://www.npmjs.com/package/@piprail/sdk
 [2.15.0]: https://www.npmjs.com/package/@piprail/sdk
 [2.14.0]: https://www.npmjs.com/package/@piprail/sdk

package/README.md

@@ -2,7 +2,7 @@
 
 **Accept and make [x402](https://x402.org) crypto payments — on any EVM chain plus Solana, TON, Tron, NEAR, Sui, Aptos, Algorand, Stellar & the XRP Ledger — in a couple of lines.**
 
-No middleman, no database, no fee, no account. Payments settle **straight into your wallet**, verified locally against your own RPC. Gate a route to make it paid-only; point an agent at a paid URL and it pays itself.
+No middleman, no database, no fee, no account, no API key. Payments settle **straight into your wallet**, verified locally against your own RPC. Gate a route to make it paid-only; point an agent at a paid URL and it pays itself.
 
 ```bash
 npm install @piprail/sdk viem

package/dist/{algorand-UF7BLBFN.js → algorand-25FMBCT3.js}

@@ -1,3 +1,6 @@
+import {
+  ALGORAND_SPEC_CAIP2
+} from "./chunk-2CX7XRZK.js";
 import {
   ConfirmationTimeoutError,
   InsufficientFundsError,
@@ -110,7 +113,7 @@ async function payExactAlgorand(input) {
       "Algorand exact is ASA-only (an asset transfer); native ALGO is not exact-payable. Pay via onchain-proof."
     );
   }
-  const feePayer = accept.extra.feePayer;
+  const feePayer = accept.extra?.feePayer;
   if (!feePayer) {
     throw new UnsupportedSchemeError("Algorand exact rail must advertise extra.feePayer (the fee sponsor address).");
   }
@@ -171,7 +174,7 @@ function decodeElement(bytes) {
 }
 async function verifyAndSettleExactAlgorand(input) {
   const { client, feePayerSk, feePayerAddr, payload, accept } = input;
-  const railFeePayer = accept.extra.feePayer;
+  const railFeePayer = accept.extra?.feePayer;
   if (!railFeePayer) throw new SettlementError("Algorand exact: rail is missing extra.feePayer.");
   if (railFeePayer !== feePayerAddr) {
     throw new SettlementError("Algorand exact: the gate relayer address does not match the rail extra.feePayer \u2014 misconfigured rail.");
@@ -463,7 +466,13 @@ function makeAlgorandNetwork(preset, algodUrl) {
   return {
     family: "algorand",
     network,
-    supports: (n) => n === network,
+    // Accept our padded 44-char genesis-hash id AND the spec's 32-char truncated form
+    // (`scheme_exact_algo.md`'s Network Identifiers table — the form 874 of the 1,463 live
+    // Algorand rails use), so a caller that bypasses `normalizeNetwork` and hands the raw
+    // spec id to the driver still matches. Mirrors TON's legacy-id tolerance; the
+    // normalizeNetwork alias remains the canonical seam. We still EMIT the padded form —
+    // changing that would break every deployed PipRail 2.x buyer, so it waits for a major.
+    supports: (n) => n === network || n === ALGORAND_SPEC_CAIP2,
     resolveToken(token) {
       if (token === "native") {
         return { asset: "native", decimals: ALGO_DECIMALS, symbol: ALGO_SYMBOL };

package/dist/{algorand-XGSWDMCZ.cjs → algorand-Q3TUQLPK.cjs}

@@ -1,5 +1,8 @@
 "use strict";Object.defineProperty(exports, "__esModule", {value: true}); function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; } function _nullishCoalesce(lhs, rhsFn) { if (lhs != null) { return lhs; } else { return rhsFn(); } } function _optionalChain(ops) { let lastAccessLHS = undefined; let value = ops[0]; let i = 1; while (i < ops.length) { const op = ops[i]; const fn = ops[i + 1]; i += 2; if ((op === 'optionalAccess' || op === 'optionalCall') && value == null) { return undefined; } if (op === 'access' || op === 'optionalAccess') { lastAccessLHS = value; value = fn(value); } else if (op === 'call' || op === 'optionalCall') { value = fn((...args) => value.call(lastAccessLHS, ...args)); lastAccessLHS = undefined; } } return value; }
 
+var _chunkV2IJ5HUWcjs = require('./chunk-V2IJ5HUW.cjs');
+
+
 
 
 
@@ -110,7 +113,7 @@ async function payExactAlgorand(input) {
       "Algorand exact is ASA-only (an asset transfer); native ALGO is not exact-payable. Pay via onchain-proof."
     );
   }
-  const feePayer = accept.extra.feePayer;
+  const feePayer = _optionalChain([accept, 'access', _2 => _2.extra, 'optionalAccess', _3 => _3.feePayer]);
   if (!feePayer) {
     throw new (0, _chunkQONQSZHJcjs.UnsupportedSchemeError)("Algorand exact rail must advertise extra.feePayer (the fee sponsor address).");
   }
@@ -171,7 +174,7 @@ function decodeElement(bytes) {
 }
 async function verifyAndSettleExactAlgorand(input) {
   const { client, feePayerSk, feePayerAddr, payload, accept } = input;
-  const railFeePayer = accept.extra.feePayer;
+  const railFeePayer = _optionalChain([accept, 'access', _4 => _4.extra, 'optionalAccess', _5 => _5.feePayer]);
   if (!railFeePayer) throw new (0, _chunkQONQSZHJcjs.SettlementError)("Algorand exact: rail is missing extra.feePayer.");
   if (railFeePayer !== feePayerAddr) {
     throw new (0, _chunkQONQSZHJcjs.SettlementError)("Algorand exact: the gate relayer address does not match the rail extra.feePayer \u2014 misconfigured rail.");
@@ -206,7 +209,7 @@ async function verifyAndSettleExactAlgorand(input) {
     return fail("transfer_not_found", `Transfer asset id ${at.assetIndex} \u2260 rail asset ${assetId}.`);
   }
   if (!addrEq(at.receiver, accept.payTo)) {
-    return fail("wrong_recipient", `Transfer pays ${_optionalChain([at, 'access', _2 => _2.receiver, 'optionalAccess', _3 => _3.toString, 'call', _4 => _4()])}, not payTo ${accept.payTo}.`);
+    return fail("wrong_recipient", `Transfer pays ${_optionalChain([at, 'access', _6 => _6.receiver, 'optionalAccess', _7 => _7.toString, 'call', _8 => _8()])}, not payTo ${accept.payTo}.`);
   }
   if (BigInt(at.amount) < BigInt(accept.amount)) {
     return fail("amount_too_low", `Transfer pays ${at.amount} of the ASA, required ${accept.amount}.`);
@@ -221,7 +224,7 @@ async function verifyAndSettleExactAlgorand(input) {
     return fail("signature_invalid", "The fee transaction must be a payment (pay) transaction.");
   }
   if (!addrEq(fee.sender, railFeePayer)) {
-    return fail("signature_invalid", `The fee transaction sender ${_optionalChain([fee, 'access', _5 => _5.sender, 'optionalAccess', _6 => _6.toString, 'call', _7 => _7()])} is not the rail fee payer ${railFeePayer}.`);
+    return fail("signature_invalid", `The fee transaction sender ${_optionalChain([fee, 'access', _9 => _9.sender, 'optionalAccess', _10 => _10.toString, 'call', _11 => _11()])} is not the rail fee payer ${railFeePayer}.`);
   }
   if (BigInt(fee.payment.amount) !== 0n) {
     return fail("signature_invalid", "The fee transaction must move 0 ALGO (it only pools the group fee).");
@@ -447,12 +450,12 @@ function makeAlgorandNetwork(preset, algodUrl) {
   const settleClient = {
     async simulate(signedGroup) {
       const resp = await algod.simulateRawTransactions(signedGroup).do();
-      const fm = _optionalChain([resp, 'optionalAccess', _8 => _8.txnGroups, 'optionalAccess', _9 => _9[0], 'optionalAccess', _10 => _10.failureMessage]);
+      const fm = _optionalChain([resp, 'optionalAccess', _12 => _12.txnGroups, 'optionalAccess', _13 => _13[0], 'optionalAccess', _14 => _14.failureMessage]);
       return { failureMessage: fm && fm.length > 0 ? fm : null };
     },
     async submit(signedGroup) {
       const res = await algod.sendRawTransaction(signedGroup).do();
-      return _nullishCoalesce(_optionalChain([res, 'optionalAccess', _11 => _11.txid]), () => ( ""));
+      return _nullishCoalesce(_optionalChain([res, 'optionalAccess', _15 => _15.txid]), () => ( ""));
     },
     async waitForConfirmation(txid) {
       const info = await _algosdk2.default.waitForConfirmation(algod, txid, 10);
@@ -463,7 +466,13 @@ function makeAlgorandNetwork(preset, algodUrl) {
   return {
     family: "algorand",
     network,
-    supports: (n) => n === network,
+    // Accept our padded 44-char genesis-hash id AND the spec's 32-char truncated form
+    // (`scheme_exact_algo.md`'s Network Identifiers table — the form 874 of the 1,463 live
+    // Algorand rails use), so a caller that bypasses `normalizeNetwork` and hands the raw
+    // spec id to the driver still matches. Mirrors TON's legacy-id tolerance; the
+    // normalizeNetwork alias remains the canonical seam. We still EMIT the padded form —
+    // changing that would break every deployed PipRail 2.x buyer, so it waits for a major.
+    supports: (n) => n === network || n === _chunkV2IJ5HUWcjs.ALGORAND_SPEC_CAIP2,
     resolveToken(token) {
       if (token === "native") {
         return { asset: "native", decimals: ALGO_DECIMALS, symbol: ALGO_SYMBOL };
@@ -575,7 +584,7 @@ function makeAlgorandNetwork(preset, algodUrl) {
         const optedIn = (_nullishCoalesce(info.assets, () => ( []))).some((a) => Number(a.assetId) === assetId);
         return optedIn ? { ready: true } : { ready: false, reason: "NOT_OPTED_IN" };
       } catch (e) {
-        if (/does not exist|no accounts found|404|account not found/i.test(String(_nullishCoalesce(_optionalChain([e, 'optionalAccess', _12 => _12.message]), () => ( e))))) {
+        if (/does not exist|no accounts found|404|account not found/i.test(String(_nullishCoalesce(_optionalChain([e, 'optionalAccess', _16 => _16.message]), () => ( e))))) {
           return { ready: false, reason: "NOT_OPTED_IN" };
         }
         return { ready: "unknown" };

package/dist/{aptos-KDLX42CR.js → aptos-SBV6SGDP.js}

@@ -107,7 +107,7 @@ async function payExactAptos(input) {
       "Aptos exact is Fungible-Asset only (a primary_fungible_store transfer); native APT is not exact-payable. Pay via onchain-proof."
     );
   }
-  const feePayer = accept.extra.feePayer;
+  const feePayer = accept.extra?.feePayer;
   if (!feePayer) {
     throw new UnsupportedSchemeError("Aptos exact rail must advertise extra.feePayer (the gas sponsor address).");
   }
@@ -157,7 +157,7 @@ function argBytes(arg) {
 }
 async function verifyAndSettleExactAptos(input) {
   const { client, feePayerAddr, payload, accept } = input;
-  const railFeePayer = accept.extra.feePayer;
+  const railFeePayer = accept.extra?.feePayer;
   if (!railFeePayer) throw new SettlementError("Aptos exact: rail is missing extra.feePayer.");
   if (railFeePayer !== feePayerAddr) {
     throw new SettlementError("Aptos exact: the gate relayer address does not match the rail extra.feePayer \u2014 misconfigured rail.");

package/dist/{aptos-J2QSWHTO.cjs → aptos-VBJONBFY.cjs}

@@ -107,7 +107,7 @@ async function payExactAptos(input) {
       "Aptos exact is Fungible-Asset only (a primary_fungible_store transfer); native APT is not exact-payable. Pay via onchain-proof."
     );
   }
-  const feePayer = accept.extra.feePayer;
+  const feePayer = _optionalChain([accept, 'access', _ => _.extra, 'optionalAccess', _2 => _2.feePayer]);
   if (!feePayer) {
     throw new (0, _chunkQONQSZHJcjs.UnsupportedSchemeError)("Aptos exact rail must advertise extra.feePayer (the gas sponsor address).");
   }
@@ -151,13 +151,13 @@ function fail(error, detail) {
   return { ok: false, error, detail };
 }
 function argBytes(arg) {
-  const v = _optionalChain([arg, 'access', _ => _.value, 'optionalAccess', _2 => _2.value]);
+  const v = _optionalChain([arg, 'access', _3 => _3.value, 'optionalAccess', _4 => _4.value]);
   if (v instanceof Uint8Array) return v;
   throw new Error("unexpected entry-function argument shape");
 }
 async function verifyAndSettleExactAptos(input) {
   const { client, feePayerAddr, payload, accept } = input;
-  const railFeePayer = accept.extra.feePayer;
+  const railFeePayer = _optionalChain([accept, 'access', _5 => _5.extra, 'optionalAccess', _6 => _6.feePayer]);
   if (!railFeePayer) throw new (0, _chunkQONQSZHJcjs.SettlementError)("Aptos exact: rail is missing extra.feePayer.");
   if (railFeePayer !== feePayerAddr) {
     throw new (0, _chunkQONQSZHJcjs.SettlementError)("Aptos exact: the gate relayer address does not match the rail extra.feePayer \u2014 misconfigured rail.");
@@ -179,7 +179,7 @@ async function verifyAndSettleExactAptos(input) {
   }
   const raw = tx.rawTransaction;
   if (!tx.feePayerAddress || !tx.feePayerAddress.equals(railFeePayerAddr)) {
-    return fail("signature_invalid", `The transaction fee payer ${_nullishCoalesce(_optionalChain([tx, 'access', _3 => _3.feePayerAddress, 'optionalAccess', _4 => _4.toString, 'call', _5 => _5()]), () => ( "(none)"))} is not the rail fee payer ${railFeePayer}.`);
+    return fail("signature_invalid", `The transaction fee payer ${_nullishCoalesce(_optionalChain([tx, 'access', _7 => _7.feePayerAddress, 'optionalAccess', _8 => _8.toString, 'call', _9 => _9()]), () => ( "(none)"))} is not the rail fee payer ${railFeePayer}.`);
   }
   const payloadKind = raw.payload;
   if (!(payloadKind instanceof _tssdk.TransactionPayloadEntryFunction)) {
@@ -620,7 +620,7 @@ function makeAptosNetwork(preset, rpcUrl) {
             feePayerPublicKey: feePayerAccount.publicKey,
             transaction
           });
-          return { success: _optionalChain([sim, 'optionalAccess', _6 => _6.success]) === true, vmStatus: String(_nullishCoalesce(_optionalChain([sim, 'optionalAccess', _7 => _7.vm_status]), () => ( ""))) };
+          return { success: _optionalChain([sim, 'optionalAccess', _10 => _10.success]) === true, vmStatus: String(_nullishCoalesce(_optionalChain([sim, 'optionalAccess', _11 => _11.vm_status]), () => ( ""))) };
         },
         async submit({ transaction, senderAuthenticator, feePayerAuthenticator }) {
           const res = await aptos.transaction.submit.simple({ transaction, senderAuthenticator, feePayerAuthenticator });