* Adding batch settlement details, plus a general cleanup of some stale content and onchain vs on-chain typos
* Additional minor polishing updates
* Merging SDK features mechanisms table with main and adding batch-settlement to resolve conflict
* feat(evm): add Radius Network and Radius Testnet default stablecoin (Permit2 + EIP-2612)
Add SBC as the default stablecoin for Radius Network (eip155:723487)
and Radius Testnet (eip155:72344) across Go, TypeScript, and Python SDKs.
SBC does not support EIP-3009, so Permit2 is the required transfer
method. SBC does support EIP-2612 permit() for gasless approval.
* docs: add Radius default-stablecoin entries to user-facing docs
* chore(paywall): update generated Radius decimals
* add mcp discovery support
* ci fixes and changelog
* rename changelog
* fix failing test
* fail in TS on transport mismatch, return extension info on settlement failure in python
* add e2e
* fix mcp payment payload parsing
* fix python parsing
* add transport to examples and docs
* docs: add Documentation Checklist + surface chain-contribution flow
DEFAULT_ASSETS.md's 'Adding a New Chain' numbered flow stopped at 'Update
all three SDKs' → 'Submit a PR' and did not mention the user-facing docs
surfaces that also enumerate every chain with default-asset support. As a
result, recent onboarding PRs have shipped with stale docs (e.g. the
Radius PR #2038 updated the SDKs but not the docs table or Go README).
The existing Cross-SDK Checklist at the bottom enumerates only the three
code registries, mirroring the same gap.
network-and-token-support.mdx has a parallel discoverability problem:
the pointer to DEFAULT_ASSETS.md used a repo-relative path that resolves
to a broken link on docs.x402.org, and the pointer sat inside the
'Default Assets for Dollar-String Pricing' intro rather than under
'Adding Support for New Networks' where a would-be contributor actually
looks. The 'Adding' section itself described only runtime registration
(server.register from consumer code) and did not mention the separate
upstream-contribution path, and it also contained a 'Running Your Own
Facilitator' subsection that is about facilitator infrastructure, not
about adding networks — a topical mismatch. The page also ordered the
'Facilitators' section before 'Adding Support for New Networks', which
inverts the natural read → use → extend → operate narrative.
Changes:
* DEFAULT_ASSETS.md:
- Promote 'Update user-facing documentation' to a numbered step in
'Adding a New Chain' (new step 3, between 'Update all three SDKs'
and 'Submit a PR'), with a cross-reference to the new checklist.
- Append a new 'Documentation Checklist' section below the existing
Cross-SDK Checklist, naming the two hot docs surfaces
(network-and-token-support.mdx and go/mechanisms/evm/README.md)
that must also be updated on a new chain onboarding.
* docs/core-concepts/network-and-token-support.mdx:
- Remove the oddly-placed 'See DEFAULT_ASSETS.md' link from the
Dollar-String Pricing intro; replace with an in-page anchor
pointing at the new contribution subsection.
- Split 'Adding Support for New Networks' into two subsections:
'Runtime Registration' (the existing content, unchanged) and
a new 'Contributing a New Default Asset' subsection that links
to DEFAULT_ASSETS.md via an absolute github.com URL (so the
link works on the published docs site) and explicitly names
the cross-SDK + docs checklist.
- Move 'Running Your Own Facilitator' out of 'Adding Support for
New Networks' into the existing 'Facilitators' section, where
it belongs topically.
- Swap top-level section order: 'Adding Support for New Networks'
now precedes 'Facilitators', matching the read → use → extend →
operate narrative.
No code changes. Documentation only.
* docs: revert DEFAULT_ASSETS.md, unify SDK READMEs to link docs
Address review feedback: the Mintlify agent (.github/workflows/update-docs.yml)
keeps docs/ in sync with code, so contributors should only update the three SDK
constants files. Remove the Documentation Checklist and Step 3 from
DEFAULT_ASSETS.md. Apply a consistent two-link block to all three SDK READMEs
(Go/TS/Python) pointing at the mdx default-assets list and the mdx
Adding Support for New Networks section. Soften the mdx Contributing a New
Default Asset blurb to drop manual mdx/README update instructions.
* docs: add extensions overview and signed offers & receipts guide
- Add extensions/overview.mdx documenting the extension system
- Add extensions/offer-receipt.mdx
- Add offer-receipt row to sdk-features.md
- Update docs.json navigation with new pages in alphabetical order
* Refined the link to the ecosystem page.
* fix: add duplicate settlement mitigation for SVM across all SDKs
Introduce an in-memory SettlementCache to prevent a race condition on
Solana where the same payment transaction could be settled multiple
times before on-chain confirmation. The cache is shared across V1 and
V2 facilitator schemes so that cross-version duplicates are caught.
- Add SettlementCache with 120s TTL in TypeScript, Python, and Go
- Integrate cache check into facilitator settle paths (V1 and V2)
- Add unit tests for duplicate detection in all three languages
- Share cache across V1/V2 in Go facilitator example
- Add duplicate settlement spec to scheme_exact_svm.md
- Document SettlementCache in SVM READMEs for all three SDKs
- Document the race condition in go/FACILITATOR.md Security section
- Add merchant-facing guidance in docs/core-concepts/client-server.md
and docs/core-concepts/facilitator.md for self-settling servers
- Fix JSDoc lint errors in TypeScript settlement-cache.ts
* refactor: optimize SettlementCache prune with early break on ordered entries
Leverage insertion-order guarantees of Map (TS) and dict (Python) to
break early once a non-expired entry is encountered, avoiding a full
scan of the cache on every isDuplicate call. Go is left unchanged since
map iteration order is not guaranteed.
Also adds prune-specific unit tests for all three SDKs covering:
- mixed expired/fresh entries
- all expired
- none expired
- insertion-order early-break correctness (Python)
* docs: add changelog entries for SVM duplicate settlement fix
Update documentation across core concepts, quickstarts, FAQ, and extensions
to reflect v2 protocol changes including PAYMENT-REQUIRED header, CAIP-2
network identifiers, SVM/Solana support, and ecosystem link fixes.