@eco-foundation/api-schemas 0.4.1 → 0.7.0

package/README.md

@@ -4,7 +4,7 @@ Zod-first schemas, error catalog, golden fixtures, and generated OpenAPI 3.1 for
 API. The Zod schemas are the source of truth; everything else (OpenAPI, fixtures, plain types)
 is generated from or gated against them.
 
-Today the package covers **13 endpoints across 12 paths**, **37 error codes** (51 namespaced
+Today the package covers **13 endpoints across 12 paths**, **39 error codes** (51 namespaced
 legacy references), and **19 golden fixtures**.
 
 ## Install
@@ -14,13 +14,13 @@ While the package is 0.x, pin the patch range or the exact version:
 ```json
 {
   "dependencies": {
-    "@eco-foundation/api-schemas": "~0.4.1"
+    "@eco-foundation/api-schemas": "~0.7.0"
   }
 }
 ```
 
 **Never write `^0`.** npm resolves `^0.x` as `>=0.0.0 <1.0.0`, so it silently accepts every
-future breaking `0.y` — it is not a pin at all. Use `~0.4.1` or the exact `0.4.1`.
+future breaking `0.y` — it is not a pin at all. Use `~0.7.0` or the exact `0.7.0`.
 
 A matching version string is not evidence of a matching artifact: also compare
 `V1_SCHEMA_DIGEST` (see [Invariants](#invariants-enforced-in-ci)). Two builds both called
@@ -30,6 +30,365 @@ A matching version string is not evidence of a matching artifact: also compare
 zod-bearing entry point. Which case you are in is decided entirely by your imports; see
 [Consumers](#consumers).
 
+## Migrating 0.6.0 -> 0.7.0
+
+**BREAKING under 0.x semver** (breaking bumps the minor while the major is 0). Nothing on the
+wire that `0.6.0` accepted is rejected, and nothing `0.6.0` published is removed: two operations
+RETURN, one response field and one error code are ADDED. Three things still break, and one of
+them is a live-behaviour change rather than a compile error — read all three before bumping.
+
+**`V1_SCHEMA_DIGEST` MOVES.** Both digest inputs changed (`errors/catalog.lock.json` gained one
+code; `openapi/v1.json` gained two operations, two request schemas and one response field), so the
+value is now `3e13c5eeb8b054f3a48a22c7694de16b0fc11e1dbf6bc3c27e8c575100225b2a` — was
+`a6724fa4dd585e77aebe680655ac10fe5a2f4b70537930a0b4dee2612afb7c8e` on `0.6.0`. Every consumer
+running `assertNoSkew` must move to the new value **in the same rollout**; a mixed fleet fails
+the check by design.
+
+**THE THREE BREAKING ITEMS FIRST.**
+
+**1. `LaneStandard` widens back to all four standards — a compile break for anyone keying on
+it.** `STANDARDS_BY_TARGET.quote` is `['erc-3009', 'permit2', 'permit3']` (`depositAddress` is
+unchanged), and `LaneStandard` is derived from the matrix, so it is now
+`'erc-3009' | 'permit2' | 'permit3' | 'erc-2612'` — the exact mirror of `0.6.0`'s narrowing.
+`V1_SUBMIT_SCHEMAS: Record<LaneStandard, …>` regains its `permit2`/`permit3` entries, and
+`V1_SUBMIT_SCHEMAS_BY_SERVICE.intents` has three lanes. **Your own `Record<LaneStandard, X>`,
+and every exhaustive `switch` over a `LaneStandard`, stops compiling until it gains two arms.**
+That is the intended signal: the alternative is a dispatcher that meets `undefined` at runtime.
+A consumer that only indexes `V1_SUBMIT_SCHEMAS_BY_SERVICE['deposit-addresses']` is untouched.
+
+**2. A bare dependency bump WIDENS what a server ADVERTISES.** A router that derives its
+`/v1/tokens` `supports.quote` from `STANDARDS_BY_TARGET` advertises `permit2` and `permit3` the
+moment this version is installed — before it can necessarily execute them. That is exactly the
+false promise `0.6.0` closed. Ship the bump in the same release as the lane implementation
+(quoted-salt dispatch, `execution.vault` publication, and the vault binding described under the
+additive items), or gate discovery separately. This is the one item here that changes live
+behaviour with no code change on your side.
+
+**3. Consumer-side, but read it: the lock gained a 400.** `V1ProblemSchema` cross-checks a KNOWN
+code's `status`/`type` against the catalog. `vault-mismatch` (below) is now known, so a body
+carrying that spelling with a contradicting status or type stops parsing where `0.6.0` tolerated
+it as "a newer server". An exhaustive `switch` over `V1ErrorCode` will not compile until it
+handles it.
+
+**THE ADDITIVE ITEMS.**
+
+**Returned — `POST /v1/intents/submit/permit2` and `/permit3`.** This supersedes `0.6.0`'s
+breaking item 4. The lanes can complete now because the two things that item named as missing
+exist: the router dispatches the QUOTED `route.salt` unchanged (so the intent it funds is the
+intent it quoted), and the quote response publishes the intent vault that salt produces
+(`execution.vault`, below), so a signer can name the vault-bound counterparty before signing.
+Both operations, both `V1_ENDPOINTS` entries (`intents.submit.permit2`, `intents.submit.permit3`),
+both golden fixtures, and the five schema exports `Permit2PermitSingleSchema`,
+`Permit2SubmitSchema`, `Permit3AllowanceSchema`, `Permit3PayloadSchema`, `Permit3SubmitSchema` are
+back. Path order in the document is `erc-3009`, `permit2`, `permit3` — the matrix order — and
+the tokens fixture advertises the same three under `supports.quote`.
+
+**The bodies are NOT the `0.5.0` bodies.** A consumer skipping `0.6.0` (`0.5.0 -> 0.7.0`) sees
+SIX newly-required fields, and a `0.5.0` body is a 400 at these paths. This is the material the
+solver's DTOs require and verify, which the `0.5.0` shapes omitted:
+
+```diff
+ // POST /v1/intents/submit/permit2
+ {
++  "chainId": 8453,
+   "target": { "quoteId": "quote:…" },
+   "permit2": {
+     "details": { "token": "0x…", "amount": "1043221", "expiration": 1767225600, "nonce": 0 },
+-    "spender": "<anything>",
++    "spender": "<execution.vault of the quote>",
+-    "sigDeadline": 1767225600
++    "sigDeadline": "1767225600"
+   },
+   "signature": "0x…"
+ }
+```
+
+```diff
+ // POST /v1/intents/submit/permit3
+ {
+   "target": { "quoteId": "quote:…" },
+   "permit3": {
+     "owner": "0x…",
++    "permitContract": "0x…",
+     "salt": "0x…",
+     "deadline": 1767225600,
++    "timestamp": 1767222000,
++    "merkleRoot": "0x…",
+     "permits": [
+-      { "chainId": 8453, "token": "0x…", "amount": "1043221" }
++      { "chainId": 8453, "token": "0x…", "amount": "1043221",
++        "account": "<execution.vault of the quote>", "modeOrExpiration": 0 }
+     ]
+   },
+   "signature": "0x…"
+ }
+```
+
+- **permit2 `chainId` (top-level, required)** is the EIP-712 domain chainId the signature was
+  produced under and the chain the permit executes on; the solver verifies the two agree. It
+  follows the C4 convention `erc-3009` and `erc-2612` already use.
+- **permit3 has NO top-level `chainId`**, deliberately: its EIP-712 domain is not the source
+  chain, and each leg names its own chain. A consumer that needs one chain id for the body takes
+  `permits[0].chainId`. It also carries no `leaves` and no `tokenKey` — the solver recomputes the
+  merkle tree from the legs, and `tokenKey` is `pad(token, 32)` (ERC-20 only) by definition.
+- **permit3 `permitContract`, `timestamp`, `merkleRoot`** are the signer's values, never
+  synthesized: the solver recomputes the root from the legs and rejects a mismatch.
+- **permit3 leg `account` and `modeOrExpiration`**: `account` is where the leg pushes funds
+  (mode `0`, immediate transfer) or grants the allowance (any other value, read as the allowance
+  expiration in Unix seconds). On a quote target it is always the vault.
+- **`nonce`, `expiration`, `timestamp` and `modeOrExpiration` are `Uint48`**, a new primitive
+  (with `UINT48_MAX`, `2^48 - 1`): the fields are uint48 on-chain and the ABI encoder truncates
+  rather than rejects, so the edge does. Expressed as bounds so the ceiling reaches the OpenAPI
+  document.
+- **permit2 `sigDeadline` is a decimal STRING (`UintString`), and `details.expiration` a
+  `Uint48`** — both carry their on-chain width instead of `UnixSeconds`. The Permit2 SDK's
+  `MaxAllowanceExpiration` (`2^48-1`) and `MaxSigDeadline` (`2^256-1`) are the standard "no
+  expiry" idiom many wallets sign, and a `<=2100` bound rejected a valid signature that would
+  have funded. Same narrow exception erc-3009's `validAfter`/`validBefore` carry; a NUMBER
+  `sigDeadline` is a 400 at `permit2.sigDeadline`. Every other deadline in the module
+  (`permit3.deadline`, erc-2612's) is still `UnixSeconds` and still rejects a milliseconds value.
+- **`Permit3PayloadSchema` stays a plain stripping `z.object`.** A `permit3.signature` sent in
+  the wrong place is dropped, so a reader has exactly one place to find the signature.
+
+**What the schema does NOT check, and the router does.** The body carries no vault, so the vault
+binding cannot be a refinement here (`refineDepositAddressBinding` is a no-op on quote targets by
+construction). Before the signature pin the router asserts, per lane: the signed counterparty
+(`permit2.spender`, every `permits[].account`) equals the quote's `execution.vault` — compared
+CASE-INSENSITIVELY (`isSameEvmAddress`, exported here), since neither side is checksum-normalized
+and a naive `===` turns a checksummed vault against a lowercase signature into a spurious 400 —
+else `vault-mismatch` (400); every permit3 leg `chainId` and the permit2 `chainId` equal the quote's
+source chain; the token equals the quote's source token and the amount is at least the reward
+amount for it; `permit2.details.expiration`, `permit2.sigDeadline`, `permit3.deadline` and a
+non-zero `modeOrExpiration` are all more than 60 seconds in the future (a stale authorisation is a
+400, not a reverting funding batch). A green parse is not a green submit.
+
+**Added — `execution.vault` on every quote object (optional, nullable, `AnyAddress`).** The
+intent vault for THIS quote: the CREATE2 address the source-chain Portal funds the intent
+through, derived from the quoted intent (route.salt included), so it changes whenever the salt
+does. It is the value to sign as erc-3009 `authorization.to`, permit2 `spender` and every permit3
+leg `account`. **Absent means the producer predates the field; `null` means the producer could
+not derive it** — today that is any non-EVM source (an SVM vault is a PDA and is not published).
+`AnyAddress` rather than `EvmAddress` because the same envelope carries SVM funding transactions
+and a future SVM producer must be able to publish the PDA here without a shape break; as always,
+never infer a VM from the branch that matched. Each ranked `quotes[]` entry carries its own. The
+zod-free `V1Execution` alias gains `vault?: string | null`, and the parity spec pins the optional
+member explicitly (an optional key is the one drift the mutual-assignability gate cannot see
+through a `looseObject`'s index signature).
+
+**Added — `vault-mismatch` (400): the signed counterparty is not the quote's intent vault.** The
+quote-target twin of `deposit-address-mismatch`, which is the wrong NAME on a quote target (there
+is no deposit address) — and `invalid-parameter` says nothing a caller can act on. `audience:
+'write'` — like the twin it needs a signed counterparty, so only a submit can emit it — and
+`legacyCodes: []` (no legacy service ever compared against a vault). A router's
+`detail` names the field (`permit2.spender`, `permit3.permits[1].account`, `authorization.to`),
+never the signed address. Branch on `code`: it shares 400 with `invalid-request`.
+
+## Migrating 0.5.0 -> 0.6.0
+
+**BREAKING under 0.x semver** (breaking bumps the minor while the major is 0). Five items REJECT
+a request `0.5.0` accepted or remove something `0.5.0` published; four are additive. Every
+breaking item is listed here — if you send anything named below, read its entry before bumping.
+
+**`V1_SCHEMA_DIGEST` MOVES.** Both digest inputs changed (`errors/catalog.lock.json` gained one
+code; `openapi/v1.json` lost two operations, gained two parameters and several descriptions), so
+the value is now `a6724fa4dd585e77aebe680655ac10fe5a2f4b70537930a0b4dee2612afb7c8e` — was
+`1d8e88e957795b23e1317dc1e3783fd64bf79b756e3f28bd40e02b047542d790` on `0.4.0`, `0.4.1` and
+`0.5.0`. Every consumer running `assertNoSkew` must move to the new value **in the same
+rollout**. Unlike `0.5.0`, this time the skew check DOES see the difference, so a mixed fleet
+fails it by design rather than silently validating two ways.
+
+**THE FIVE BREAKING ITEMS FIRST.**
+
+**1. `slippage` now rejects `0` and anything below `0.0001`, and the rejection is named.**
+
+```ts
+// 0.5.0: parses (and then fails downstream). 0.6.0: 400, code slippage-out-of-bounds, path ['slippage'].
+{ ..., slippage: 0 }
+{ ..., slippage: 0.00005 }
+```
+
+The range is `0.0001`-`1` (`SLIPPAGE_MIN`/`SLIPPAGE_MAX`, both exported), a DECIMAL FRACTION of
+the destination amount: `0.005` is 0.5%. No solver can express a tolerance below one basis
+point, so a `0` could only ever be rejected downstream, silently clamped, or silently replaced
+by a default; refusing it at the edge with a named code is the honest one. Zero tolerance is
+meaningless on a swap route and ignored on a non-swap route, so nothing is lost.
+
+**The code changes for EVERY out-of-range value, not only the new floor.** `0.5.0` enforced the
+bound with a built-in `.min()/.max()`, which zod reports as `too_small`/`too_big` — and
+`v1ErrorCodeFromIssues` maps only a `custom` issue carrying `v1IssueParams`, so the catalog's
+`slippage-out-of-bounds` was promised and unreachable: `50` rendered as the generic
+`invalid-request` with `legacyCode: eco-quotes:1003`. It now renders as
+`slippage-out-of-bounds` (status 400 unchanged, `detail` text unchanged, no `legacyCode`
+because that code has none). An integrator branching on `code === 'invalid-request'` for a
+bad slippage, or reading `legacyCode` there, sees the change. The catalog TITLE names the
+floor now; code, status and `legacyCodes` are untouched.
+
+The published document also carries the units for the first time: both `slippage` fields have a
+`description`, and the request field keeps `minimum`/`maximum` (via `.meta()`, since the bound
+itself lives in a refinement that `z.toJSONSchema` drops). The response `slippage` is documented
+as the tolerance ACTUALLY bound into `destination.minAmountOut` — when a request omits
+`slippage`, that is the default the solver applied, not the omission.
+
+**2. A zero `amount` is rejected on the quote request.**
+
+```ts
+// 0.5.0: parses, reaches a solver, comes back as a 502. 0.6.0: 400, path ['source','amount'].
+{ ..., source: { chainId: 8453, token: '0x…', amount: '0' } }
+```
+
+`source.amount` and `destination.amount` are `PositiveUintString` (new primitive: `UintString`
+with `'0'` excluded, message `must be greater than 0`). Every other `UintString` field is
+unchanged — a zero `value` on a destination call or a zero fee is still legal. The bound reaches
+the OpenAPI document as a `description` only; a string has no `minimum`.
+
+**3. `options.maxCallDataSize` is gone.**
+
+```ts
+// 0.5.0: parses. 0.6.0: 400, unrecognized_keys at path ['options'].
+{ ..., options: { maxCallDataSize: 1000 } }
+```
+
+It was published with no description and read by no service, so a caller sending it was handed
+a 200 for a bound nobody enforced. The strict `options` object now names the key in a 400, the
+same disposition `allowHighSlippage` has had since `0.3.0`. The zod-free `V1QuoteRequest` alias
+drops the member too. A caller that needs a calldata cap needs one that is defined and enforced,
+which is a different change.
+
+**4. `POST /v1/intents/submit/permit2` and `/permit3` are WITHDRAWN.** (Superseded by `0.7.0`,
+which returns both lanes with the fields named below — see that section.)
+
+Neither lane can complete, and this is why. The signed Permit2 `spender` and every Permit3 leg
+`account` must be the intent VAULT (`Portal.fundFor` pulls the funds through
+`IPermit.transferFrom(funder, vault)`), and the vault is derived from the route salt the router
+dispatches — a value the signer cannot know before signing until quoted-salt dispatch and vault
+binding exist. On top of that the published bodies omitted material the solver requires (permit2
+`chainId`; permit3 `permitContract`, `timestamp`, `merkleRoot`, per-leg `account` /
+`modeOrExpiration`), so the first refusal was a 401 on every request. Advertising a lane whose
+every body ends in a 4xx is a false promise. The lanes return as a follow-on once quoted-salt
+dispatch and vault binding land; `erc-3009` is the quote-target intents standard until then.
+
+What moved, concretely:
+
+- `STANDARDS_BY_TARGET.quote` is `['erc-3009']`. `depositAddress` is unchanged.
+- The two registry entries, the two operations in `openapi/v1.json`, and the two golden fixtures
+  are gone (11 endpoints over 10 paths; 17 fixtures). A router that dispatches from
+  `V1_SUBMIT_SCHEMAS_BY_SERVICE.intents` answers `invalid-parameter` on those routes by
+  construction.
+- **Five exports are deleted:** `Permit3AllowanceSchema`, `Permit3PayloadSchema`,
+  `Permit3SubmitSchema`, `Permit2PermitSingleSchema`, `Permit2SubmitSchema`. No endpoint accepts
+  those bodies, so there is nothing for them to validate.
+- **`V1_SUBMIT_SCHEMAS` is keyed by the new `LaneStandard` type** (`'erc-3009' | 'erc-2612'` —
+  the standards that have a lane), not by `SubmitStandard`. `V1_SUBMIT_SCHEMAS[standard]` with
+  a `SubmitStandard`-typed index no longer compiles; narrow to `LaneStandard` first. That is the
+  intended signal — the alternative was an `undefined` a dispatcher trips over at runtime.
+- **`SUBMIT_STANDARDS` and `SubmitStandard` KEEP all four spellings.** That enum is also the
+  discovery vocabulary a token advertises under `supports`, and narrowing it would make a
+  consumer hard-fail on a token list from a server still spelling `permit3`. The vocabulary is
+  what a token MAY advertise; the matrix is what has a lane. The tokens fixture advertises
+  `quote: ['erc-3009']`.
+
+**5. Consumer-side only, but read it: the lock gained a 502.** `V1ProblemSchema` cross-checks a
+KNOWN code's `status`/`type` against the catalog. `solver-error` (below) is now known, so a body
+carrying that spelling with a contradicting status or type stops parsing where `0.5.0` tolerated
+it as "a newer server". An exhaustive `switch` over `V1ErrorCode` will not compile until it
+handles it.
+
+**THE FOUR ADDITIVE ITEMS.**
+
+**Added — `solver-error` (502): an upstream solver rejected or failed the quote request.**
+`solver-timeout` was the only 502, so a router had to label a solver answering 400 in six
+milliseconds with a title that says "timed out". `solver-error` is the code for every upstream
+failure that is NOT a deadline expiry — a solver 4xx/5xx, a network error, an unparseable body.
+It is 502 rather than 4xx/422 on purpose: the gateway built the RFQ, so a solver rejection is a
+gateway/contract fault, never the caller's, and a 422 mapping would hide a contract bug as "no
+route". `legacyCodes` is EMPTY by construction: `eco-quotes:1025` (Failed) is the ref that would
+belong here, but it was published on `solver-timeout` and the lock is append-only, so it stays
+there. Branch on `code`, not on `status`, to tell the two 502s apart.
+
+**Added — `?chainId=` on `GET /v1/chains` and `GET /v1/tokens`.** OPTIONAL on both (the
+unfiltered document is unchanged and stays legal), a single value only. A malformed value —
+`abc`, `0`, `-1`, `1.5`, or a repeated `?chainId=1&chainId=8453` — is a 400 at the field; a
+syntactically valid chain id that matches nothing is a 200 with `chains: []` /
+`tokens: [], nextCursor: null`, never a 404. New exports: `CHAINS_LIST_QUERY_SHAPE` /
+`ChainsListQuerySchema`, `TOKENS_LIST_QUERY_SHAPE` / `TokensListQuerySchema`, and `ChainIdParam`
+(the coercing query-string twin of the body `ChainId`, which all three `chainId` query params —
+these two and the deposit-address lookup's — now wrap, so the accepted set cannot differ between
+endpoints publishing the same parameter name). Query-side only: never coerce a chain id in a
+JSON body.
+
+**Added — `renderIssuesAsProblemParts(issues, opts?) -> { code, detail?, errors? }`, THE one
+sanctioned path from a `ZodError` to a problem body.** Two services rendered the same validation
+failure with a cap of 4 and a cap of 10, a `(+N more issues)` suffix and an `N issues, first M:`
+prefix, a bare root message and a `(root)` placeholder, and only one of them emitted `errors[]`.
+This function is the single set of conventions: cap `MAX_DETAIL_ISSUES` (8, now exported) for
+both `detail` and `errors`; overflow is ONE trailing `(+N more issues)`; a root-level issue is
+its bare message; `errors` carries bare dotted fields and is omitted when nothing survives.
+Absent keys are absent, so the result spreads straight into `problem(code, rest)` or your own
+builder. `problemFromZodError` is built on it and a test pins that the two produce byte-identical
+bodies. A service with its own problem type should route every `ZodError` through here and
+delete its local cap and overflow constants.
+
+**Added — execution detail on a status entry.** `StatusEntrySchema` and `statusEntrySchemaFor`
+gain three OPTIONAL members: `sourceTx` and `destinationTx` as
+`{ chainId, txHash, token, amount }`, and `steps[]` as
+`{ type: 'SWAP' | 'BRIDGE', status, from, to, transactions: { created?, fulfilled?, refunded? } }`
+with `{ token, amount, chainId }` legs and `{ chainId, txHash }` transaction refs. The shape
+mirrors the solver's step facts verbatim; the step `type` is the producer's vocabulary (not the
+quote-response `StepKind`) and the step `status` is the producer's raw per-step state beneath the
+C1 entry-level vocabulary, deliberately unmapped. **Absent means unknown; `null` is rejected** —
+a null would read as "known to be none" on a lane whose upstream simply has no token/amount.
+Today the quote-status lane can populate them; the general intent-status lane omits them.
+`chainId` is a JSON number (the solver spells it as a string; the producer converts), amounts
+are uint strings, `token` is a bare string because the native asset may be a sentinel. New
+schema exports `StatusTxRefSchema`, `StatusTokenAmountSchema`, `StatusTxDetailSchema`,
+`StatusStepSchema`, `StatusStepType` / `STATUS_STEP_TYPES`; new zod-free aliases `V1StatusTxRef`,
+`V1StatusTokenAmount`, `V1StatusTxDetail`, `V1StatusStep`, `V1StatusStepType`.
+
+## Migrating 0.4.1 -> 0.5.0
+
+**BREAKING under 0.x semver** (breaking bumps the minor while the major is 0): this release
+REJECTS a request body `0.4.1` accepted. Nothing else moved — no code, status, `legacyCodes`
+mapping, or response shape changed.
+
+**`V1_SCHEMA_DIGEST` DOES NOT MOVE, and that is the caveat to read before rolling out.** The new
+rule is a `superRefine`, and `z.toJSONSchema` drops refinements, so neither digest input changed:
+`openapi/v1.json` is byte-identical and `assertNoSkew` cannot see the difference. A fleet running
+`0.4.1` and `0.5.0` side by side therefore passes the skew check while VALIDATING DIFFERENTLY —
+the same body is a 400 on one instance and a 200 on another. Roll every consumer together, or
+accept that inconsistency knowingly.
+
+**Rejected — a `funder` that cannot share a chain with `source.token`.**
+
+```ts
+// 0.4.1: parses. 0.5.0: 400, path ['funder'].
+{ source: { chainId: 1399811149, token: '<a Solana mint>' }, funder: '0x3333…3333' }
+```
+
+Both fields live on the SOURCE chain, so an EVM funder beside a Solana source token describes no
+chain that exists. It used to parse, get quoted, and then fail wherever a service classified the
+funder against the source VM — and a service that read a malformed funder as ITS OWN material
+answered `500 internal-error` for a field the caller sent.
+
+**What this rule deliberately does NOT do: bind `funder` to `source.chainId`.** That needs a
+chain-ID-to-VM table, and this package holds none by design — `ChainId` is any positive integer,
+and `ADDRESS_BY_CHAIN_TYPE` exists for the caller that already knows the chain type. A table here
+would make every published version an allow-list of chains: a newly launched SVM chain would be
+misclassified by every consumer still on an older pin, and its valid base58 funder rejected, so
+this package would have to be re-released and rolled out before a chain could launch. Comparing
+two addresses from the same request needs no table and cannot go stale.
+
+So the check is a NECESSARY condition, not a sufficient one, in two specific ways:
+
+- **Two EVM addresses agree with each other whatever `chainId` says**, including a Solana chain id.
+  A green parse is not evidence the funder is right for the chain.
+- **SVM and TVM are not separated.** A Tron base58check address also satisfies `SvmAddress`'s
+  32-44 character range (see the `AnyAddress` docblock), so shape cannot decide between them and
+  the rule lets that pair through rather than guessing.
+
+A service that knows the chain's VM must still check each address against it. Two new exports help:
+`addressFamilies(value)` returns every family a value is consistent with, and
+`addressFamiliesCanAgree(a, b)` is the pairwise predicate the refinement uses.
+
 ## Migrating 0.4.0 -> 0.4.1
 
 Purely additive; no schema, wire, or digest change. `V1_SCHEMA_DIGEST` is UNCHANGED, so this is
@@ -550,10 +909,10 @@ which needs no server.
 build → lint:check → test → catalog:check → openapi:check → digest:check
 ```
 
-Both `.github/workflows/ci.yml` (every PR) and `.github/workflows/publish-api-schemas.yml`
+Both `.github/workflows/ci.yml` (every PR) and `.github/workflows/publish.yml`
 (every release tag) run exactly that one command.
 
-**The `verify`-before-`publish` step in the publish workflow is load-bearing — do not
+**The `verify`-before-`stage` step in the release workflow is load-bearing — do not
 streamline it away.** `build` uses `tsconfig.build.json`, which excludes `src/**/*.spec.ts`, so
 the compile-time gates that live in spec files — most importantly the `v1/types` parity gate —
 cannot fail `build`. They fail `test`. Publishing without running `verify` would therefore ship
@@ -577,13 +936,37 @@ Two `catalog:check` outcomes are NOT failures and must not be confused with each
 
 ## Publishing
 
-Tag `v<version>` (must equal `package.json` version) — the `publish` workflow verifies and
-publishes. It needs the `NPM_TOKEN` repo secret (an npm automation token with publish rights on
-`@eco-foundation`). It fails with `::error::tag version <x> != package version <y>`
-if the two drift, so a stale tag can never publish a mismatched artifact.
+Publishing is **two steps, and CI only does the first one.**
+
+**1. Tag `v<version>`** (must equal `package.json` version). The `Stage release` workflow
+verifies and then runs `npm stage publish`, which uploads the tarball to npm in a pending state.
+It fails with `::error::tag version <x> != package version <y>` if the two drift, so a stale tag
+can never stage a mismatched artifact. It needs the `NPM_TOKEN` repo secret: a granular token
+scoped to `@eco-foundation` with **"Read and write (stage only)"** rights.
+
+**A green run means the version is QUEUED, not released.** Nobody can install it yet.
+
+**2. A maintainer promotes it**, which costs a 2FA challenge:
+
+```
+npm stage list @eco-foundation/api-schemas
+npm stage approve <stage-id>          # or: npm stage reject <stage-id>
+```
+
+The queue is also visible on npmjs.com, and the workflow's run summary repeats these commands.
+
+Why the split: npm removes direct publish from granular access tokens in **January 2027**, and
+an approval cannot be satisfied by any CI credential — token or OIDC — by design. A stolen
+runner token can queue a release; it can never ship one. `npm stage approve` needs npm ≥
+`11.15.0` locally, same as CI.
+
+Two staging rules worth knowing before you tag. The dist-tag is **immutable once staged** — it
+cannot be changed on the way to approval, only rejected and re-staged — and a version that is
+already staged cannot be staged again, so a re-tag of a queued version fails until the queued
+one is approved or rejected.
 
 Semver: breaking schema change = major, additive = minor; consumers pin minor. **While the
-package is 0.x, "pin minor" means `~0.4.1` or the exact `0.4.1` — never `^0`** (see
+package is 0.x, "pin minor" means `~0.7.0` or the exact `0.7.0` — never `^0`** (see
 [Install](#install)). Consumers additionally compare `V1_SCHEMA_DIGEST`: a matching version
 string is not evidence of a matching artifact. `/v1/routes` is draft-tagged and exempt until its
 stability flips.

package/dist/fixtures/index.js

@@ -29,9 +29,9 @@ const FIXTURE_BINDINGS = [
     bind('quotes.create', 'response', 'public-swap', quotes_create_response_public_swap_json_1.default),
     bind('quotes.create', 'response', 'private-swap', quotes_create_response_private_swap_json_1.default),
     bind('quotes.create', 'response', 'all-quotes', quotes_create_response_all_quotes_json_1.default),
-    bind('intents.submit.permit3', 'request', 'quote-target', intents_submit_permit3_request_quote_target_json_1.default),
-    bind('intents.submit.permit2', 'request', 'quote-target', intents_submit_permit2_request_quote_target_json_1.default),
     bind('intents.submit.erc-3009', 'response', 'job', intents_submit_erc_3009_response_job_json_1.default),
+    bind('intents.submit.permit2', 'request', 'quote-target', intents_submit_permit2_request_quote_target_json_1.default),
+    bind('intents.submit.permit3', 'request', 'quote-target', intents_submit_permit3_request_quote_target_json_1.default),
     bind('deposit-addresses.submit.erc-3009', 'request', 'deposit-address-target', deposit_addresses_submit_erc_3009_request_deposit_address_target_json_1.default),
     bind('deposit-addresses.submit.erc-2612', 'request', 'deposit-address-target', deposit_addresses_submit_erc_2612_request_deposit_address_target_json_1.default),
     bind('intents.status', 'response', 'intent-filled', intents_status_response_intent_filled_json_1.default),

package/dist/fixtures/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/fixtures/index.ts"],"names":[],"mappings":";;;;;;AACA,+GAAgE;AAChE,mJAAuF;AACvF,qJAAyF;AACzF,yIAA2E;AAC3E,uLAAsG;AACtG,uLAAsG;AACtG,qIAA8E;AAC9E,iIAA2E;AAC3E,qHAAsE;AACtE,6HAAuE;AACvE,+HAA2E;AAC3E,6IAAkF;AAClF,6IAAkF;AAClF,yHAA8E;AAC9E,yHAA0E;AAC1E,6HAA0E;AAC1E,2HAAwE;AACxE,+GAAgE;AAChE,+GAAgE;AA0ChE,MAAM,IAAI,GAAG,CACX,UAAwB,EACxB,SAAiC,EACjC,OAAe,EACf,IAAa,EACb,OAA+E,EAAE,EACjF,EAAE,CAAC,CAAC,EAAE,UAAU,EAAE,SAAS,EAAE,OAAO,EAAE,IAAI,EAAE,GAAG,IAAI,EAAE,CAAC,CAAC;AAezD,MAAM,gBAAgB,GAAG;IACvB,IAAI,CAAC,eAAe,EAAE,SAAS,EAAE,aAAa,EAAE,gDAAmB,CAAC;IACpE,IAAI,CAAC,eAAe,EAAE,UAAU,EAAE,aAAa,EAAE,iDAAY,CAAC;IAC9D,IAAI,CAAC,eAAe,EAAE,UAAU,EAAE,cAAc,EAAE,kDAAa,CAAC;IAChE,IAAI,CAAC,eAAe,EAAE,UAAU,EAAE,YAAY,EAAE,gDAAe,CAAC;IAChE,IAAI,CAAC,wBAAwB,EAAE,SAAS,EAAE,cAAc,EAAE,0DAAa,CAAC;IACxE,IAAI,CAAC,wBAAwB,EAAE,SAAS,EAAE,cAAc,EAAE,0DAAa,CAAC;IACxE,IAAI,CAAC,yBAAyB,EAAE,UAAU,EAAE,KAAK,EAAE,mDAAa,CAAC;IACjE,IAAI,CAAC,mCAAmC,EAAE,SAAS,EAAE,wBAAwB,EAAE,+EAAY,CAAC;IAC5F,IAAI,CAAC,mCAAmC,EAAE,SAAS,EAAE,wBAAwB,EAAE,+EAAY,CAAC;IAC5F,IAAI,CAAC,gBAAgB,EAAE,UAAU,EAAE,eAAe,EAAE,oDAAY,CAAC;IACjE,IAAI,CAAC,gBAAgB,EAAE,UAAU,EAAE,SAAS,EAAE,8CAAa,CAAC;IAC5D,IAAI,CAAC,gBAAgB,EAAE,UAAU,EAAE,iBAAiB,EAAE,sDAAa,CAAC;IACpE,IAAI,CAAC,gBAAgB,EAAE,UAAU,EAAE,aAAa,EAAE,kDAAU,CAAC;IAC7D,IAAI,CAAC,aAAa,EAAE,UAAU,EAAE,SAAS,EAAE,2CAAU,CAAC;IACtD,IAAI,CAAC,aAAa,EAAE,UAAU,EAAE,SAAS,EAAE,2CAAU,CAAC;IAGtD,IAAI,CAAC,aAAa,EAAE,UAAU,EAAE,SAAS,EAAE,2CAAU,EAAE,EAAE,SAAS,EAAE,OAAO,EAAE,CAAC;IAC9E,IAAI,CAAC,0BAA0B,EAAE,SAAS,EAAE,eAAe,EAAE,6DAAe,CAAC;IAC7E,IAAI,CAAC,0BAA0B,EAAE,UAAU,EAAE,eAAe,EAAE,8DAAgB,CAAC;IAC/E,IAAI,CAAC,0BAA0B,EAAE,UAAU,EAAE,SAAS,EAAE,wDAAQ,CAAC;CAQhE,CAAC;AAEJ,SAAS,WAAW,CAAC,OAA0C;IAC7D,MAAM,IAAI,GAAG,OAAO,CAAC,IAA+B,CAAC;IACrD,IACE,IAAI,CAAC,UAAU,KAAK,OAAO,CAAC,UAAU;QACtC,IAAI,CAAC,SAAS,KAAK,OAAO,CAAC,SAAS;QACpC,IAAI,CAAC,OAAO,KAAK,OAAO,CAAC,OAAO,EAChC,CAAC;QACD,MAAM,IAAI,KAAK,CACb,wDAAwD;YACtD,GAAG,OAAO,CAAC,UAAU,IAAI,OAAO,CAAC,SAAS,IAAI,OAAO,CAAC,OAAO,cAAc;YAC3E,GAAG,MAAM,CAAC,IAAI,CAAC,UAAU,CAAC,IAAI,MAAM,CAAC,IAAI,CAAC,SAAS,CAAC,IAAI,MAAM,CAAC,IAAI,CAAC,OAAO,CAAC,EAAE,CACjF,CAAC;IACJ,CAAC;IAMD,MAAM,iBAAiB,GAAG,OAAO,CAAC,SAAS,IAAI,QAAQ,CAAC;IACxD,MAAM,aAAa,GAAI,IAAI,CAAC,SAAoC,IAAI,QAAQ,CAAC;IAC7E,IAAI,aAAa,KAAK,iBAAiB,EAAE,CAAC;QACxC,MAAM,IAAI,KAAK,CACb,mDAAmD;YACjD,GAAG,OAAO,CAAC,UAAU,IAAI,OAAO,CAAC,SAAS,IAAI,OAAO,CAAC,OAAO,iBAAiB;YAC9E,GAAG,iBAAiB,eAAe,aAAa,EAAE,CACrD,CAAC;IACJ,CAAC;IACD,IAAI,IAAI,CAAC,SAAS,CAAC,IAAI,CAAC,OAAO,IAAI,EAAE,CAAC,KAAK,IAAI,CAAC,SAAS,CAAC,OAAO,CAAC,OAAO,IAAI,EAAE,CAAC,EAAE,CAAC;QACjF,MAAM,IAAI,KAAK,CACb,kDAAkD;YAChD,GAAG,OAAO,CAAC,UAAU,IAAI,OAAO,CAAC,SAAS,IAAI,OAAO,CAAC,OAAO,EAAE,CAClE,CAAC;IACJ,CAAC;IACD,OAAO,IAA4B,CAAC;AACtC,CAAC;AAEY,QAAA,WAAW,GAAyB,gBAAgB,CAAC,GAAG,CAAC,WAAW,CAAC,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/fixtures/index.ts"],"names":[],"mappings":";;;;;;AACA,+GAAgE;AAChE,mJAAuF;AACvF,qJAAyF;AACzF,yIAA2E;AAC3E,uLAAsG;AACtG,uLAAsG;AACtG,qIAA8E;AAC9E,iIAA2E;AAC3E,qHAAsE;AACtE,6HAAuE;AACvE,+HAA2E;AAC3E,6IAAkF;AAClF,6IAAkF;AAClF,yHAA8E;AAC9E,yHAA0E;AAC1E,6HAA0E;AAC1E,2HAAwE;AACxE,+GAAgE;AAChE,+GAAgE;AA0ChE,MAAM,IAAI,GAAG,CACX,UAAwB,EACxB,SAAiC,EACjC,OAAe,EACf,IAAa,EACb,OAA+E,EAAE,EACjF,EAAE,CAAC,CAAC,EAAE,UAAU,EAAE,SAAS,EAAE,OAAO,EAAE,IAAI,EAAE,GAAG,IAAI,EAAE,CAAC,CAAC;AAezD,MAAM,gBAAgB,GAAG;IACvB,IAAI,CAAC,eAAe,EAAE,SAAS,EAAE,aAAa,EAAE,gDAAmB,CAAC;IACpE,IAAI,CAAC,eAAe,EAAE,UAAU,EAAE,aAAa,EAAE,iDAAY,CAAC;IAC9D,IAAI,CAAC,eAAe,EAAE,UAAU,EAAE,cAAc,EAAE,kDAAa,CAAC;IAChE,IAAI,CAAC,eAAe,EAAE,UAAU,EAAE,YAAY,EAAE,gDAAe,CAAC;IAChE,IAAI,CAAC,yBAAyB,EAAE,UAAU,EAAE,KAAK,EAAE,mDAAa,CAAC;IACjE,IAAI,CAAC,wBAAwB,EAAE,SAAS,EAAE,cAAc,EAAE,0DAAa,CAAC;IACxE,IAAI,CAAC,wBAAwB,EAAE,SAAS,EAAE,cAAc,EAAE,0DAAa,CAAC;IACxE,IAAI,CAAC,mCAAmC,EAAE,SAAS,EAAE,wBAAwB,EAAE,+EAAY,CAAC;IAC5F,IAAI,CAAC,mCAAmC,EAAE,SAAS,EAAE,wBAAwB,EAAE,+EAAY,CAAC;IAC5F,IAAI,CAAC,gBAAgB,EAAE,UAAU,EAAE,eAAe,EAAE,oDAAY,CAAC;IACjE,IAAI,CAAC,gBAAgB,EAAE,UAAU,EAAE,SAAS,EAAE,8CAAa,CAAC;IAC5D,IAAI,CAAC,gBAAgB,EAAE,UAAU,EAAE,iBAAiB,EAAE,sDAAa,CAAC;IACpE,IAAI,CAAC,gBAAgB,EAAE,UAAU,EAAE,aAAa,EAAE,kDAAU,CAAC;IAC7D,IAAI,CAAC,aAAa,EAAE,UAAU,EAAE,SAAS,EAAE,2CAAU,CAAC;IACtD,IAAI,CAAC,aAAa,EAAE,UAAU,EAAE,SAAS,EAAE,2CAAU,CAAC;IAGtD,IAAI,CAAC,aAAa,EAAE,UAAU,EAAE,SAAS,EAAE,2CAAU,EAAE,EAAE,SAAS,EAAE,OAAO,EAAE,CAAC;IAC9E,IAAI,CAAC,0BAA0B,EAAE,SAAS,EAAE,eAAe,EAAE,6DAAe,CAAC;IAC7E,IAAI,CAAC,0BAA0B,EAAE,UAAU,EAAE,eAAe,EAAE,8DAAgB,CAAC;IAC/E,IAAI,CAAC,0BAA0B,EAAE,UAAU,EAAE,SAAS,EAAE,wDAAQ,CAAC;CAQhE,CAAC;AAEJ,SAAS,WAAW,CAAC,OAA0C;IAC7D,MAAM,IAAI,GAAG,OAAO,CAAC,IAA+B,CAAC;IACrD,IACE,IAAI,CAAC,UAAU,KAAK,OAAO,CAAC,UAAU;QACtC,IAAI,CAAC,SAAS,KAAK,OAAO,CAAC,SAAS;QACpC,IAAI,CAAC,OAAO,KAAK,OAAO,CAAC,OAAO,EAChC,CAAC;QACD,MAAM,IAAI,KAAK,CACb,wDAAwD;YACtD,GAAG,OAAO,CAAC,UAAU,IAAI,OAAO,CAAC,SAAS,IAAI,OAAO,CAAC,OAAO,cAAc;YAC3E,GAAG,MAAM,CAAC,IAAI,CAAC,UAAU,CAAC,IAAI,MAAM,CAAC,IAAI,CAAC,SAAS,CAAC,IAAI,MAAM,CAAC,IAAI,CAAC,OAAO,CAAC,EAAE,CACjF,CAAC;IACJ,CAAC;IAMD,MAAM,iBAAiB,GAAG,OAAO,CAAC,SAAS,IAAI,QAAQ,CAAC;IACxD,MAAM,aAAa,GAAI,IAAI,CAAC,SAAoC,IAAI,QAAQ,CAAC;IAC7E,IAAI,aAAa,KAAK,iBAAiB,EAAE,CAAC;QACxC,MAAM,IAAI,KAAK,CACb,mDAAmD;YACjD,GAAG,OAAO,CAAC,UAAU,IAAI,OAAO,CAAC,SAAS,IAAI,OAAO,CAAC,OAAO,iBAAiB;YAC9E,GAAG,iBAAiB,eAAe,aAAa,EAAE,CACrD,CAAC;IACJ,CAAC;IACD,IAAI,IAAI,CAAC,SAAS,CAAC,IAAI,CAAC,OAAO,IAAI,EAAE,CAAC,KAAK,IAAI,CAAC,SAAS,CAAC,OAAO,CAAC,OAAO,IAAI,EAAE,CAAC,EAAE,CAAC;QACjF,MAAM,IAAI,KAAK,CACb,kDAAkD;YAChD,GAAG,OAAO,CAAC,UAAU,IAAI,OAAO,CAAC,SAAS,IAAI,OAAO,CAAC,OAAO,EAAE,CAClE,CAAC;IACJ,CAAC;IACD,OAAO,IAA4B,CAAC;AACtC,CAAC;AAEY,QAAA,WAAW,GAAyB,gBAAgB,CAAC,GAAG,CAAC,WAAW,CAAC,CAAC"}

package/dist/fixtures/v1/intents-submit-permit2.request.quote-target.json

@@ -7,18 +7,19 @@
     "expectedStatus": 202,
     "sideEffect": true,
     "payload": {
+        "chainId": 8453,
         "target": {
             "quoteId": "quote:8f14e45f-ea3c-4c2d-9b6e-1a2b3c4d5e6f"
         },
         "permit2": {
             "details": {
-                "token": "0x2222222222222222222222222222222222222222",
+                "token": "0x1111111111111111111111111111111111111111",
                 "amount": "1043221",
                 "expiration": 1767225600,
                 "nonce": 0
             },
-            "spender": "0x1111111111111111111111111111111111111111",
-            "sigDeadline": 1767225600
+            "spender": "0x5555555555555555555555555555555555555555",
+            "sigDeadline": "1767225600"
         },
         "signature": "0xcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcd"
     }

package/dist/fixtures/v1/intents-submit-permit3.request.quote-target.json

@@ -11,14 +11,19 @@
             "quoteId": "quote:8f14e45f-ea3c-4c2d-9b6e-1a2b3c4d5e6f"
         },
         "permit3": {
-            "owner": "0x1111111111111111111111111111111111111111",
+            "owner": "0x3333333333333333333333333333333333333333",
+            "permitContract": "0x6666666666666666666666666666666666666666",
             "salt": "0xabababababababababababababababababababababababababababababababab",
             "deadline": 1767225600,
+            "timestamp": 1767222000,
+            "merkleRoot": "0x7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a",
             "permits": [
                 {
                     "chainId": 8453,
-                    "token": "0x2222222222222222222222222222222222222222",
-                    "amount": "1043221"
+                    "token": "0x1111111111111111111111111111111111111111",
+                    "amount": "1043221",
+                    "account": "0x5555555555555555555555555555555555555555",
+                    "modeOrExpiration": 0
                 }
             ]
         },

package/dist/fixtures/v1/quotes-create.response.all-quotes.json

@@ -149,7 +149,8 @@
                 }
             },
             "encodedRoute": "0xdead",
-            "encodedReward": "0xbeef"
+            "encodedReward": "0xbeef",
+            "vault": "0x5555555555555555555555555555555555555555"
         },
         "expiresAt": 1767225600,
         "signature": "0xcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcd",
@@ -297,7 +298,8 @@
                         }
                     },
                     "encodedRoute": "0xdead",
-                    "encodedReward": "0xbeef"
+                    "encodedReward": "0xbeef",
+                    "vault": "0x5555555555555555555555555555555555555555"
                 },
                 "expiresAt": 1767225600,
                 "signature": "0xcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcd"
@@ -445,7 +447,8 @@
                         }
                     },
                     "encodedRoute": "0xdead",
-                    "encodedReward": "0xbeef"
+                    "encodedReward": "0xbeef",
+                    "vault": "0x7777777777777777777777777777777777777777"
                 },
                 "expiresAt": 1767225600,
                 "signature": "0x9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a9a"

package/dist/fixtures/v1/quotes-create.response.private-swap.json

@@ -143,7 +143,8 @@
                 }
             },
             "encodedRoute": null,
-            "encodedReward": null
+            "encodedReward": null,
+            "vault": "0x5555555555555555555555555555555555555555"
         },
         "expiresAt": 1767225600,
         "signature": "0xcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcd",

package/dist/fixtures/v1/quotes-create.response.public-swap.json

@@ -149,7 +149,8 @@
                 }
             },
             "encodedRoute": "0xdead",
-            "encodedReward": "0xbeef"
+            "encodedReward": "0xbeef",
+            "vault": "0x5555555555555555555555555555555555555555"
         },
         "expiresAt": 1767225600,
         "signature": "0xcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcd",

package/dist/fixtures/v1/tokens-list.response.default.json

@@ -14,7 +14,7 @@
                 "symbol": "USDC",
                 "decimals": 6,
                 "supports": {
-                    "quote": ["permit3", "permit2", "erc-3009"],
+                    "quote": ["erc-3009", "permit2", "permit3"],
                     "depositAddress": ["erc-2612", "erc-3009"]
                 }
             }

package/dist/generated/build-digest.json

@@ -1,5 +1,5 @@
 {
-    "digest": "1d8e88e957795b23e1317dc1e3783fd64bf79b756e3f28bd40e02b047542d790",
+    "digest": "3e13c5eeb8b054f3a48a22c7694de16b0fc11e1dbf6bc3c27e8c575100225b2a",
     "inputs": [
         "errors/catalog.lock.json",
         "openapi/v1.json"

package/dist/index.d.ts

@@ -3,4 +3,4 @@ export { generateOpenApiDocument, STABLE_TAG } from './openapi';
 export type { V1Fixture } from './testing';
 export { assertMatchesV1Schema, loadV1Fixtures } from './testing';
 export * as v1 from './v1';
-export type { LegacyCodeRef, V1Chain, V1ChainType, V1DepositAddress, V1DepositAddressChainStatus, V1DepositAddressCreateRequest, V1DepositAddressCreateResponse, V1DepositAddressKind, V1DestinationCall, V1ErrorCode, V1ErrorDefinition, V1Execution, V1Fee, V1FeeKind, V1FeeToken, V1FundingTransaction, V1GaslessJob, V1GaslessJobStatus, V1GaslessSubState, V1GaslessSubStatus, V1Guarantee, V1IntentCall, V1IntentReward, V1IntentRoute, V1IntentTokenAmount, V1ProblemBody, V1QuoteCore, V1QuoteRequest, V1QuoteResponse, V1RankedQuoteEntry, V1RelatedIntent, V1RelatedIntentRole, V1SolverIdentity, V1StatusEntry, V1StatusType, V1Step, V1StepKind, V1StepLeg, V1SvmAccountMeta, V1SvmInstruction, V1SwapType, V1TokenEntry, V1Visibility, } from './v1/types';
+export type { LegacyCodeRef, V1Chain, V1ChainType, V1DepositAddress, V1DepositAddressChainStatus, V1DepositAddressCreateRequest, V1DepositAddressCreateResponse, V1DepositAddressKind, V1DestinationCall, V1ErrorCode, V1ErrorDefinition, V1Execution, V1Fee, V1FeeKind, V1FeeToken, V1FundingTransaction, V1GaslessJob, V1GaslessJobStatus, V1GaslessSubState, V1GaslessSubStatus, V1Guarantee, V1IntentCall, V1IntentReward, V1IntentRoute, V1IntentTokenAmount, V1ProblemBody, V1QuoteCore, V1QuoteRequest, V1QuoteResponse, V1RankedQuoteEntry, V1RelatedIntent, V1RelatedIntentRole, V1SolverIdentity, V1StatusEntry, V1StatusStep, V1StatusStepType, V1StatusTokenAmount, V1StatusTxDetail, V1StatusTxRef, V1StatusType, V1Step, V1StepKind, V1StepLeg, V1SvmAccountMeta, V1SvmInstruction, V1SwapType, V1TokenEntry, V1Visibility, } from './v1/types';

package/dist/v1/endpoints/chains.d.ts

@@ -1,4 +1,11 @@
 import { z } from 'zod';
+export declare const CHAINS_LIST_QUERY_SHAPE: {
+    chainId: z.ZodOptional<z.ZodCoercedNumber<unknown>>;
+};
+export declare const ChainsListQuerySchema: z.ZodObject<{
+    chainId: z.ZodOptional<z.ZodCoercedNumber<unknown>>;
+}, z.core.$strip>;
+export type ChainsListQuery = z.infer<typeof ChainsListQuerySchema>;
 export declare const ChainContractsSchema: z.ZodObject<{
     portal: z.ZodUnion<readonly [z.ZodString, z.ZodUnion<readonly [z.ZodString, z.ZodString]>, z.ZodString]>;
     executor: z.ZodNullable<z.ZodUnion<readonly [z.ZodString, z.ZodUnion<readonly [z.ZodString, z.ZodString]>, z.ZodString]>>;

package/dist/v1/endpoints/chains.js

@@ -1,10 +1,14 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.ChainsResponseSchema = exports.V1LimitsSchema = exports.ChainSchema = exports.ChainContractsSchema = void 0;
+exports.ChainsResponseSchema = exports.V1LimitsSchema = exports.ChainSchema = exports.ChainContractsSchema = exports.ChainsListQuerySchema = exports.CHAINS_LIST_QUERY_SHAPE = void 0;
 const zod_1 = require("zod");
 const enums_1 = require("../enums");
 const primitives_1 = require("../primitives");
 const status_1 = require("./status");
+exports.CHAINS_LIST_QUERY_SHAPE = {
+    chainId: primitives_1.ChainIdParam.optional(),
+};
+exports.ChainsListQuerySchema = zod_1.z.object(exports.CHAINS_LIST_QUERY_SHAPE);
 exports.ChainContractsSchema = zod_1.z.looseObject({
     portal: primitives_1.AnyAddress,
     executor: primitives_1.AnyAddress.nullable(),