tersign 0.5.0 → 0.6.1

package/dist/assure.d.ts

@@ -9,7 +9,8 @@ export interface AssureConfig {
     ledger?: LedgerConfig;
 }
 export interface SettlementContext {
-    /** CAIP-2 */
+    /** CAIP-2 (`"eip155:8453"`), or an x402 v1 name (`"base"`), which the receipt payload carries as
+     * CAIP-2; an unknown name throws. */
     network: string;
     resourceUrl: string;
     payer: string;
@@ -30,18 +31,79 @@ export interface IssuedReceipt {
     compliance: SignedComplianceRecord;
     ledger?: CountersignResult;
 }
-/** The core primitive: after a settled x402 payment, issue the signed base receipt
- * (merged offer-receipt extension, EIP-712) plus the Tersign compliance record bound to it,
- * and counter-sign into the hosted ledger when configured. Attach the result to the
- * SettlementResponse via `attachToExtensions`. */
+/** The core primitive: after a settled x402 payment, issue the seller-signed receipt
+ * (offer-receipt extension, EIP-712) and the Tersign compliance record. With a ledger configured,
+ * the ledger counter-signs the receipt into the seller's hash chain; the compliance-fields record is not
+ * counter-signed, and is bound to its receipt only by the seller's own signature, which covers the
+ * receipt's digest. Merge the result into the x402 SettlementResponse (the `PAYMENT-RESPONSE`
+ * header) with `attachToSettlementResponse`; `withAssure` does this for you. */
 export declare class Assure {
     private cfg;
     private ledger?;
     constructor(cfg: AssureConfig);
     issueFor(ctx: SettlementContext): Promise<IssuedReceipt>;
 }
-/** Decorate an x402 SettlementResponse body with the receipt at the spec-defined placement
- * (`extensions["offer-receipt"].info.receipt`) and the Tersign record alongside it. */
+/** JSON Schema for `extensions["offer-receipt"]` on a SettlementResponse — the same shape the
+ * upstream reference server attaches (x402-foundation/x402 typescript/packages/extensions/src/
+ * offer-receipt/server.ts RECEIPT_SCHEMA, main 5eee1e3c35, read 2026-09-29). */
+export declare const OFFER_RECEIPT_RESPONSE_SCHEMA: {
+    readonly $schema: "https://json-schema.org/draft/2020-12/schema";
+    readonly type: "object";
+    readonly properties: {
+        readonly receipt: {
+            readonly type: "object";
+            readonly properties: {
+                readonly format: {
+                    readonly type: "string";
+                };
+                readonly payload: {
+                    readonly type: "object";
+                    readonly properties: {
+                        readonly version: {
+                            readonly type: "integer";
+                        };
+                        readonly network: {
+                            readonly type: "string";
+                        };
+                        readonly resourceUrl: {
+                            readonly type: "string";
+                        };
+                        readonly payer: {
+                            readonly type: "string";
+                        };
+                        readonly issuedAt: {
+                            readonly type: "integer";
+                        };
+                        readonly transaction: {
+                            readonly type: "string";
+                        };
+                    };
+                    readonly required: readonly ["version", "network", "resourceUrl", "payer", "issuedAt"];
+                };
+                readonly signature: {
+                    readonly type: "string";
+                };
+            };
+            readonly required: readonly ["format", "signature"];
+        };
+    };
+    readonly required: readonly ["receipt"];
+};
+/** Merge the receipt and the compliance record into an x402 `SettlementResponse` — the object
+ * the HTTP transport carries, base64-encoded, in the `PAYMENT-RESPONSE` header. The receipt goes
+ * to `extensions["offer-receipt"].info.receipt` (offer-receipt spec §5.1, same for v1 and v2)
+ * with its schema; the record and its attestation to `extensions["compliance-fields"].info`
+ * (placement proposed in x402-foundation/x402#2853, open). Every other member of the settlement
+ * response, and every other extension, is kept; an `offer-receipt` entry already present is
+ * replaced, because the record binds to THIS receipt's digest. */
+export declare function attachToSettlementResponse<T extends Record<string, unknown>>(settlement: T, issued: IssuedReceipt): T & {
+    extensions: Record<string, unknown>;
+};
+/** LEGACY: decorate the resource's JSON response BODY with the same extension entries. The x402
+ * v2 HTTP transport carries protocol data in headers only ("Response bodies are a server
+ * implementation concern"), so a wallet reading `PAYMENT-RESPONSE` never sees a body placement.
+ * Kept for readers built against tersign ≤0.5; `withAssure` uses it only with
+ * `legacyBodyPlacement: true`. */
 export declare function attachToExtensions<T extends Record<string, unknown>>(responseBody: T, issued: IssuedReceipt): T & {
     extensions: Record<string, unknown>;
 };

package/dist/assure.js

@@ -1,10 +1,13 @@
 import { signReceipt } from './receipt/eip712.js';
+import { toCaip2Network } from './receipt/network.js';
 import { buildMinimalRecord, signComplianceRecord } from './compliance/record.js';
 import { LedgerClient } from './ledgerClient.js';
-/** The core primitive: after a settled x402 payment, issue the signed base receipt
- * (merged offer-receipt extension, EIP-712) plus the Tersign compliance record bound to it,
- * and counter-sign into the hosted ledger when configured. Attach the result to the
- * SettlementResponse via `attachToExtensions`. */
+/** The core primitive: after a settled x402 payment, issue the seller-signed receipt
+ * (offer-receipt extension, EIP-712) and the Tersign compliance record. With a ledger configured,
+ * the ledger counter-signs the receipt into the seller's hash chain; the compliance-fields record is not
+ * counter-signed, and is bound to its receipt only by the seller's own signature, which covers the
+ * receipt's digest. Merge the result into the x402 SettlementResponse (the `PAYMENT-RESPONSE`
+ * header) with `attachToSettlementResponse`; `withAssure` does this for you. */
 export class Assure {
     cfg;
     ledger;
@@ -16,7 +19,7 @@ export class Assure {
     async issueFor(ctx) {
         const payload = {
             version: 1,
-            network: ctx.network,
+            network: toCaip2Network(ctx.network),
             resourceUrl: ctx.resourceUrl,
             payer: ctx.payer,
             issuedAt: ctx.settledAt,
@@ -45,8 +48,71 @@ export class Assure {
         return { receipt, compliance, ledger };
     }
 }
-/** Decorate an x402 SettlementResponse body with the receipt at the spec-defined placement
- * (`extensions["offer-receipt"].info.receipt`) and the Tersign record alongside it. */
+/** JSON Schema for `extensions["offer-receipt"]` on a SettlementResponse — the same shape the
+ * upstream reference server attaches (x402-foundation/x402 typescript/packages/extensions/src/
+ * offer-receipt/server.ts RECEIPT_SCHEMA, main 5eee1e3c35, read 2026-09-29). */
+export const OFFER_RECEIPT_RESPONSE_SCHEMA = {
+    $schema: 'https://json-schema.org/draft/2020-12/schema',
+    type: 'object',
+    properties: {
+        receipt: {
+            type: 'object',
+            properties: {
+                format: { type: 'string' },
+                payload: {
+                    type: 'object',
+                    properties: {
+                        version: { type: 'integer' },
+                        network: { type: 'string' },
+                        resourceUrl: { type: 'string' },
+                        payer: { type: 'string' },
+                        issuedAt: { type: 'integer' },
+                        transaction: { type: 'string' },
+                    },
+                    required: ['version', 'network', 'resourceUrl', 'payer', 'issuedAt'],
+                },
+                signature: { type: 'string' },
+            },
+            required: ['format', 'signature'],
+        },
+    },
+    required: ['receipt'],
+};
+function complianceInfo(issued) {
+    return {
+        record: issued.compliance.record,
+        attestation: issued.compliance.attestation,
+        ...(issued.ledger
+            ? { ledger: { seq: issued.ledger.seq, digest: issued.ledger.digest, countersignature: issued.ledger.countersignature } }
+            : {}),
+    };
+}
+/** Merge the receipt and the compliance record into an x402 `SettlementResponse` — the object
+ * the HTTP transport carries, base64-encoded, in the `PAYMENT-RESPONSE` header. The receipt goes
+ * to `extensions["offer-receipt"].info.receipt` (offer-receipt spec §5.1, same for v1 and v2)
+ * with its schema; the record and its attestation to `extensions["compliance-fields"].info`
+ * (placement proposed in x402-foundation/x402#2853, open). Every other member of the settlement
+ * response, and every other extension, is kept; an `offer-receipt` entry already present is
+ * replaced, because the record binds to THIS receipt's digest. */
+export function attachToSettlementResponse(settlement, issued) {
+    const prior = isPlainRecord(settlement.extensions) ? settlement.extensions : {};
+    return {
+        ...settlement,
+        extensions: {
+            ...prior,
+            'offer-receipt': { info: { receipt: issued.receipt }, schema: OFFER_RECEIPT_RESPONSE_SCHEMA },
+            'compliance-fields': { info: complianceInfo(issued) },
+        },
+    };
+}
+function isPlainRecord(v) {
+    return typeof v === 'object' && v !== null && !Array.isArray(v);
+}
+/** LEGACY: decorate the resource's JSON response BODY with the same extension entries. The x402
+ * v2 HTTP transport carries protocol data in headers only ("Response bodies are a server
+ * implementation concern"), so a wallet reading `PAYMENT-RESPONSE` never sees a body placement.
+ * Kept for readers built against tersign ≤0.5; `withAssure` uses it only with
+ * `legacyBodyPlacement: true`. */
 export function attachToExtensions(responseBody, issued) {
     const prior = (responseBody.extensions ?? {});
     return {
@@ -54,15 +120,7 @@ export function attachToExtensions(responseBody, issued) {
         extensions: {
             ...prior,
             'offer-receipt': { info: { receipt: issued.receipt } },
-            'compliance-fields': {
-                info: {
-                    record: issued.compliance.record,
-                    attestation: issued.compliance.attestation,
-                    ...(issued.ledger
-                        ? { ledger: { seq: issued.ledger.seq, digest: issued.ledger.digest, countersignature: issued.ledger.countersignature } }
-                        : {}),
-                },
-            },
+            'compliance-fields': { info: complianceInfo(issued) },
         },
     };
 }

package/dist/compliance/record.d.ts

@@ -1,8 +1,8 @@
 import type { Account } from 'viem/accounts';
 import type { Adjustment, ComplianceRecordV1, SignedComplianceRecord, SignedReceipt, VerifyLike } from './types.js';
 import { type SignerBinding } from '../receipt/binding.js';
-/** Canonical domain per the compliance-fields extension spec (x402-foundation/x402#2853).
- * Migrated from the vendor domain 'tersign compliance-record' on 2026-07-14 while ZERO
+/** EIP-712 domain named in the proposed compliance-fields extension (x402-foundation/x402#2853,
+ * open — proposed, not settled spec). Migrated from the vendor domain 'tersign compliance-record' on 2026-07-14 while ZERO
  * production compliance records existed — a free change then, a breaking wire change after. */
 export declare const COMPLIANCE_DOMAIN: {
     readonly name: "compliance-fields";
@@ -32,7 +32,8 @@ export interface IssuerConfig {
     name: string;
     jurisdiction: string;
     taxId?: string;
-    /** default 7 — HK IRO s.51C floor, ≥ MiCA 5+2 */
+    /** default 7 where no longer period applies (HK IRO s.51C, MiCA 5+2) — set the longest period
+     * that applies to you (e.g. DE § 14b UStG: eight years); 7 is a default, not a sufficiency claim */
     retentionYears?: number;
 }
 export interface MinimalRecordInput {
@@ -45,8 +46,13 @@ export interface MinimalRecordInput {
     refundOf?: `0x${string}`;
     adjustment?: Adjustment;
 }
-/** MINIMAL tier ≈ EU VAT Art 226b simplified-invoice content — legally sufficient for
- * sub-€100 supplies EU-wide, and the default for machine-to-machine micro-receipts. */
+/** Build a record carrying the MINIMAL members of the proposed compliance-fields extension —
+ * content isomorphic to the EU VAT Art 226b simplified invoice. Whether it suffices as an invoice
+ * is decided by the invoicing rules that apply to the supply (Art 219a): Art 220a(1)(a) makes
+ * every Member State allow simplified invoices up to EUR 100, a Member State may require further
+ * details on them (Art 226b), and some supplies can never use one (Art 220(1)(2)-(3), Art 220a(2),
+ * and national bars). MINIMAL needs `tax.amount` whenever `tax.scheme` is not `none`; that is the caller's
+ * input. `seq` is not set here: it is the issuer's to assign before attestation. */
 export declare function buildMinimalRecord(issuer: IssuerConfig, input: MinimalRecordInput): ComplianceRecordV1;
 export declare function recordDigest(record: ComplianceRecordV1): `0x${string}`;
 export declare function signComplianceRecord(record: ComplianceRecordV1, account: Account): Promise<SignedComplianceRecord>;

package/dist/compliance/record.js

@@ -1,8 +1,8 @@
 import { recoverTypedDataAddress } from 'viem';
 import { digestOf } from '../canonical.js';
 import { bindSigner, isPlainObject, parseExpectedSigner, signatureError } from '../receipt/binding.js';
-/** Canonical domain per the compliance-fields extension spec (x402-foundation/x402#2853).
- * Migrated from the vendor domain 'tersign compliance-record' on 2026-07-14 while ZERO
+/** EIP-712 domain named in the proposed compliance-fields extension (x402-foundation/x402#2853,
+ * open — proposed, not settled spec). Migrated from the vendor domain 'tersign compliance-record' on 2026-07-14 while ZERO
  * production compliance records existed — a free change then, a breaking wire change after. */
 export const COMPLIANCE_DOMAIN = { name: 'compliance-fields', version: '1', chainId: 1n };
 export const COMPLIANCE_TYPES = {
@@ -20,11 +20,17 @@ export const COMPLIANCE_WIRE_VECTOR = digestOf({
     domain: { ...COMPLIANCE_DOMAIN, chainId: 1 },
     types: COMPLIANCE_TYPES,
 });
-/** MINIMAL tier ≈ EU VAT Art 226b simplified-invoice content — legally sufficient for
- * sub-€100 supplies EU-wide, and the default for machine-to-machine micro-receipts. */
+/** Build a record carrying the MINIMAL members of the proposed compliance-fields extension —
+ * content isomorphic to the EU VAT Art 226b simplified invoice. Whether it suffices as an invoice
+ * is decided by the invoicing rules that apply to the supply (Art 219a): Art 220a(1)(a) makes
+ * every Member State allow simplified invoices up to EUR 100, a Member State may require further
+ * details on them (Art 226b), and some supplies can never use one (Art 220(1)(2)-(3), Art 220a(2),
+ * and national bars). MINIMAL needs `tax.amount` whenever `tax.scheme` is not `none`; that is the caller's
+ * input. `seq` is not set here: it is the issuer's to assign before attestation. */
 export function buildMinimalRecord(issuer, input) {
     const record = {
         version: 1,
+        canonicalizationVersion: 1,
         receiptDigest: digestOf(input.receipt),
         issuedAt: input.issuedAt,
         issuer: {

package/dist/index.d.ts

@@ -3,6 +3,7 @@ export { canonicalStringify, digestOf, GENESIS_DIGEST, chainLinkDigest, CHAIN_CO
 export { RECEIPT_DOMAIN, RECEIPT_TYPES, OFFER_DOMAIN, OFFER_TYPES, signReceipt, signOffer, verifyReceipt, SIGNED_RECEIPT_FIELDS, type VerifyResult, } from './receipt/eip712.js';
 export { PUBLISHED_TEST_KEYS, publishedKeyLabel } from './receipt/known-keys.js';
 export { signerStatus, type SignerBinding, type SignerStatus } from './receipt/binding.js';
+export { toCaip2Network } from './receipt/network.js';
 export { COMPLIANCE_DOMAIN, COMPLIANCE_TYPES, COMPLIANCE_WIRE_VECTOR, buildMinimalRecord, recordDigest, signComplianceRecord, verifyComplianceRecord, type RecordVerifyResult, type IssuerConfig, type MinimalRecordInput, } from './compliance/record.js';
 export { MemoryIdempotencyStore, checkIdempotency, extractPaymentId, fingerprint, REPLAY_HEADER, type IdempotencyStore, type IdempotencyOutcome, type IdempotencyOptions, type CachedResponse, type FingerprintParts, } from './idempotency/middleware.js';
 export { D1IdempotencyStore, D1_IDEMPOTENCY_DDL, type D1Like } from './idempotency/d1.js';
@@ -11,7 +12,7 @@ export { DISPUTE_DOMAIN, EVIDENCE_DOMAIN, CRITERIA_DOMAIN, DISPUTE_TYPES, EVIDEN
 export { ACTION_DOMAIN, ACTION_TYPES, ACTION_WIRE_VECTOR, actionDigest, signActionRecord, verifyActionRecord, type ActionKind, type DisclosureKind, type GovernanceOutcome, type ActionRecordV1, type ActionAttestationPayload, type SignedActionRecord, } from './evidence/action.js';
 export { recordDisclosure, type RecordDisclosureOptions, type RecordDisclosureResult } from './evidence/disclose.js';
 export { LedgerClient, type LedgerConfig, type CountersignResult } from './ledgerClient.js';
-export { Assure, attachToExtensions, type AssureConfig, type SettlementContext, type IssuedReceipt } from './assure.js';
-export { withAssure, extractSettlement, extractPaymentPayload, type WithAssureConfig, type SettlementInfo } from './adapter/x402.js';
+export { Assure, attachToExtensions, attachToSettlementResponse, OFFER_RECEIPT_RESPONSE_SCHEMA, type AssureConfig, type SettlementContext, type IssuedReceipt, } from './assure.js';
+export { withAssure, extractSettlement, extractPaymentPayload, encodeX402Header, decodeX402Header, COMPLIANCE_FIELDS_ADVERTISEMENT_SCHEMA, type WithAssureConfig, type SettlementInfo, type ComplianceAdvertisement, } from './adapter/x402.js';
 export { ENVELOPE_STATEMENT_MAX_CHARS, VENUE_SUBMISSION_MAX_CHARS, ENVELOPE_VENUES, type EvidenceEnvelopeV1, type EnvelopeSubjectKind, type EnvelopeVenue, } from './envelope/types.js';
 export { assertEnvelopeCaps, toInternetCourtSubmission, toKlerosEvidence, toUMAClaim, type Kleros1497Evidence, } from './envelope/serialize.js';

package/dist/index.js

@@ -3,6 +3,7 @@ export { canonicalStringify, digestOf, GENESIS_DIGEST, chainLinkDigest, CHAIN_CO
 export { RECEIPT_DOMAIN, RECEIPT_TYPES, OFFER_DOMAIN, OFFER_TYPES, signReceipt, signOffer, verifyReceipt, SIGNED_RECEIPT_FIELDS, } from './receipt/eip712.js';
 export { PUBLISHED_TEST_KEYS, publishedKeyLabel } from './receipt/known-keys.js';
 export { signerStatus } from './receipt/binding.js';
+export { toCaip2Network } from './receipt/network.js';
 export { COMPLIANCE_DOMAIN, COMPLIANCE_TYPES, COMPLIANCE_WIRE_VECTOR, buildMinimalRecord, recordDigest, signComplianceRecord, verifyComplianceRecord, } from './compliance/record.js';
 export { MemoryIdempotencyStore, checkIdempotency, extractPaymentId, fingerprint, REPLAY_HEADER, } from './idempotency/middleware.js';
 export { D1IdempotencyStore, D1_IDEMPOTENCY_DDL } from './idempotency/d1.js';
@@ -10,7 +11,7 @@ export { DISPUTE_DOMAIN, EVIDENCE_DOMAIN, CRITERIA_DOMAIN, DISPUTE_TYPES, EVIDEN
 export { ACTION_DOMAIN, ACTION_TYPES, ACTION_WIRE_VECTOR, actionDigest, signActionRecord, verifyActionRecord, } from './evidence/action.js';
 export { recordDisclosure } from './evidence/disclose.js';
 export { LedgerClient } from './ledgerClient.js';
-export { Assure, attachToExtensions } from './assure.js';
-export { withAssure, extractSettlement, extractPaymentPayload } from './adapter/x402.js';
+export { Assure, attachToExtensions, attachToSettlementResponse, OFFER_RECEIPT_RESPONSE_SCHEMA, } from './assure.js';
+export { withAssure, extractSettlement, extractPaymentPayload, encodeX402Header, decodeX402Header, COMPLIANCE_FIELDS_ADVERTISEMENT_SCHEMA, } from './adapter/x402.js';
 export { ENVELOPE_STATEMENT_MAX_CHARS, VENUE_SUBMISSION_MAX_CHARS, ENVELOPE_VENUES, } from './envelope/types.js';
 export { assertEnvelopeCaps, toInternetCourtSubmission, toKlerosEvidence, toUMAClaim, } from './envelope/serialize.js';

package/dist/ledgerClient.d.ts

@@ -22,8 +22,11 @@ export declare class LedgerClient {
     constructor(cfg: LedgerConfig);
     private get f();
     submitReceipt(artifact: SignedReceipt, compliance?: SignedComplianceRecord): Promise<CountersignResult>;
+    /** Log a refund against a receipt on this seller's chain. The ledger stores a PENDING refund
+     * entry; it is not counter-signed or chained, so the answer carries no digest or seq. */
     recordRefund(originalDigest: `0x${string}`, amount: string, reason: string): Promise<{
         id: string;
+        status: string;
     }>;
     /** Fetch the venue-neutral evidence envelope for a chained artifact (public endpoint — works
      * without an API key; the apiKey/sellerId in cfg are unused here). `statement` is an optional

package/dist/ledgerClient.js

@@ -23,6 +23,8 @@ export class LedgerClient {
             throw new Error(`ledger submit failed: ${res.status} ${await res.text()}`);
         return (await res.json());
     }
+    /** Log a refund against a receipt on this seller's chain. The ledger stores a PENDING refund
+     * entry; it is not counter-signed or chained, so the answer carries no digest or seq. */
     async recordRefund(originalDigest, amount, reason) {
         const res = await this.f(`${this.cfg.url}/v1/refunds`, {
             method: 'POST',

package/dist/mcp/server.d.ts

@@ -8,6 +8,6 @@ export declare function envDeps(env?: Record<string, string | undefined>): McpDe
  * every client; mcp.test.ts pins it against package.json so a release bump can't drift it. */
 export declare const MCP_SERVER_IDENTITY: {
     readonly name: "tersign";
-    readonly version: "0.5.0";
+    readonly version: "0.6.1";
 };
 export declare function buildServer(deps: McpDeps): McpServer;

package/dist/mcp/server.js

@@ -53,12 +53,12 @@ function json(value) {
 }
 /** MUST match package.json name/version — the MCP handshake self-reports this identity to
  * every client; mcp.test.ts pins it against package.json so a release bump can't drift it. */
-export const MCP_SERVER_IDENTITY = { name: 'tersign', version: '0.5.0' };
+export const MCP_SERVER_IDENTITY = { name: 'tersign', version: '0.6.1' };
 export function buildServer(deps) {
     const server = new McpServer(MCP_SERVER_IDENTITY);
     server.registerTool('issue_receipt', {
         title: 'Issue signed receipt',
-        description: 'Issue an x402 offer-receipt (EIP-712) plus a Tersign compliance record (returned as `compliance`; verify_compliance_record checks it) for a payment that has ALREADY settled, and counter-sign both into your hash chain when a ledger is configured. ' +
+        description: 'Issue an x402 offer-receipt (EIP-712) plus a Tersign compliance record (returned as `compliance`; verify_compliance_record checks it) for a payment that has ALREADY settled; when a ledger is configured, the ledger counter-signs the receipt into your hash chain, while the compliance-fields record is not counter-signed and is bound to its receipt only by your own signature, which covers the receipt\'s digest. ' +
             'Use this for money that moved; use record_disclosure for a non-payment agent action. ' +
             'Side effects: signs with your signing key (TERSIGN_SELLER_KEY when set, else the one generated and kept locally on first run), and performs ONE network write to the ledger when TERSIGN_LEDGER_URL/_API_KEY/_SELLER_ID are set (without them it signs locally and returns an unchained artifact). ' +
             'Returns the signed receipt artifact, its keccak256 canonical digest, and — when chained — the ledger counter-signature and sequence number.',
@@ -133,10 +133,10 @@ export function buildServer(deps) {
     }, async ({ record, attestation, expectedSigner }) => json(await verifyRecordTool(record, attestation, expectedSigner)));
     server.registerTool('record_refund', {
         title: 'Record refund',
-        description: 'Record a refund against an already-chained receipt, as the SELLER. The refund becomes its own counter-signed entry that references the original — nothing is edited or deleted, so the chain stays append-only and both the charge and the refund remain visible. ' +
+        description: 'Log a refund against a receipt already on your chain, as the SELLER. The ledger stores it as a PENDING refund entry that references the original receipt digest; the entry is NOT counter-signed or appended to the hash chain, and it has no digest or sequence number of its own. Nothing is edited or deleted: the original receipt and its chain position stay exactly as they were. ' +
             'Requires ledger configuration (TERSIGN_LEDGER_URL/_API_KEY/_SELLER_ID) and performs one network write; errors if the original digest is not on your chain. ' +
-            'This RECORDS a refund you have already made — it moves no money. ' +
-            'Returns the refund record, its digest, the ledger counter-signature and sequence number.',
+            'This RECORDS a refund you have already made — it moves no money. For a signed refund RECORD, build a compliance record with refundOf set to the original record digest (buildMinimalRecord in the SDK). ' +
+            'Returns { id, status: "pending" }.',
         inputSchema: {
             originalDigest: z
                 .string()
@@ -190,9 +190,9 @@ export function buildServer(deps) {
     })));
     server.registerTool('adjudicate_dispute', {
         title: 'Adjudicate dispute',
-        description: 'Trigger deterministic adjudication of an open dispute. The v0 rulebook is public and the verdict is recomputable by anyone from the chain — no discretion, no model in the loop. ' +
-            'Side effects: writes a verdict entry, and a refund verdict automatically creates the corresponding refund record. Adjudicating twice is not meaningful; the first verdict stands. ' +
-            'Returns the verdict, the rationale naming the rule applied, and the ledger signature over both.',
+        description: 'Trigger deterministic adjudication of an open dispute: the same inputs always produce the same verdict and rationale — no discretion, no model in the loop — and the verdict object embeds the inputs it was computed from. ' +
+            'Side effects: writes the verdict to the dispute record; a refund verdict also logs a PENDING refund entry against the receipt (not counter-signed into the chain; no money moves). Adjudicating twice is not meaningful; the first verdict stands (a second call returns 409). ' +
+            'Returns the verdict, the rationale naming the rule applied, the adjudication inputs, the verdict digest, and the ledger signature over that digest.',
         inputSchema: {
             disputeDigest: digestSchema.describe('0x-prefixed digest of the open dispute to adjudicate, as returned by open_dispute'),
         },

package/dist/mcp/tools.d.ts

@@ -52,6 +52,7 @@ export declare function verifyReceiptTool(artifact: SignedReceipt, expectedSigne
 export declare function verifyRecordTool(record: ComplianceRecordV1, attestation: SignedComplianceRecord['attestation'], expectedSigner?: string): Promise<VerifyToolResult>;
 export declare function recordRefundTool(deps: McpDeps, originalDigest: `0x${string}`, amount: string, reason: string): Promise<{
     id: string;
+    status: string;
 }>;
 export interface OpenDisputeArgs {
     receiptDigest: `0x${string}`;
@@ -68,8 +69,8 @@ export interface SubmitEvidenceArgs {
     artifacts: EvidenceArtifactRef[];
 }
 export declare function submitEvidenceTool(deps: McpDeps, args: SubmitEvidenceArgs): Promise<unknown>;
-/** Trigger deterministic adjudication (public — the rulebook is recomputable, so anyone
- * may pull the trigger once the route guard allows it). */
+/** Trigger deterministic adjudication (no API key — the outcome is a deterministic function of
+ * the recorded inputs, so anyone may pull the trigger once the route guard allows it). */
 export declare function adjudicateDisputeTool(deps: McpDeps, disputeDigest: `0x${string}`): Promise<unknown>;
 export declare function getDisputeTool(deps: McpDeps, disputeDigest: `0x${string}`): Promise<unknown>;
 export interface RecordDisclosureArgs {

package/dist/mcp/tools.js

@@ -119,8 +119,8 @@ export async function submitEvidenceTool(deps, args) {
         ...(args.role === 'respondent' && deps.ledgerHttp.apiKey !== undefined ? { apiKey: deps.ledgerHttp.apiKey } : {}),
     });
 }
-/** Trigger deterministic adjudication (public — the rulebook is recomputable, so anyone
- * may pull the trigger once the route guard allows it). */
+/** Trigger deterministic adjudication (no API key — the outcome is a deterministic function of
+ * the recorded inputs, so anyone may pull the trigger once the route guard allows it). */
 export async function adjudicateDisputeTool(deps, disputeDigest) {
     if (!deps.ledgerHttp)
         throw new Error('ledger URL not configured — set TERSIGN_LEDGER_URL');

package/dist/receipt/binding.d.ts

@@ -32,7 +32,10 @@ export declare function signerStatus(r: SignerBinding, expected: string | undefi
 export declare function bindSigner(signer: `0x${string}`, expected: string | undefined, mismatchReason: string): SignerBinding;
 /** Why an EIP-712 `signature` is not THE canonical encoding, or undefined. Checked BEFORE
  * recovery, with the same rules as the Python twin's verify_receipt (sdk-py tersign/verify.py
- * signature_error). The canonical encoding is exactly one string per signer and message:
+ * signature_error). Each signature has exactly one accepted string, so a re-encoding of it is
+ * refused. That is a property of one signature, not of a signer and message: the signer can
+ * produce other valid signatures over the same message, so key any deduplication on (signer,
+ * message), never on the signature bytes. The accepted string is:
  *
  *   "0x" + 130 LOWER-CASE hex digits = r (32 bytes) || s (32 bytes) || v (1 byte), with
  *   1 <= r, s < n; s <= n/2 (low-s); v = 27 or 28 (0x1b / 0x1c) — what viem's

package/dist/receipt/binding.js

@@ -48,7 +48,10 @@ export function bindSigner(signer, expected, mismatchReason) {
 const SECP256K1_N = 0xfffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd0364141n;
 /** Why an EIP-712 `signature` is not THE canonical encoding, or undefined. Checked BEFORE
  * recovery, with the same rules as the Python twin's verify_receipt (sdk-py tersign/verify.py
- * signature_error). The canonical encoding is exactly one string per signer and message:
+ * signature_error). Each signature has exactly one accepted string, so a re-encoding of it is
+ * refused. That is a property of one signature, not of a signer and message: the signer can
+ * produce other valid signatures over the same message, so key any deduplication on (signer,
+ * message), never on the signature bytes. The accepted string is:
  *
  *   "0x" + 130 LOWER-CASE hex digits = r (32 bytes) || s (32 bytes) || v (1 byte), with
  *   1 <= r, s < n; s <= n/2 (low-s); v = 27 or 28 (0x1b / 0x1c) — what viem's

package/dist/receipt/network.d.ts

@@ -0,0 +1,31 @@
+/** x402 v1 network names → CAIP-2, for the receipt payload.
+ *
+ * The offer-receipt extension requires CAIP-2 in the signed payload whatever the protocol version:
+ * "Servers MUST convert v1 network identifiers (e.g., "base-sepolia") to CAIP-2 format (e.g.,
+ * "eip155:84532") in the receipt payload" (x402-foundation/x402 specs/extensions/
+ * extension-offer-and-receipt.md, receipt section; present at main 6b6ee91fee02, read 2026-09-29).
+ * A v1 settlement response carries the v1 name (`"base"`), so a receipt built from it without this
+ * step signs a payload that fails the spec.
+ *
+ * The EVM table is upstream `@x402/evm`'s `EVM_NETWORK_CHAIN_ID_MAP`, copied as written
+ * (typescript/packages/mechanisms/evm/src/constants.ts, blob ab7db42cc1c0: main 6b6ee91fee02, last
+ * changed a9955ae5538e, read 2026-09-29). Those 24 names are the ones upstream's v1 EVM facilitator
+ * settles and reports back as `network`, so each can reach a receipt. The offer-receipt reference's
+ * own table (typescript/packages/extensions/src/offer-receipt/signing.ts `V1_EVM_NETWORK_CHAIN_IDS`,
+ * same commit) holds 17 of them, with the same ids. The Solana table is signing.ts
+ * `V1_SOLANA_NETWORKS`, identical to `@x402/svm`'s `V1_TO_V2_NETWORK_MAP`
+ * (mechanisms/svm/src/constants.ts, same commit). The rules are signing.ts
+ * `convertNetworkStringToCAIP2`'s: a string containing `:` passes through unchanged, a known v1 name
+ * is looked up case-insensitively, anything else throws. One difference: the lookup reads own keys
+ * only, so an inherited object key such as `constructor` throws instead of resolving. Re-check
+ * against both upstream files when a v1 network is added there; test/network.test.ts pins both
+ * tables by exact equality.
+ *
+ * The tables are exported for that test only; the package entry re-exports `toCaip2Network`, not
+ * them. */
+export declare const V1_EVM_NETWORK_CHAIN_IDS: Readonly<Record<string, number>>;
+export declare const V1_SOLANA_NETWORKS: Readonly<Record<string, string>>;
+/** A CAIP-2 identifier passes through; a known x402 v1 name (`"base"`, `"base-sepolia"`,
+ * `"solana"`, …) becomes its CAIP-2 form; anything else throws, because a receipt cannot carry
+ * it. */
+export declare function toCaip2Network(network: string): string;

package/dist/receipt/network.js

@@ -0,0 +1,71 @@
+/** x402 v1 network names → CAIP-2, for the receipt payload.
+ *
+ * The offer-receipt extension requires CAIP-2 in the signed payload whatever the protocol version:
+ * "Servers MUST convert v1 network identifiers (e.g., "base-sepolia") to CAIP-2 format (e.g.,
+ * "eip155:84532") in the receipt payload" (x402-foundation/x402 specs/extensions/
+ * extension-offer-and-receipt.md, receipt section; present at main 6b6ee91fee02, read 2026-09-29).
+ * A v1 settlement response carries the v1 name (`"base"`), so a receipt built from it without this
+ * step signs a payload that fails the spec.
+ *
+ * The EVM table is upstream `@x402/evm`'s `EVM_NETWORK_CHAIN_ID_MAP`, copied as written
+ * (typescript/packages/mechanisms/evm/src/constants.ts, blob ab7db42cc1c0: main 6b6ee91fee02, last
+ * changed a9955ae5538e, read 2026-09-29). Those 24 names are the ones upstream's v1 EVM facilitator
+ * settles and reports back as `network`, so each can reach a receipt. The offer-receipt reference's
+ * own table (typescript/packages/extensions/src/offer-receipt/signing.ts `V1_EVM_NETWORK_CHAIN_IDS`,
+ * same commit) holds 17 of them, with the same ids. The Solana table is signing.ts
+ * `V1_SOLANA_NETWORKS`, identical to `@x402/svm`'s `V1_TO_V2_NETWORK_MAP`
+ * (mechanisms/svm/src/constants.ts, same commit). The rules are signing.ts
+ * `convertNetworkStringToCAIP2`'s: a string containing `:` passes through unchanged, a known v1 name
+ * is looked up case-insensitively, anything else throws. One difference: the lookup reads own keys
+ * only, so an inherited object key such as `constructor` throws instead of resolving. Re-check
+ * against both upstream files when a v1 network is added there; test/network.test.ts pins both
+ * tables by exact equality.
+ *
+ * The tables are exported for that test only; the package entry re-exports `toCaip2Network`, not
+ * them. */
+export const V1_EVM_NETWORK_CHAIN_IDS = {
+    ethereum: 1,
+    sepolia: 11155111,
+    abstract: 2741,
+    'abstract-testnet': 11124,
+    'base-sepolia': 84532,
+    base: 8453,
+    'avalanche-fuji': 43113,
+    avalanche: 43114,
+    iotex: 4689,
+    sei: 1329,
+    'sei-testnet': 1328,
+    polygon: 137,
+    'polygon-amoy': 80002,
+    peaq: 3338,
+    story: 1514,
+    educhain: 41923,
+    'skale-base-sepolia': 324705682,
+    megaeth: 4326,
+    monad: 143,
+    'monad-testnet': 10143,
+    stable: 988,
+    'stable-testnet': 2201,
+    celo: 42220,
+    flare: 14,
+};
+export const V1_SOLANA_NETWORKS = {
+    solana: 'solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp',
+    'solana-devnet': 'solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1',
+    'solana-testnet': 'solana:4uhcVJyU9pJkvQyS88uRDiswHXSCkY3z',
+};
+/** A CAIP-2 identifier passes through; a known x402 v1 name (`"base"`, `"base-sepolia"`,
+ * `"solana"`, …) becomes its CAIP-2 form; anything else throws, because a receipt cannot carry
+ * it. */
+export function toCaip2Network(network) {
+    if (network.includes(':'))
+        return network;
+    const key = network.toLowerCase();
+    const chainId = Object.hasOwn(V1_EVM_NETWORK_CHAIN_IDS, key) ? V1_EVM_NETWORK_CHAIN_IDS[key] : undefined;
+    if (chainId !== undefined)
+        return `eip155:${chainId}`;
+    const solana = Object.hasOwn(V1_SOLANA_NETWORKS, key) ? V1_SOLANA_NETWORKS[key] : undefined;
+    if (solana !== undefined)
+        return solana;
+    throw new Error(`Unknown network identifier: "${network}". A receipt needs CAIP-2 (e.g. "eip155:8453") or an x402 v1 name (e.g. "base", "solana").`);
+}