uvd-x402-sdk 2.76.0 → 2.77.0

package/dist/index.d.mts

@@ -369,8 +369,6 @@ declare function sellerDigestFor(paymentId: string, contentHash: string, payee:
 /**
  * Largest `POST /dx402/anchor` request the facilitator accepts, mirroring its
  * `MAX_REQUEST_BODY_BYTES` (default 64 KiB, an anti-OOM bound on every route).
- * After base64 inflation and ~600 bytes of metadata this leaves ~47 KB of
- * plaintext.
  */
 declare const ANCHOR_MAX_REQUEST_BYTES: number;
 declare function anchorEvidence(body: Uint8Array, opts: AnchorOptions): Promise<Record<string, unknown>>;

package/dist/index.d.ts

@@ -369,8 +369,6 @@ declare function sellerDigestFor(paymentId: string, contentHash: string, payee:
 /**
  * Largest `POST /dx402/anchor` request the facilitator accepts, mirroring its
  * `MAX_REQUEST_BODY_BYTES` (default 64 KiB, an anti-OOM bound on every route).
- * After base64 inflation and ~600 bytes of metadata this leaves ~47 KB of
- * plaintext.
  */
 declare const ANCHOR_MAX_REQUEST_BYTES: number;
 declare function anchorEvidence(body: Uint8Array, opts: AnchorOptions): Promise<Record<string, unknown>>;

package/dist/index.js

@@ -1638,6 +1638,12 @@ async function anchorEvidence(body, opts) {
       // `sealed` -> it hosts and derives the pointer; `pointer` alone -> it uses
       // yours; neither -> error (x402-rs `dx402/service.rs`).
       ...pointer !== void 0 ? { pointer } : { sealed: toBase64(blob) },
+      // Declared, not measured. Since x402-rs 2.3.0 the facilitator records
+      // the store that ACTUALLY took the bytes and returns that, so a response
+      // may name a different backend than the request did -- `ipfs` where you
+      // said `s3`, because a deployment whose primary is Pinata wrote there.
+      // That is the facilitator correcting the record, not a mismatch to
+      // assert on.
       backend: opts.backend ?? (pointer !== void 0 ? backendForPointer(pointer) : "s3"),
       contentHash: hash,
       keyAlg: opts.payerKey.length === 32 ? "ECIES-X25519" : "ECIES-secp256k1",