Address forensic review-quorum findings and conform SVM paywall to upstream pattern:
- Drop dead solana:TESTNET FAUCET_URLS entry (Circle faucet does not
dispense USDC on Solana Testnet; Option B renders "No faucet configured."
for any unmapped chain).
- Revert all Solana Testnet recognition added by prior refactor pass
(SOLANA_NETWORK_REFS.TESTNET constant, getNetworkDisplayName branch,
isTestnetNetwork OR-branch). The paywall now recognizes one non-mainnet
SVM network — Devnet — matching upstream/main. No SVM dev expects
paywall Testnet support; upstream doesn't provide it.
- Unify "Need {tokenName} on {chainName}?" copy in SolanaPaywall and
AvmPaywall payment-required headers (were hardcoded "USDC"; matches
EvmPaywall).
Closes#2159
Tightens the viem floor in every package.json that lists viem (41 refs
across 40 files), refreshes all three lockfiles so every direct viem
resolution reads 2.48.11, and regenerates the paywall bundled templates
so the EVM/SVM/AVM bundles match the new viem chain database.
## Why floor-tightening matters
PR #2013 bumped lockfiles to 2.47.14, but later PRs (#2061, #2197, ...)
added sub-packages with ^2.39.x / ^2.43.x floors. pnpm re-resolved on
subsequent installs and the solver picked the lowest acceptable version
across constraints. ^-ranges with low floors do NOT preserve a bump --
lockfile refreshes erode the floor.
This PR fixes that incomplete tightening from #2013 by raising every
floor to ^2.48.11. The same regression will recur if any future PR adds
a viem-using sub-package with a lower floor. Gate criterion: new
packages must use ^2.48.11 (or tighter) for viem.
## Acceptance verification
- pnpm install --frozen-lockfile clean across typescript/,
examples/typescript/, and e2e/.
- pnpm format:check, lint:check, build, test green for typescript/.
- pnpm format:check, lint:check green for examples/typescript/.
- All direct viem resolutions read 2.48.11 in all three workspaces.
- Paywall bundled templates regenerated via
pnpm --filter @x402/paywall run build:paywall.
* feat: add batch-settlement implementation to Go SDK
* feat: add batch-settlement examples for go sdk
* feat: updated typescript examples to match go examples
* feat: add e2e testing for batch-settlement in go
* Batch-settlement: go-ts parity (#2227)
* fix PendingRequest and refund cleanup
* fix lint
* remove duplicate payer info from storage
* fix PAYMENT-RESPONSE field ordering
* clean up comments
* consolidate ProcessSettlementWithExtensions into ProcessSettlement
---------
Co-authored-by: phdargen <p.dargent@cern.ch>
The committed @x402/paywall bundle on main was last generated against an
older viem than the lockfile currently pins. pnpm install --frozen-lockfile
resolves viem 2.47.12 (via #2013), but the bundled src/evm/gen/template.ts
(and its Python + Go siblings) were built against an earlier resolution
that pre-dated chain definitions for Mezo, MegaETH, Stable, Radius (each
with a testnet variant), and 33 others. EvmPaywall.tsx throws
"Unsupported chain ID" at init for any eip155:<id> whose chain isn't in
the bundled viem/chains.
This PR:
1. Regenerates all nine auto-generated template files (TypeScript,
Python, and Go for EVM/SVM/AVM) against the current lockfile. No
source changes on any runtime path.
2. Teaches build:paywall to emit output matching the repo's formatters
(prettier / ruff), so generated files stay clean under pnpm run
format + uvx ruff format.
3. Adds a PR-time drift check
(.github/workflows/check_paywall_template.yml) so a future lockfile
or @x402/evm change that invalidates the bundle fails loudly
instead of shipping silently.
Scope is limited to @x402/paywall because it is the only package in this
repo that bakes viem chain definitions into a built artifact.
Verified on a fork-internal test PR running on ubuntu-latest
(Node 24, pnpm 10.7.0): check_format, check_lint, check_go, check_python,
check_package_lock, and the new check_paywall_template drift check all
pass. Additional local evidence:
- Chain-presence in regenerated bundle: Mezo 31612/31611, MegaETH
4326/6343, Stable 988/2201, Radius 723487/72344, Base/Arbitrum/
Polygon all present (mainnet/testnet ordering).
- Cross-platform determinism: a clean-slate rebuild on macOS produces
byte-identical output to ubuntu-latest CI.
- Tarball install into a throwaway consumer: all expected chain IDs
present in the published dist/esm/evm/index.js.
- Browser smoke test (Chrome, served from a local HTTP server):
EvmPaywall mounts without Unsupported-chain throw for
eip155:31611 (Mezo Testnet) and eip155:723487 (Radius); DOM
renders the expected token/chain labels.
Fixes#1971.
* fix(paywall): use dynamic token decimals instead of hardcoding 6
The EVM paywall displays incorrect amounts for any token that does not
use 6 decimal places. An 18-decimal token priced at 0.001 raw units
renders as $1,000,000,000 because the code divides by 10^6 everywhere.
Root cause: the paywall was built assuming USDC (6 decimals) is the
only payment token. This assumption appears in three places:
1. Server-side HTML generation (index.ts) divides the raw amount by
a hardcoded 10^6 to produce the display value injected into the
template.
2. Client-side balance display (EvmPaywall.tsx) calls formatUnits
with a hardcoded 6 and reads the token address from a 3-chain
USDC lookup table that returns 0 for any other chain.
3. The balance utility (utils.ts) only knows USDC addresses on
Ethereum, Base, and Base Sepolia — every other chain silently
shows a zero balance.
Fix:
Server-side (index.ts): look up the token's decimal precision from a
known-decimals map aligned with DEFAULT_STABLECOINS. Only non-6-decimal
chains need entries; everything else falls back to 6. This keeps the
server-side path simple with no RPC calls.
Client-side (EvmPaywall.tsx): read the token contract address from
the payment requirement's `asset` field (which the server already
populates) and query the standard ERC-20 decimals() function on-chain.
This works for any compliant token without maintaining a lookup table.
utils.ts: replace the USDC-specific getUSDCBalance (internal helper,
not part of the public API) with generic getTokenBalance and
getTokenDecimals functions that accept a token address parameter.
The function signature changes from 2 args to 3, but no external
consumer can import it — it is only used by the bundled React
component inside the paywall HTML template.
**Breaking change note:** the internal helper getUSDCBalance in utils.ts
is removed and replaced by getTokenBalance (different signature: takes
an explicit token address instead of looking it up by chain ID). This
function is not exported from the package's public API — it is only
consumed by the bundled EvmPaywall React component inside the paywall
HTML template. No server operator code calls it directly. However,
anyone who has forked the paywall and imports from the file path
(bypassing package exports) would need to update their import and
call site.
Regenerated Go, Python, and TS paywall templates.
**AI disclosure:** This PR was prepared with the assistance of a coding agent and
reviewed by Ryan R. Fox (an actual human) before submission.
* style: ruff format paywall templates
* fix(paywall): use DEFAULT_STABLECOINS lookup + BigInt formatUnits
Removes the parallel KNOWN_DECIMALS map in @x402/paywall/src/evm/index.ts
that mirrored DEFAULT_STABLECOINS from @x402/evm. The paywall now resolves
token decimals through the same registry that scheme implementations and
@x402/core's inline scheme dispatch already read from.
evmPaywall.generateHtml changes:
* getDefaultTokenDecimals helper looks up requirement.network directly in
@x402/evm's DEFAULT_STABLECOINS, with a 6 (USDC default) fallback when
the network is unknown.
* Atomic-to-display conversion uses Number(formatUnits(BigInt(amount),
decimals)) instead of parseFloat(amount) / 10**decimals. parseFloat
silently rounds sub-cent precision on real 18-decimal amounts before
the divide; BigInt + formatUnits preserves precision through the
conversion. BigInt also rejects non-integer atomic strings, which
matches the spec's atomic-integer contract.
@x402/paywall package.json: @x402/evm moves from devDependencies to
dependencies because the new server-side import of DEFAULT_STABLECOINS is
on the runtime path emitted into dist/.
@x402/evm now publicly re-exports DEFAULT_STABLECOINS from
./shared/defaultAssets so consumers can read the canonical default-asset
registry directly. Both @x402/evm and @x402/paywall get a minor bump
for the additive public API.
Adds 6 unit tests:
* getDefaultTokenDecimals returns 18 for Mezo Testnet (registry path)
* getDefaultTokenDecimals returns 6 for Base mainnet, asserted alongside
DEFAULT_STABLECOINS so an empty registry would fail the test
* getDefaultTokenDecimals falls back to 6 for unknown networks
* evmPaywall.generateHtml renders 1e15-atomic Mezo mUSD as
'amount: 0.001,' end-to-end (regression test for the /1e6 bug)
* evmPaywall.generateHtml renders 1e6-atomic Base USDC as 'amount: 1,'
* evmPaywall.generateHtml throws on a non-integer atomic ('1.5'),
pinning the BigInt strictness so a future revert to parseFloat fails
Closes#1979.
* refactor(paywall): generate evm decimals at build time, drop @x402/evm runtime dep
Addresses @phdargen's review: rather than promoting @x402/evm to a
runtime dependency of @x402/paywall, keep it a devDependency and
emit a codegen'd `src/evm/gen/decimals.ts` that mirrors just the
per-network `decimals` field of `DEFAULT_STABLECOINS`.
Pattern-consistent with the existing `src/evm/gen/template.ts` codegen
(HTML bundle) — same build step (`src/evm/build.ts`), same "AUTO-GENERATED
DO NOT EDIT" banner, same commit-the-generated-file workflow. The CI
drift check queued in #2054 (`check_paywall_template.yml`) will pick up
`decimals.ts` under the existing `typescript/packages/http/paywall/**`
trigger glob once that PR merges; in the meantime an in-process drift
invariant test in `network-handlers.test.ts` asserts `NETWORK_DECIMALS`
matches `DEFAULT_STABLECOINS` key-for-key.
Runtime behaviour is unchanged. `getDefaultTokenDecimals` now reads the
generated `NETWORK_DECIMALS` map instead of reading `DEFAULT_STABLECOINS`
at runtime; the same Mezo-18, Base-6, unknown→6 cases still hold, and
the existing 6 regression tests in `network-handlers.test.ts` pass
without modification. A seventh test pins the drift invariant described
above.
package.json: `@x402/evm` moved from `dependencies` to `devDependencies`.
Runtime module graph for `@x402/paywall` no longer pulls `@x402/evm`;
the only surviving `@x402/evm` references in paywall src are:
* `browserAdapter.ts` — `import type { ClientEvmSigner }` (type-only,
erased at build time)
* `EvmPaywall.tsx` — `ExactEvmScheme` (bundled into `gen/template.ts`
by esbuild, not part of the server-side runtime path)
* `build.ts` and `network-handlers.test.ts` — build-time / test-time
consumers; devDep is available in both.
Both the root `typescript/pnpm-lock.yaml` and `examples/typescript/pnpm-lock.yaml`
are updated to reflect the dep move — both workspaces reference the
paywall package manifest via `workspace:~`.
The EVM paywall hardcodes "USDC" as the token label in all display
text. The payment requirements already carry the token name in
extra.name (populated by the server from the default asset registry),
but the paywall ignores it.
Read extra.name from the first payment requirement and use it for
all user-facing token text. Falls back to "USDC" when extra.name
is absent (backward compatible with EIP-3009 tokens).
5 display strings updated:
- Header: "please pay $X {tokenName}" (was "USDC")
- Testnet prompt: "Need {tokenName} on {chainName}?" (was "USDC")
- Balance: "$X {tokenName}" (was "USDC")
- Amount row: "$X {tokenName}" (was "USDC")
- Error: "Make sure you have {tokenName} on {chainName}" (was "USDC")
Regenerated Go, Python, and TS paywall templates.
* fix(go): add omitempty to QueryInput/BodyInput.Method to prevent spurious enum validation failure
When external JSON omits info.input.method (valid when method is not in the schema's
required list), Go zero-initializes the Method field to "" and re-marshaling produces
"method":"", which fails the enum constraint in ValidateDiscoveryExtension.
Adding omitempty ensures absent method fields remain absent after round-trip serialization.
Fixes#1830
Made-with: Cursor
* enforce method is required in TS and Python discovery extension schemas
Per spec, the method field must always be present in a discovery extension's
info.input. Add "method" to the required array in schemas built by the TS
and Python resource service builders, so ValidateDiscoveryExtension rejects
extensions missing method with a clear error.
Also reverts the Go omitempty workaround from the prior commit; the Go SDK
was already producing a validation error for absent method (via the enum
constraint), and the schema-level required enforcement is the correct fix.
Closes#1830
Made-with: Cursor
* style: format resourceService.ts type union per Prettier
Made-with: Cursor
* fix: auto-populate HTTP method from adapter in all SDKs
The SDK entry points (processHTTPRequest, requiresPayment,
processSettlement) now derive the HTTP method from the adapter
when it is not explicitly set on the request context. This ensures
direct x402HTTPResourceServer users do not need to manually assign
the method field — the SDK computes it at runtime, matching the
behavior middleware users already get.
Made-with: Cursor
* test: add declare → enrich → validate flow tests for bazaar extension
Verify the real middleware path: extensions are declared without method,
enrichDeclaration injects method from the HTTP context at request time,
and the enriched extension passes schema validation. Covers GET and
POST in all three SDKs (TypeScript, Go, Python).
Made-with: Cursor
* feat(evm): add upto payment scheme TypeScript SDK
Implement the upto payment scheme for EVM, enabling usage-based payments
where a client authorizes a maximum amount via Permit2 and the server
settles for the actual amount used (which may be less).
Covers all three roles:
- Client: creates Permit2 payloads with max authorized amount
- Server: builds payment requirements, forces permit2 transfer method
- Facilitator: verifies permitted >= required, settles actual usage,
supports zero-settlement path for no-charge responses
Key design decisions:
- Permit2 only (no EIP-3009, per spec)
- Shared Permit2 witness struct with exact scheme
- Re-exports shared utilities from exact (approval helpers, extensions, RPC)
- V2 protocol only
Resolves: CDPAI-714
* chore(evm): add JSDoc descriptions and fix lint errors in upto SDK
Add comprehensive JSDoc descriptions, @param, and @returns tags to all
upto scheme files to satisfy eslint jsdoc rules. Remove unused imports
in facilitator test file.
* refactor(evm): extract shared permit2 helpers to reduce duplication between exact and upto facilitators
* refactor(evm): consolidate client-side createPermit2Payload into shared helper
* refactor(evm): extract shared trySignEip2612Permit and trySignErc20Approval from scheme classes
* refactor(evm): split shared/permit2-helpers into permit2.ts and extensions.ts
* test(evm): add upto server, register, and types tests; expand client and facilitator coverage
Add 3 new test files (server.test.ts, register.test.ts, types.test.ts)
covering upto-specific server behaviors (permit2 forcing, facilitator
address injection, price parsing), registration helpers for all three
roles, and type guard validation. Expand existing client and facilitator
tests with additional edge cases.
Also includes in-progress source changes: shared permit2 helper
refactoring, upto facilitator hardening, spec clarifications, and
defaultAssets extraction.
* fix(evm): resolve lint errors for CI — add missing JSDoc descriptions and fix unused vars
* fix(evm): address PR review — align upto verify flow with exact, update spec, remove createEvmClient
* refactor(evm): move shared utils to shared/, remove upto register pattern
- Move validateErc20ApprovalForPayment to shared/erc20approval.ts
(was in exact/facilitator/, used by both exact and upto)
- Move RPC utilities to shared/rpc.ts, rename types to drop Exact prefix
(EvmSchemeConfig, EvmSchemeOptions, etc.) with deprecated aliases
- Remove registerUptoEvmScheme from client, facilitator, and server
(v1 legacy pattern not needed for v2-only upto scheme)
- Backward-compat re-exports preserved at original paths
* test(e2e): add upto payment scheme e2e test coverage
Add full e2e test suite for the upto payment scheme mirroring exact
permit2 coverage: direct settle, EIP-2612 gas sponsoring, and ERC-20
approval gas sponsoring endpoints.
- Add 3 upto endpoints to Express e2e server with UptoEvmScheme
- Register UptoEvmScheme in TypeScript facilitator
- Register UptoEvmClientScheme in fetch and axios e2e clients
- Add upto Permit2 approve/revoke cycle handling in test runner
- Add upto entry points to @x402/evm tsup.config.ts
- Update test.config.json files for all components
* fix(evm): harden upto type guard, add time window validation, improve settlement comments
- Add validAfter check to isUptoPermit2Payload for stricter exact/upto discrimination
- Add deadline > validAfter guard in client permit2 payload creation
- Default simulateInSettle to true for settlement re-verification
- Expand settlement re-verification comment for reviewer clarity
- Add no-register.ts comments explaining V1 compat is not needed for upto
- Clarify e2e test config description for upto endpoint
- Add tests for validAfter type guard and buildUptoPermit2SettleArgs
* feat: added SettlementOverride
* fix: examples lock
* feat: Added upto to hono/next e2e tests
* feat: update upto tests
* feat: update tests to support fallback facilitator for non-SDK parity testing
* fix: format/lint
* fix: add linting to upto example
---------
Co-authored-by: Fabrice Cheng <fabrice.cheng@coinbase.com>
* feat(go): add net/http standard library adapter for payment middleware
* feat(go): add PaymentMiddlewareFromHTTPServer, example server, and e2e tests
* feat(go/http): add onProtectedRequest hook for pre-payment request interception
* feat(go/http/gin): add PaymentMiddlewareFromHTTPServer for pre-configured server support
* feat(go): Add payment-identifier constants to shared types
Add extension identifier and validation constants for the
payment-identifier extension to the shared types package.
* feat(go): Add payment-identifier core types, utils, and schema
Add foundational components for the payment-identifier extension:
- doc.go: Package documentation
- types.go: PaymentIdentifierInfo, PaymentIdentifierExtension, ValidationResult
- utils.go: GeneratePaymentID, IsValidPaymentID
- schema.go: JSON Schema (Draft 2020-12) for validation
* feat(go): Add payment-identifier server-side declaration
Add server-side components for resource servers to declare
support for the payment-identifier extension:
- server.go: PaymentIdentifierResourceServerExtension
- resource_service.go: DeclarePaymentIdentifierExtension
* feat(go): Add payment-identifier client-side append function
Add client-side utility for appending payment identifiers to
extension payloads when the server has declared support.
* feat(go): Add payment-identifier facilitator extraction and validation
Add facilitator-side functions for extracting and validating
payment identifiers from payment payloads:
- IsPaymentIdentifierExtension, ValidatePaymentIdentifier
- ExtractPaymentIdentifier, ExtractPaymentIdentifierFromBytes
- ExtractAndValidatePaymentIdentifier, HasPaymentIdentifier
- IsPaymentIdentifierRequired, ValidatePaymentIdentifierRequirement
- ExtractPaymentIdentifierFromPaymentRequired
* test(go): Add payment-identifier extension tests
Add comprehensive test coverage for the payment-identifier extension:
- Constants validation matching TypeScript implementation
- ID generation and validation
- JSON Schema structure
- Server-side declaration
- Client-side append functionality
- Facilitator extraction and validation
- Full integration workflow tests
- JSON round-trip serialization tests
* docs(go): Add payment-identifier extension examples
Add usage examples for the payment-identifier extension:
- examples/go/servers/payment-identifier/: Standalone server example
- examples/go/clients/payment-identifier/: Standalone client example
- examples/go/facilitator/advanced/payment-identifier.go: Facilitator example
Structure matches TypeScript examples with dedicated directories
for client and server examples.
* Format
* Changelog
* test(go): Add payment-identifier tests for uncovered logic paths
Cover additional branches: invalid extension structure in append,
empty ID extraction, missing key with non-nil extensions map, and
V2 PaymentRequired with nil extensions.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix(go): Fix client example compilation error and add go.sum files
* refactor(go): Extract parseExtension helper and use DetectVersion
* fix(go): Remove debug logging and skip_settlement from gin middleware
* feat(go): Add PayloadFingerprint for 409 Conflict detection
SHA-256 hash of the serialized payload enables servers to distinguish
a legitimate retry from a misuse of the same payment ID with different
content.
* feat(ts): Add payloadFingerprint for 409 Conflict detection
Parity with Go SDK. Uses sorted-key JSON.stringify for deterministic
serialization before SHA-256 hashing.
* feat(go): Return 409 Conflict for duplicate ID with different payload
Example server now compares payload fingerprints on duplicate payment
IDs: matching fingerprints return the cached 200, mismatches return 409.
* feat(ts): Return 409 Conflict in example server for duplicate ID with different payload
* refactor(go): Move PayloadFingerprint out of core library into example
PayloadFingerprint is an application-level convenience for 409 Conflict
detection, not a protocol primitive. The spec defines the expected
behavior but not the implementation strategy.
* refactor(ts): Move payloadFingerprint out of core library into example
Mirrors the Go-side change — payloadFingerprint is an application-level
convenience for 409 Conflict detection, not a protocol primitive.
* refactor(go): Extract getPaymentIdentifierExtension helper to reduce duplication
Consolidate the repeated nil-check + map-lookup pattern for extracting
the payment-identifier extension from a PaymentPayload into a single
shared helper, used by ExtractPaymentIdentifier,
ExtractAndValidatePaymentIdentifier, and HasPaymentIdentifier. Also
add missing payment-identifier pattern to the facilitator example
dispatcher comments.
* fix: Exclude payment proof from fingerprint hash
The payload field contains per-attempt cryptographic signatures that
are unique on every retry. Hashing them caused legitimate retries
(same ID, same intent) to trigger 409 Conflict. Now only the intent
fields (x402Version, accepted, resource, extensions) are hashed.
* fix: Revert intent-only fingerprint, cache payment header for true retries
The fingerprint should hash the full PaymentPayload including the
cryptographic signature. A proper retry resends the exact same signed
payload, so hashing everything is correct — and a genuinely different
request (different signer/amount) correctly triggers 409.
The client example now caches the PAYMENT-SIGNATURE header from the
first successful attempt and replays it on subsequent requests,
instead of creating a new payment each time.
fix: Move idempotency check before payment middleware, cache payment header
The settlement hooks (OnBeforeSettle abort) don't properly short-circuit
the middleware — the abort error isn't handled by OnSettleFailure, so the
middleware returns 402 for duplicate requests.
Fix: move the idempotency check to a gin middleware that runs BEFORE the
payment middleware (matching the TS onProtectedRequest pattern). Duplicate
payment IDs are detected and served from cache without entering the
payment pipeline at all.
Also fixes the client to cache and replay the PAYMENT-SIGNATURE header
on retry instead of creating a new payment each time.
Fingerprint is now a hash of the raw PAYMENT-SIGNATURE header string,
which is simpler and correct — a true retry sends identical bytes.
* Lint
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Replace panic() calls with idiomatic Go error returns in the HTTP client
and server encoding functions. This prevents application crashes from
malformed input and follows Go best practices for error handling.
Changes:
- EncodePaymentSignatureHeader now returns (map[string]string, error)
- encodePaymentRequiredHeader now returns (string, error)
- encodePaymentResponseHeader now returns (string, error)
- createHTTPResponseV2 now returns (*HTTPResponseInstructions, error)
- createSettlementHeaders now returns (map[string]string, error)
- Updated all call sites with proper error handling
- Updated unit tests and integration tests accordingly
* fix: pass headers from reverse proxy
* fix: use explicit resource config for proxy support
* refactor: remove resourceUrl assignment from requirements extra map.
* refactor: simplify Gin adapter's GetURL by removing X-Forwarded header checks and using Request.URL.Path.
* feat: Inject payment page configuration as a JavaScript object into a template, replacing direct HTML rendering with data attributes.
* test: update paywall HTML assertions for new template structure and embedded config.
* Update go/http/server.go
Co-authored-by: phdargen <pdargent@icloud.com>
* refactor: remove cdpClientKey and fix other comments
---------
Co-authored-by: phdargen <pdargent@icloud.com>
* chore: move packages, examples and e2e clients/servers/facilitators to legacy subfolders
* feat: added @x402/core to /typescript/packages
* feat: added @x402/evm to /typescript/packages/mechanism
* feat: added @x402/svm to /typescript/packages/mechanism
* feat: added @x402/extensions to /typescript/packages
* feat: added @x402/fetch to /typescript/packages/http
* feat: added @x402/axios to /typescript/packages/http
* feat: added @x402/paywall to /typescript/packages/http
* feat: added @x402/express to /typescript/packages/http
* feat: added @x402/hono to /typescript/packages/http
* feat: added @x402/next to /typescript/packages/http
* chore: update /typescript pnpm packaging
* feat: added core files to /go
* feat: added evm mechanism to /go
* feat: added svm mechanism to /go
* feat: added extensions to /go
* feat: added gin to /go/http
* feat: added tests to /go
* feat: rewrote e2e test suite system
* feat: added axios client to e2e suite
* feat: added fetch client to e2e suite
* feat: added go http client to e2e suite
* feat: added express server to e2e suite
* feat: added hono server to e2e suite
* feat: added next server to e2e suite
* feat: added gin server to e2e suite
* feat: added typescript facilitator to e2e suite
* feat: added go facilitator to e2e suite
* feat: added fetch example to examples/typescript/clients
* feat: added axios example to examples/typescript/clients
* feat: added advanced example to examples/typescript/clients
* feat: added custom example to examples/typescript/clients
* feat: added express example to examples/typescript/servers
* feat: added hono example to examples/typescript/servers
* feat: added advanced example to examples/typescript/servers
* feat: added custom example to examples/typescript/servers
* feat: added facilitator example to examples/typescript
* chore: update /examples/typescript pnpm packaging
* feat: added http client to examples/go/clients
* feat: added advanced client to examples/go/clients
* feat: added custom client to examples/go/clients
* feat: added gin server to examples/go/servers
* feat: added advanced server to examples/go/servers
* feat: added custom server to examples/go/servers
* feat: added facilitator to examples/go
* chore: updated github workflows
* fix: typescript examples fotmat/lint
* v2: next example (#706)
* fix legacy example builds
* add next example
* fix format
* upgrade to next 16
* fix legacy build
* fix e2e tests
* V2: next api wrapper (#707)
* add next route wrapper
* add protected api to example page
* add unit tests
* fix missing settle failure check
* added e2e tests for withX402
* add SettleResponse to ProcessSettleResultResponse
* add requirements to payment-header
* feat: add v2 support to x402.org facilitator
* feat: dynamically load bazaar extension in Next only when used
* fix: x402Facilitator in typescript calling onAfterVerify instead on onVerifyFailure on failure
* feat: add ERC1271 and ERC6492 support to Typescript facilitator
* feat: update typescript facilitator example & e2e test for ERC1271/ERC6492 support
* feat: add ERC1271 and ERC6492 support to Go facilitators
* feat: update go facilitator example & e2e test for ERC1271/ERC6492 support
* v2: express fixes + unit tests (#712)
* add express fixes from v1
* add units test for express/hono
* added fetch/axios unit tests
* v2: Clean up paywall (#710)
* Remove cdpClientKey and sessionTokenEndpoint from PaywallConfig
Remove Onramp functionality from EvmPaywall
Remove Coinbase fields from paywall template generation
* Migrate site to @x402/next with v2 protocol support
* Clean up tests
* remove CDP onramp from core paywall
* Update templates and build process
* Format
* Lockfile
* mock templates for CI
* Format
* Generate new templates
* Format
* v2: facilitator sync fix (#716)
* update next/react versions
* update site to next 16, tailwind 4 and fix env vars
* fix initializeOnStart pattern
* security: bump quic-go dependency for security fix GHSA-47m2-4cr7-mhcw
* v2:fix ts advanced/custom examples (#717)
* fix ts examples
* add clients/advanced/preferred-network example
* feat: improved e2e cli for external facilitator testing
* feat: updated evm & svm signer interfaces in go
* feat: updated evm & svm signer interfaces in typescript
* feat: reverted SupportedKind's kinds structure in go
* feat: reverted SupportedKind's kinds structure in typescript
* feat: refactor facilitator SVM signer interface in typescript
* go example fixes (#719)
* feat: cleanup go bazaar extension
* V2: docs update (#729)
* ts example docs
* improve ts package docs
* feat: dynamic bazaar import for all server middleware
* feat: allow dynamic response building for 402 response in typescript
* feat: allow dynamic response building for 402 response in go
* feat: added withBazaar HTTPFacilitatorClient wrapper
* feat: added linting to go
* fix: lint go
* improve go example docs (#733)
* feat: Solana PR review feedback in typescript
* feat: Solana PR review feedback in go
* fix: locks & paywall gen after rebase off main
* fix: format
* docs: improve @x402/extensions README with comprehensive documentation (#731)
* First draft of contributor docs (#738)
Correct ts contributing
Clean up contribution guidelines
* feat: updated specs for v2
* fix: merge with main, fixed lock
* v2: go settlement failure and initOnStart fixes (#720)
* go settlement failure and initOnStart fixes
* update go unit tests
* update readmes
* feat: review & improve examples & READMEs
* v2: add multiple payment options for go (#743)
* add multiple payment options for go
* fix SyncFacilitatorOnStart
* v2: add hooks for advanced go example (#745)
* add hooks for advanced go example
* fix legacy ts deps
* feat: added server initialization validation
* feat: added @x402 package workflows
* v2: add miniapp and mcp examples (#746)
* add miniapp example
* fix format
* add mcp example
* fix format
* v2: add manifest to miniapp example (#751)
* add manifest to miniapp
* fix format
* feat: x402 website redesign (#750)
* port new website to public repo
* chore: update pnpm-lock.yaml with motion dependency
* feat: add x402 V2 launch blog post and update hero code snippet
- Add /writing/x402-v2-launch blog post page
- Add blog images (blog_intro.png, blog_x402_layers.png, homepage_build5.png)
- Enable Writing nav link in NavBar and Footer
- Update hero code snippet to show V2 SDK usage
- Fix CodeSnippet to support multi-line code
* feat: edit nav for mobile
* Revert "feat: edit nav for mobile"
This reverts commit 475999a2a84f1fab875cd0fe2bb74d44dba7e1bd.
* feat: add ecosystem page and minor home page tweaks
* feat: fix typography in ecosystem
* homepage qa fixes
* feat: add ecosystem icons and fix halftone
* cleanup assets
* fix: minor bug on faq
* feat: add hamburger menu to mobile
* Update README (#755)
* Update readme
* Install instructions and typos
* feat: update site sample code & reduce supported networks
* fix: v1 header in README updated to v2
---------
Co-authored-by: phdargen <p.dargent@cern.ch>
Co-authored-by: A. McDermott <amanda.p.mcdermott@gmail.com>
Co-authored-by: Vedant Anand <136731196+VedantAnand17@users.noreply.github.com>
Co-authored-by: Faris Habib <frs@hbb.dev>
Co-authored-by: erikreppel-cb <erik.reppel@coinbase.com>