@coinlist-co/react 0.12.2-rc.818bed6 → 0.12.2-rc.99b1bd5

package/dist/time-DJU6E8KK.d.ts

@@ -1,4052 +0,0 @@
-import { Hash, Transport, PublicClient, Hex } from 'viem';
-
-declare const __brand: unique symbol;
-type Newtype<Base, Branding> = Base & {
-    readonly [__brand]: Branding;
-};
-
-type AuthorizationCode = Newtype<string, 'AuthorizationCode'>;
-declare const AuthorizationCode: (value: string) => AuthorizationCode;
-type CodeVerifier = Newtype<string, 'CodeVerifier'>;
-declare const CodeVerifier: (value: string) => CodeVerifier;
-type CodeChallenge = Newtype<string, 'CodeChallenge'>;
-declare const CodeChallenge: (value: string) => CodeChallenge;
-type PKCEState = Newtype<string, 'PKCEState'>;
-declare const PKCEState: (value: string) => PKCEState;
-type RedirectUri = Newtype<string, 'RedirectUri'>;
-declare const RedirectUri: (value: string) => RedirectUri;
-type ClientId = Newtype<string, 'ClientId'>;
-declare const ClientId: (value: string) => ClientId;
-type ClientSecret = Newtype<string, 'ClientSecret'>;
-declare const ClientSecret: (value: string) => ClientSecret;
-
-/**
- * A classified wallet or transaction failure. The SDK derives this from
- * whatever the {@link EvmWallet} throws, so hosts get a stable, typed error
- * shape regardless of the wallet library underneath.
- *
- * Lives here rather than beside its classifier because it is the failure half
- * of the {@link EvmWallet} contract, and because both `@/universal` and
- * `@/client` name it: {@link LogCause} carries one, and classifying a thrown
- * error into one needs viem's error classes, which are browser-side.
- */
-type WalletError = {
-    type: 'user_rejected';
-} | {
-    type: 'insufficient_funds';
-} | {
-    type: 'contract_reverted';
-    /**
-     * What the contract said, when it said anything: a `require` string, a
-     * panic description, a custom error's name, or the four-byte selector of
-     * an error the ABI could not decode.
-     *
-     * `null` when a revert carried no data, since the string the RPC node
-     * offers in its place is not the contract's - see `classifyWalletError`.
-     * Nullable rather than optional so that every arm has to answer the
-     * question: "it reverted and said nothing" is a fact about the revert,
-     * and a caller should have to read it rather than miss it.
-     *
-     * Never the custom error's arguments. A name is a compile-time
-     * identifier; its operands are runtime values - an address, a balance -
-     * and those are `'debug'` material.
-     */
-    reason: string | null;
-} | {
-    type: 'timeout';
-    hash: Hash;
-} | {
-    type: 'unknown';
-    cause: unknown;
-};
-/**
- * A {@link WalletError} as it may be reported above `'debug'`: the
- * classification, never the throw.
- *
- * Only the `unknown` arm differs, and it differs because it is the one arm
- * carrying a value the SDK did not author - the raw error the wallet library
- * threw, whose message and metadata hold the transaction's `from`, `to`,
- * `value` and calldata. The other four carry compile-time constants or a
- * server-minted identifier already, so they pass through as they stand.
- *
- * This exists as a type rather than as a scrub some function remembers to
- * apply: `LogCause` names it, so an arm that grew a raw field would fail the
- * build instead of quietly reaching {@link Logger.error}.
- */
-type RedactedWalletError = Exclude<WalletError, {
-    type: 'unknown';
-}> | {
-    type: 'unknown';
-};
-declare const RedactedWalletError: {
-    fromWalletError: (error: WalletError) => RedactedWalletError;
-};
-
-/**
- * The observability seam a host implements to see inside the SDK.
- *
- * Pass an implementation as {@link Config.logger} and the SDK reports every
- * request it makes, every failure it classifies, and every state a hook
- * settles into. Leave it out and the SDK logs nothing at all - there is no
- * fallback to `console`, at any level, on any codepath.
- *
- * Four methods over a {@link LogEvent} lambda, plus {@link level}. An event is
- * a constant `msg`, the {@link LogScope} it came from, the accumulated
- * {@link LogBindings}, and a bag of `fields` - so a host forwards structured
- * records rather than parsing strings.
- *
- * ```ts
- * const logger: Logger = {
- *   level: () => 'info',
- *   debug: () => {},
- *   info: (event) => sink.info(toRecord(event())),
- *   warn: (event) => sink.warn(toRecord(event())),
- *   error: (event) => sink.error(toRecord(event())),
- * };
- * ```
- *
- * {@link pinoClientLogger} and {@link pinoServerLogger} are ready-made
- * implementations over pino, and are what most hosts should reach for.
- *
- * ## Where to run it
- *
- * **Not in production, as the default answer.** Development, tests, staging,
- * and reproducing a reported bug are where this seam earns its keep. Left
- * undefined elsewhere it discloses nothing, and that holds no matter what a
- * later revision of the SDK puts on a line.
- *
- * Where you do run one in production, `'info'` and above is the only sane
- * choice, and the shipped implementations make the alternative unrepresentable
- * rather than merely discouraged: `isDev: false` narrows the level to
- * {@link ProductionLogLevel}, so `'debug'` does not compile. That narrowing is
- * a guard for the partner who ignored this paragraph, not an endorsement of
- * the practice.
- *
- * The distinction worth holding onto: `'info'` and above are **redacted by
- * construction** - see the next section for exactly what that covers, and the
- * type that enforces it. Redacted is a mechanism the SDK can hold itself to. A
- * blanket "safe in production" is a promise about your environment that the
- * SDK is in no position to make, and one that a single future field could
- * quietly break.
- *
- * `'debug'` is for reproducing a bug: a developer's machine, tests, and beta
- * or staging environments where the data flowing through the SDK is not real
- * customer data.
- *
- * ## What each level may disclose
- *
- * **`'debug'` is unredacted. Every other level is not.**
- *
- * At `'debug'` the SDK reports request and response bodies, request headers,
- * the full URL including its query string, and operation parameters
- * **verbatim** - bearer tokens, KYC answers, tax-document fields, wallet
- * signatures, the lot. There is no denylist and no redaction: see ADR-8 for
- * why a partial guarantee was rejected in favour of an honest absence of one.
- *
- * At `'info'`, `'warn'` and `'error'` the SDK emits only its own
- * classification of what happened and identifiers the server minted: a method
- * and a bare path, a status, a duration, a {@link RequestId}, a frontline
- * error code and event id, a {@link LogCause} arm. No request body, no
- * response body, no query string, no host-supplied parameters, and no message
- * text read off a thrown error the SDK did not author.
- *
- * The type carries that boundary rather than merely documenting it:
- * {@link SafeEvent} constrains every field value to a {@link LogValue} scalar,
- * so spreading a body, a DTO or an operation's params into an `info`, `warn`
- * or `error` line does not compile. Only {@link DebugEvent} accepts arbitrary
- * values.
- *
- * The one deliberate exception is an SDK-authored validation message, which
- * quotes the single scalar that failed to map - `Unsupported chain:
- * "solana_mainnet"`. It is a hand-written template naming one offending value,
- * not a payload, and it is the whole reason this seam exists.
- *
- * ## Your responsibility
- *
- * The SDK hands you events. What happens next is yours: **you own the final
- * filtering, redaction and retention** before anything is written to a file, a
- * console, or a third-party sink such as Sentry or Datadog. In particular, if
- * you implement {@link debug} and forward it anywhere durable, you have taken
- * on storing live credentials and personal data, deliberately. Implement
- * `debug` as a no-op - or return a level below it from {@link level} - in any
- * environment where that is not acceptable.
- *
- * **Every event is a lambda, and that is load bearing.** The SDK consults
- * {@link level} first and never invokes the lambda when the level forbids it,
- * so an expensive debug event - a serialized DTO, a loop over balances - costs
- * nothing in production where the level is `'error'` or `'none'`. Build the
- * event inside the lambda, never outside it.
- *
- * ## Every method must be total
- *
- * **None of the five methods may throw, and that includes {@link level}.** The
- * SDK calls them inline, on the codepath of the work it is reporting, and it
- * does not catch them: a `logger.error` that throws while reporting a failed
- * request turns that request's rejection into your logger's exception, and a
- * `level()` that throws breaks the call it was asked about even when nothing
- * else went wrong.
- *
- * That is deliberate. Swallowing would hide a logger that is broken in every
- * environment, and the SDK cannot tell a transport blip in your sink from a
- * bug in your implementation. So the contract is on this side of the seam:
- * catch inside your implementation, and never let an exception out. The
- * shipped pino implementations do exactly that.
- *
- * ```ts
- * error: (event) => {
- *   try {
- *     const e = event();
- *     Sentry.captureMessage(e.msg, { extra: e });
- *   } catch {
- *     // never rethrow: the SDK is on the other side of this call
- *   }
- * },
- * ```
- */
-interface Logger {
-    /**
-     * The most detailed level this logger wants. Consulted before **every** log
-     * call, so keep it cheap and pure: return a captured constant or read a
-     * plain field. Do not read an environment variable, hit storage, or call
-     * out to a feature-flag service here.
-     *
-     * Returning `'none'` silences the SDK as completely as omitting the logger.
-     *
-     * **Must not throw.** It is consulted inside every SDK operation, so an
-     * exception here fails the operation itself.
-     */
-    level(): LogLevel;
-    /**
-     * Fine-grained detail: request and response bodies, full URLs, headers,
-     * operation parameters, hook transitions.
-     *
-     * **Unredacted.** This is the only level that may carry credentials or
-     * personal data, and it always may. Its event is a {@link DebugEvent}, whose
-     * fields accept arbitrary values for exactly that reason. Do not forward it
-     * to a durable or third-party sink outside development and beta.
-     *
-     * **Must not throw**, here and on every method below.
-     */
-    debug(event: () => DebugEvent): void;
-    /** Notable, expected events: a request completing, a flow advancing. */
-    info(event: () => SafeEvent): void;
-    /**
-     * Recoverable trouble: a retried request, a renewed session, a poll tick
-     * that failed while the last value still stands.
-     *
-     * Carries a {@link LogCause} when one was classified, the same as
-     * {@link error} does. What separates the two levels is whether anything
-     * actually broke, not how much is known about it.
-     */
-    warn(event: () => SafeEvent): void;
-    /**
-     * A failure. {@link SafeEvent.cause} carries what the SDK knows about it,
-     * classified into {@link LogCause}, and is absent when the failure is not an
-     * error the SDK caught - a flow reporting the step it stopped at, for
-     * instance.
-     *
-     * Every part of the event is SDK-authored classification or server-authored
-     * identifiers, so forwarding it as it stands is safe. `scope` says which
-     * part of the SDK the line came from, which is what to route or filter on.
-     */
-    error(event: () => SafeEvent): void;
-}
-/**
- * A value the SDK is willing to put in a structured field above `'debug'`.
- *
- * Scalars only, and that is the redaction boundary made structural rather than
- * documentary. Every leak ADR-8 found was an *object* spread onto a line that
- * a host forwards to a tracker - an operation's params, a thrown wallet error,
- * a response body. None of them is assignable to this, so each is now a
- * compile error rather than a review catch.
- *
- * It does not stop a call site writing `{ token: accessToken }`, and it is not
- * meant to: a string is a string. What it stops is the mistake that actually
- * happened.
- */
-type LogValue = string | number | boolean | null;
-/**
- * Fields safe at every level: SDK-authored classification and server-minted
- * identifiers, constrained to {@link LogValue}.
- */
-type SafeFields = Readonly<Record<string, LogValue>>;
-/**
- * Fields for `'debug'` only: bodies, headers, full URLs, operation params,
- * raw thrown values. Arbitrary values, because that is the point of the level.
- *
- * The SDK's own implementations render these into a form that cannot fail to
- * serialize - a `bigint`, a cycle or a getter that throws must never turn a
- * log line into a second failure - but they are otherwise passed through.
- */
-type UnredactedFields = Readonly<Record<string, unknown>>;
-/**
- * One narrowing applied to a logger by {@link InternalLogger.child}.
- *
- * A union of single-key objects rather than a positional `string`, because the
- * three things the SDK narrows by are not the same kind of thing: a request id
- * correlates retries of one wire call, a flow name names an on-chain
- * procedure, a hook name names a React binding. Rendered into one `[SCOPE:x]`
- * prefix they were indistinguishable; as fields they must not be.
- *
- * `requestId` keeps its {@link RequestId} newtype rather than widening to
- * `string` at the seam.
- */
-type LogBinding = {
-    readonly requestId: RequestId;
-} | {
-    readonly flow: string;
-} | {
-    readonly hook: string;
-} | {
-    readonly op: string;
-};
-/**
- * Every {@link LogBinding} applied so far, merged. This is what reaches a
- * host, so a line from `prepareOndoSell` carries `flow: 'prepareSell'` as its
- * own key and is filterable without parsing anything.
- */
-type LogBindings = {
-    readonly [K in LogBinding as keyof K]?: K[keyof K];
-};
-type BaseEvent = {
-    /**
-     * What happened, as a **constant string literal**.
-     *
-     * Never interpolated. A log aggregator groups by message, so a `msg` that
-     * embeds a status, a count or a reason produces one group per distinct
-     * value and is not groupable at all. Every varying value belongs in
-     * `fields`, which is what a host filters and facets on.
-     *
-     * This is a convention, not a checked rule: deslop reasons about import
-     * edges and cannot see a template literal, and the type-level approximations
-     * catch only some interpolations. ADR-8 records why a partial guarantee was
-     * refused here as elsewhere.
-     */
-    readonly msg: string;
-    /**
-     * Which part of the SDK reported this. Stamped by
-     * {@link internalLogger}, never by a call site.
-     */
-    readonly scope: LogScope;
-    /** Every {@link LogBinding} applied by {@link InternalLogger.child}. */
-    readonly bindings: LogBindings;
-};
-/**
- * An event for `'info'`, `'warn'` and `'error'` - the levels a host may run in
- * production.
- *
- * Its fields are {@link SafeFields}, so nothing but a scalar can reach it.
- */
-type SafeEvent = BaseEvent & {
-    readonly fields: SafeFields;
-    /**
-     * What the SDK knows about an accompanying failure, classified. Absent when
-     * there is nothing to classify.
-     */
-    readonly cause?: LogCause;
-};
-/**
- * An event for `'debug'`, the unredacted level. Its fields accept anything.
- */
-type DebugEvent = BaseEvent & {
-    readonly fields: UnredactedFields;
-};
-/**
- * How much the SDK may report, from silent to everything.
- *
- * Ordered: each level admits itself and everything before it, so `'info'`
- * shows errors, warnings and info but not debug. `'none'` admits nothing.
- *
- * `'debug'` is the unredacted level, and it is deliberately the bottom of the
- * ladder: the guarantee "`debug` is unredacted and every other level is not"
- * only closes if there is nothing below it. That is why the SDK keeps its own
- * five levels rather than adopting pino's seven, which put `trace` underneath.
- */
-type LogLevel = 'none' | 'error' | 'warn' | 'info' | 'debug';
-/**
- * The redacted levels: the only ones to consider running in production.
- *
- * Every level except `'debug'`, which is unredacted by design. Used by the
- * shipped pino implementations to make a production `'debug'` logger
- * unrepresentable rather than merely discouraged - see
- * {@link PinoLoggerOptions}.
- *
- * The name marks which levels are *redacted*, not a verdict that running them
- * in production is safe. The SDK's advice is to leave {@link Config.logger}
- * undefined there; this type is what stops the partner who does not take it
- * from reaching the unredacted level as well.
- */
-type ProductionLogLevel = Exclude<LogLevel, 'debug'>;
-/**
- * How to build one of the SDK's pino-backed loggers.
- *
- * A union rather than `{ level, isDev }`, and that is the whole point:
- * `{ isDev: false, level: 'debug' }` does not typecheck, so a production
- * build cannot ship a logger that prints bearer tokens to a browser console.
- *
- * `isDev` does exactly one thing - decide whether `'debug'` is a legal level.
- * It changes no formatting: dev output and production output are the same
- * shape, so what you debug is what you ship. Pretty-printing is a pipe the
- * host owns (`node server.js | npx pino-pretty`), not a dependency the SDK
- * takes.
- */
-type PinoLoggerOptions = {
-    readonly isDev: true;
-    readonly level: LogLevel;
-} | {
-    readonly isDev: false;
-    readonly level: ProductionLogLevel;
-};
-/**
- * Which part of the SDK a line came from, carried as the `scope` field on
- * every event.
- *
- * It names the seam that **reported** the line, not the layer that raised what
- * it reports: an error from `OFFERS` surfaced by `useOffers` is reported on a
- * `HOOKS` line, because that is the hook telling you what it did with it. The
- * `OFFERS` line for the same error is emitted separately, by the namespace.
- *
- * A closed union rather than a free string so that `ONDO` and `Ondo` cannot
- * both appear, so that adding a namespace without giving it a scope fails to
- * compile, and so that a host can `switch` on it when routing. Anything finer
- * - an operation, a flow, a hook - is a {@link LogBinding} and appears as its
- * own field.
- */
-type LogScope = 'HTTP' | 'RPC' | 'AUTH' | 'OFFERS' | 'REQUIREMENTS' | 'WALLETS' | 'ERC20' | 'TOKEN_SALE' | 'SUPERSTATE' | 'ONDO' | 'CENTRIFUGE' | 'TOKENS' | 'SUPPORT' | 'HOOKS';
-/**
- * Correlates every line one logical request produces. The first attempt, each
- * retry, and the re-send after a session renewal all carry the same id, so a
- * failure can be read back to the request that caused it.
- */
-type RequestId = Newtype<string, 'RequestId'>;
-/**
- * The id frontline keys its own logs by, minted server-side and returned as
- * `event_id` on an error envelope. Quote it when raising a ticket with
- * CoinList support: it is what leads from a partner's log line to the request
- * as the backend saw it.
- *
- * A {@link Newtype} rather than a bare `string` because it sits next to
- * {@link RequestId} and frontline's `code` on the same cause, and the three
- * are not interchangeable: an id swapped for a code reads plausibly and points
- * a support engineer at nothing.
- */
-type FrontlineEventId = Newtype<string, 'FrontlineEventId'>;
-/**
- * What the SDK knows about a failure, classified.
- *
- * **Safe to forward as it stands.** Every arm is SDK-authored classification
- * or a server-authored identifier: no request or response body, no host-
- * supplied parameter, and no value read off a thrown error the SDK did not
- * author. There is nothing here to strip before handing it to an error
- * tracker, which is deliberate - a `LogCause` reaches {@link Logger.error},
- * the level a host actually runs in production, and a guarantee that depends
- * on the host remembering to strip a field is not a guarantee.
- *
- * It is the SDK's **only** structured classification of a thrown error, and it
- * reaches {@link Logger.warn} as well as {@link Logger.error}: a recoverable
- * failure is no less worth naming than a fatal one, and rendering it into a
- * string instead would have meant interpolating into `msg`.
- *
- * Bodies are a `'debug'`-only disclosure and stay on the `HTTP` lines, which
- * {@link RequestId} points at.
- *
- * The arms are the remedies, not the exception classes: a `validation` cause
- * means the backend sent something the SDK does not understand and is worth
- * reporting to CoinList, while an `invariant` cause means the SDK itself
- * computed something impossible and is worth reporting as an SDK bug. Reading
- * `type` should tell you who has to fix it.
- *
- * It carries no scope of its own. The {@link SafeEvent} it arrives on has one,
- * and a cause could only ever have repeated it: the scope is stamped by the
- * logger that *emits* the line, not by the layer that raised the error, so a
- * `validation` failure from `OFFERS` surfaced by `useOffers` would have been
- * tagged `HOOKS` on the hook's line. Forward the event, not the cause alone.
- */
-/**
- * Why an on-chain read failed, named after what a caller would do about it
- * rather than after the viem error class that reported it. See the `rpc` arm
- * of {@link LogCause}.
- */
-type RpcFailureReason = 'reverted' | 'node-rejected' | 'transport' | 'malformed-response' | 'unknown';
-type LogCause = 
-/**
- * A request reached the backend and came back non-2xx.
- *
- * Deliberately carries no response body. `requestId` is how you get the
- * rest: the `HTTP` lines for the same request carry the method, the path,
- * the duration, every retry, and at `'debug'` the body itself. `code` and
- * `eventId` are frontline's own - quote `eventId` when raising a ticket with
- * CoinList support.
- */
-{
-    type: 'http';
-    requestId: RequestId | null;
-    status: number;
-    code: string | null;
-    eventId: FrontlineEventId | null;
-}
-/**
- * The wire succeeded; the payload was not a shape the SDK can map.
- *
- * `message` is an SDK-authored template and may quote the single scalar that
- * failed - `Unsupported chain: "solana_mainnet"`, `expires_at: not a date
- * ("13/40/2026")`. That one value is the point of the arm; it is never a
- * body and never a whole field set.
- */
- | {
-    type: 'validation';
-    message: string;
-}
-/**
- * The SDK computed something impossible. An SDK bug - please report it.
- * `message` is an SDK-authored template, like `validation`'s.
- */
- | {
-    type: 'invariant';
-    message: string;
-}
-/**
- * Every operand was well-formed and the arithmetic on them still had no
- * answer: a division by zero, a result outside the range its type can hold.
- * `message` is an SDK-authored template, like `validation`'s.
- *
- * Separate from `invariant` because the remedy differs. An `invariant` says
- * the SDK computed something impossible and is a bug to report against the
- * SDK; a `math` says the operation was well-posed and the operands, which
- * came off the wire, admit no result - so it points at the response the same
- * way `validation` does, one step later.
- */
- | {
-    type: 'math';
-    message: string;
-}
-/** An API-backed call was made without a logged-in user. */
- | {
-    type: 'not-authenticated';
-}
-/** A code path the SDK has not shipped yet. */
- | {
-    type: 'not-implemented';
-}
-/**
- * The user's wallet, or the chain, refused.
- *
- * {@link RedactedWalletError} rather than the full `WalletError`: its
- * `unknown` arm arrives with its `cause` dropped, that field holding the raw
- * wallet-library error whose message and metadata carry the transaction's
- * `from`, `to`, `value` and calldata. It is still on the flow's own returned
- * result, and on the `'debug'` line the flow seam emits beside this one.
- *
- * A type rather than a scrub applied at the call site, so an arm that grew a
- * raw field would fail the build.
- */
- | {
-    type: 'wallet';
-    error: RedactedWalletError;
-}
-/**
- * An on-chain read did not answer. `reason` names the remedy, not the viem
- * class that carried it:
- *
- * - `reverted` - the contract refused the call. Check the arguments, or the
- *   contract's own state (a stopped swap reverts its `preview`).
- * - `node-rejected` - the node reached the contract and declined. Usually a
- *   malformed request, a rate limit, or a method the node does not serve.
- *   Also where a host-supplied `Transport` throwing something viem cannot
- *   read a code off lands: `buildRequest` wraps it in `UnknownRpcError`.
- * - `transport` - the node was not reached at all. Retry, or fail over.
- *   A dropped `webSocket()` socket included.
- * - `malformed-response` - the call returned something the ABI cannot
- *   decode, which in practice means the wrong address or a stale ABI.
- * - `unknown` - anything else. Rare, since viem wraps most of what a read
- *   can throw into one of the classes the arms above name.
- *
- * Decided by `instanceof` alone. Nothing is read off the thrown error - not
- * its `name`, not its `message`, not a revert reason - because a viem
- * message embeds the calldata, the contract address and the caller, and
- * `name` is a writable property a host-supplied transport could set to
- * anything. All of that is on the paired `'debug'` line.
- */
- | {
-    type: 'rpc';
-    reason: RpcFailureReason;
-}
-/**
- * Something the SDK does not recognise - usually a host-supplied lambda
- * (`getAccessToken`, an {@link EvmWallet} method) throwing, or a
- * network-level `fetch` failure.
- *
- * `name` is the error's class name and nothing else. The message and the
- * thrown value itself are host-authored, so they are a `'debug'` disclosure:
- * the paired debug line renders them in full.
- */
- | {
-    type: 'generic-error';
-    name: string;
-};
-
-/**
- * The exhaustive chain set: a new {@link EthereumChain} is a compile error
- * here until it is listed, which is what keeps the constructor total.
- */
-declare const ETHEREUM_CHAINS: Record<EthereumChain, true>;
-type EthereumChain = 'ethereum_mainnet' | 'ethereum_sepolia' | 'base_mainnet' | 'base_sepolia';
-/**
- * Validates that a raw backend string names a chain the SDK supports.
- *
- * @throws ValidationError on anything else. Passing an unknown chain through
- * would let downstream EIP-155 lookups blow up far from the response that
- * caused it.
- */
-declare const EthereumChain: (value: string) => EthereumChain;
-/**
- * The exhaustive chain set: a new {@link SolanaChain} is a compile error
- * here until it is listed, which is what keeps the constructor total.
- */
-declare const SOLANA_CHAINS: Record<SolanaChain, true>;
-type SolanaChain = 'solana_mainnet' | 'solana_devnet';
-/**
- * Validates that a raw backend string names a chain the SDK supports.
- *
- * @throws ValidationError on anything else. Passing an unknown chain through
- * would let downstream EIP-155 lookups blow up far from the response that
- * caused it.
- */
-declare const SolanaChain: (value: string) => SolanaChain;
-/**
- * {@link Chain}'s check without the throw, for a mapper over a list that drops
- * the entries it cannot name rather than rejecting the whole list. Frontline's
- * chain registry may carry chains this SDK does not model yet.
- */
-declare const isChain: (value: string) => value is Chain;
-type Chain = EthereumChain | SolanaChain;
-declare const Chain: (value: string) => Chain;
-/**
- * Protocol a wallet binding is scoped to. EVM-only for now: an EVM address
- * binds once per option regardless of which EVM chain proved ownership.
- * Frontline's enum also has `:solana`, but we don't handle Solana bindings yet,
- * so this stays `'ethereum'` until Solana support lands.
- */
-type WalletProtocol = 'ethereum';
-/**
- * EVM addresses keep a `0x${string}` base so they stay assignable to the
- * `0x${string}` shapes that on-chain libraries (viem/wagmi) expect. We only
- * drop the runtime `0x` narrowing: values are trusted at the boundary and
- * branded via the constructor.
- */
-type EvmWalletAddress = Newtype<`0x${string}`, 'EvmWalletAddress'>;
-declare const EvmWalletAddress: (value: string) => EvmWalletAddress;
-type EvmContractAddress = Newtype<`0x${string}`, 'EvmContractAddress'>;
-declare const EvmContractAddress: (value: string) => EvmContractAddress;
-/**
- * What uniquely identifies a token: the chain it is deployed on plus its
- * contract address. Never a symbol, which can collide across issuers.
- */
-type TokenIdentifier = {
-    /** The chain the token contract is deployed on. */
-    chain: EthereumChain;
-    /**
-     * The token's contract address, in any casing — consumers that need the
-     * EIP-55 form (e.g. the token registry routes) checksum it themselves.
-     */
-    address: EvmContractAddress;
-};
-type HexEncodedTransactionData = Newtype<`0x${string}`, 'HexEncodedTransactionData'>;
-declare const HexEncodedTransactionData: (value: string) => HexEncodedTransactionData;
-/**
- * A transaction the backend has already encoded for us — the caller only
- * broadcasts it. Used by the flows that hand a wallet a ready-made `to`/`data`
- * pair (allow-listing a wallet, an Ondo swap) rather than encoding a contract
- * call themselves.
- */
-type Tx = {
-    to: EvmContractAddress;
-    data: HexEncodedTransactionData;
-};
-/**
- * The largest exponent whose power of ten still fits a uint256: 10^77 fits,
- * 10^78 does not.
- *
- * The bound is arithmetic rather than a token standard's. ERC-20 reports
- * `decimals()` as a `uint8`, so 255 is what a contract *can* say, but every
- * {@link AssetDecimals} in this codebase is paired with a {@link Uint256} raw
- * by construction, and scaling by anything past this leaves that pairing
- * unrepresentable. A value between 78 and 255 would therefore pass a
- * standard-faithful check and then break the first multiplication it reached.
- */
-declare const MAX_ASSET_DECIMALS = 77;
-/**
- * How many decimal places one whole token divides into.
- *
- * Validated, unlike its neighbours here — {@link Uint256} is a bare `bigint`
- * with a separate {@link assertUint256} guard, and {@link DecimalString} casts
- * unchecked. The asymmetry is deliberate and follows the value's provenance:
- * an `AssetDecimals` used to come only from literals and the token registry,
- * but backends now publish exponents of their own (`asset_decimals` on an Ondo
- * quote, both scales on a built swap), and those feed `10n ** BigInt(d)`
- * during render. Guarding at construction is what keeps a fractional or
- * unbounded exponent from surfacing as a `RangeError` mid-render — or, at
- * 10^200, as a hung tab — instead of as the failed state the screen has.
- *
- * See docs/ADR-7-VALIDATED-NEWTYPES.md.
- *
- * @throws ValidationError on a non-integer, a negative, or anything above
- * {@link MAX_ASSET_DECIMALS}.
- */
-type AssetDecimals = Newtype<number, 'AssetDecimals'>;
-declare const AssetDecimals: (value: number) => AssetDecimals;
-declare const STABLE_DECIMALS: AssetDecimals;
-/**
- * A non-negative decimal number the backend sent as a string, kept unscaled.
- *
- * Reach for it when a response gives you a number but not the decimals to
- * scale it by, or gives you one it has already applied. Inventing an exponent
- * for either is how a display ends up orders of magnitude out.
- *
- * Contrast {@link BlockchainAmount}, which pairs a raw uint256 with the
- * decimals it is denominated in and so is only constructible when you know
- * both. Arithmetic on a `DecimalString` needs a decimal library we
- * deliberately do not ship.
- */
-type DecimalString = Newtype<string, 'DecimalString'>;
-declare const DecimalString: (value: string) => DecimalString;
-declare const MAX_UINT_256: bigint;
-/**
- * A non-negative integer within uint256 bounds. Kept unbranded (a plain
- * `bigint`) so raw on-chain amounts flow in without ceremony; bounds are
- * enforced where it matters (see {@link combineAmounts}).
- */
-type Uint256 = bigint;
-/**
- * Asserts a computed bigint falls within uint256 bounds. Use at on-chain
- * arithmetic boundaries (bps math, price computation) where the SDK's own
- * arithmetic could underflow below zero or overflow above 2^256-1.
- *
- * Throws {@link InvariantError}, because reaching it means the SDK computed
- * something no chain could represent. **For a value that came off the wire,
- * use {@link parseUint256} instead**: the backend sending an unrepresentable
- * number is a {@link ValidationError}, and the two have different remedies.
- */
-declare const assertUint256: (value: bigint) => Uint256;
-/**
- * {@link assertUint256} at a wire boundary: the same bounds check, reported as
- * a {@link ValidationError} against the named field, because a value out of
- * range here is the backend's, not the SDK's.
- *
- * `label` names the field the way a DTO mapper's other failures do, so a log
- * line says which one - `SwapPreview.pay_input_amount`, not `a number`.
- */
-declare const parseUint256: (value: bigint, label: string) => Uint256;
-type BlockchainAmount = Newtype<{
-    raw: Uint256;
-    decimals: AssetDecimals;
-}, 'BlockchainAmount'>;
-/**
- * Constructs a {@link BlockchainAmount} and exposes arithmetic helpers.
- * TypeScript has no operator overloading, so use `BlockchainAmount.add(a, b)`
- * instead of `+`/`-`/`*`/`/` on the objects directly.
- */
-declare const BlockchainAmount: ((value: {
-    raw: Uint256;
-    decimals: AssetDecimals;
-}) => BlockchainAmount) & {
-    add: (a: BlockchainAmount, b: BlockchainAmount) => BlockchainAmount;
-    sub: (a: BlockchainAmount, b: BlockchainAmount) => BlockchainAmount;
-    mul: typeof multiplyAmounts;
-    div: typeof divideAmounts;
-};
-/**
- * `a * b`, denominated in `a`'s decimals - a price times a quantity, an amount
- * times a rate.
- *
- * The exact inverse of {@link divideAmounts}, and it reads the same way round:
- * the answer stays in `a`'s scale and `b`'s divides back out, so the two
- * compose - `mul(div(a, b), b)` is `a` again, short only what truncation took.
- * That is what makes `price x quantity` land in the currency the price was
- * quoted in rather than at some product of two exponents no token uses.
- *
- * The multiplication happens *before* the division by `10^b.decimals`, so the
- * full precision of both operands survives into the one rounding at the end.
- * Like `div` it truncates towards zero on both signs, which is the safe
- * direction for money: a total is never inflated past what the parts hold.
- *
- * Total - unlike `div`, there is nothing here to reject. The scale it divides
- * by is a power of ten, never zero, and a product is not bounds-checked for
- * the same reason a quotient is not: whether one past uint256 is a corrupt
- * response or an expected magnitude belongs to the caller.
- */
-declare function multiplyAmounts(a: BlockchainAmount, b: BlockchainAmount): BlockchainAmount;
-/**
- * `a / b`, denominated in `a`'s decimals - a price, a ratio, a rate.
- *
- * Unlike {@link combineAmounts}, the two operands may be at different scales,
- * and usually are: dividing dollars by shares is the point of the operation,
- * and the two tokens rarely share an exponent. `b`'s scale divides back out -
- * the numerator is scaled by `10^b.decimals` *before* the division, so nothing
- * is lost to integer truncation early and the quotient lands in `a`'s scale,
- * which is the one the amounts it is rendered beside are in.
- *
- * Truncates towards zero on both signs, which is what BigInt division already
- * does and the safe direction for money: the total a price implies never
- * exceeds, in magnitude, the amount that actually moved.
- *
- * A zero divisor is the only rejection. The quotient is deliberately *not*
- * bounds-checked the way {@link combineAmounts} checks a sum: scaling the
- * numerator carries even legal pairs past uint256 (a maximal amount over a
- * single base unit), and whether that reads as a corrupt response or an
- * expected magnitude is the caller's to judge - see `computeOndoBuyPrice` and
- * `computeOndoSellPrice`, which bounds-check the price they build out of this.
- *
- * @throws MathError when `b` is zero. `add` and `sub` throw a bare `Error`
- * because a scale mismatch is a programming error caught in review; a zero
- * divisor arrives from a server response and is divided by during render, so
- * it is a named failure a screen can catch and map to a failed state.
- */
-declare function divideAmounts(a: BlockchainAmount, b: BlockchainAmount): BlockchainAmount;
-type AssetSymbol = Newtype<string, 'AssetSymbol'>;
-declare const AssetSymbol: (value: string) => AssetSymbol;
-/**
- * A stablecoin symbol is an {@link AssetSymbol} narrowed to the coins we
- * support. It shares the `AssetSymbol` brand so it stays assignable to it.
- */
-type StablecoinSymbol = Newtype<'USDC' | 'USDT', 'AssetSymbol'>;
-declare const StablecoinSymbol: (value: "USDC" | "USDT") => StablecoinSymbol;
-type KnownAssetSymbol = StablecoinSymbol;
-declare const KnownAssetSymbol: (value: "USDC" | "USDT") => StablecoinSymbol;
-type Erc20Asset = {
-    name: string;
-    symbol: AssetSymbol;
-    decimals: AssetDecimals;
-};
-type Bps = Newtype<bigint, 'Bps'>;
-declare const Bps: (value: bigint) => Bps;
-
-type GetTokenAllowanceParams = {
-    tokenAddress: EvmContractAddress;
-    owner: EvmWalletAddress;
-    spender: EvmContractAddress;
-    chain: EthereumChain;
-};
-type GetTokenBalanceParams = {
-    tokenAddress: EvmContractAddress;
-    owner: EvmWalletAddress;
-    chain: EthereumChain;
-};
-
-/**
- * OAuth 2.0 token response (RFC 6749 §5.1).
- * Maps to OpenAPI schema OauthToken.
- */
-type OAuthSessionDto = {
-    access_token: string;
-    expires_in: number;
-    refresh_token?: string;
-};
-
-type ClientCredentialsOAuth = Newtype<OAuthAccessToken, 'ClientCredentialsOAuth'>;
-declare const ClientCredentialsOAuth: (value: OAuthAccessToken) => ClientCredentialsOAuth;
-type OAuthAccessToken = {
-    value: string;
-    expiresAt: Date;
-};
-type OAuthRefreshToken = Newtype<string, 'OAuthRefreshToken'>;
-declare const OAuthRefreshToken: (value: string) => OAuthRefreshToken;
-type OAuthSession = {
-    accessToken: OAuthAccessToken;
-    refreshToken?: OAuthRefreshToken;
-};
-declare const OAuthSession: {
-    fromDto: (dto: OAuthSessionDto) => OAuthSession;
-};
-
-type HttpRequestAttributes = {
-    /**
-     * Correlates the log lines of one logical request. Minted by
-     * {@link HttpClient} on the first attempt and carried onto every retry and
-     * post-renewal re-send by {@link concat}, which is what lets a reader tell
-     * three attempts of one request from three separate requests.
-     */
-    requestId?: RequestId;
-    protected?: boolean;
-    userAgent?: boolean;
-    idempotencyKey?: boolean;
-    /** Zero-based attempt index: 0 = first request, 1 = first retry, etc. */
-    retryAttempt?: number;
-    renewAttempted?: boolean;
-    /**
-     * `false` opts a request out of `requestRetryMiddleware`. For exchanges
-     * that must never be replayed: a refresh token is single-use, so re-sending
-     * one whose first attempt reached the server presents a token that has
-     * already been rotated away.
-     */
-    retryable?: boolean;
-    /**
-     * The user access token `attachSessionMiddleware` put on this request, so
-     * that a 401 can say *which* token was refused. Absent when the request
-     * went out with no user token.
-     */
-    sentWith?: OAuthAccessToken;
-    clientCredentials?: ClientCredentialsOAuth;
-};
-
-/**
- * The value types a query-string parameter may take.
- *
- * Declared here rather than beside the HTTP client because domain models build
- * query parameters too: `ParticipationsPaginationParams.toQueryParams` returns
- * a `Record<string, QueryParamValue>`, and a domain model must not import
- * `@/universal/api/**`.
- */
-type QueryParamValue = string | number | boolean | null | undefined;
-type QueryParamValues = QueryParamValue | QueryParamValue[];
-
-type HttpRequest<TBody = unknown> = {
-    method: 'GET';
-    url: string;
-    queryParams?: Record<string, QueryParamValues>;
-    headers?: Record<string, string>;
-    attributes?: HttpRequestAttributes;
-    redirect?: RequestRedirect;
-} | {
-    method: 'POST';
-    url: string;
-    queryParams?: Record<string, QueryParamValues>;
-    headers?: Record<string, string>;
-    body: TBody;
-    attributes?: HttpRequestAttributes;
-    redirect?: RequestRedirect;
-} | {
-    method: 'DELETE';
-    url: string;
-    queryParams?: Record<string, QueryParamValues>;
-    headers?: Record<string, string>;
-    attributes?: HttpRequestAttributes;
-    redirect?: RequestRedirect;
-};
-type HttpResponse<TBody = unknown> = {
-    status: number;
-    headers?: Record<string, string>;
-    body: TBody | null;
-    /**
-     * The id of the request that produced this response, stamped by
-     * {@link HttpClient} so that whoever turns a non-2xx into an
-     * {@link HttpError} can carry it without threading the request alongside.
-     * Absent when the response did not come from an `HttpClient`.
-     */
-    requestId?: RequestId;
-};
-declare class HttpError<TBody = unknown> extends Error {
-    readonly response: HttpResponse<TBody>;
-    constructor(response: HttpResponse<TBody>);
-    /**
-     * Correlates this failure with the `[HTTP]` log lines for the same request,
-     * which carry the method, the URL, the duration and every retry. `null` when
-     * the response did not come from an {@link HttpClient}.
-     *
-     * Worth quoting in a bug report: it is what makes a log excerpt readable.
-     */
-    get requestId(): RequestId | null;
-}
-/**
- * The machine-readable `code` frontline attaches to an error, or `null` for
- * anything else - a non-HTTP failure, or an error body that carries only a
- * message.
- *
- * Frontline answers a failure with `{ type, message, code?, errors?,
- * event_id? }`, and `code` is the only part of it meant to be branched on:
- * `message` is prose that may be reworded, and `type` distinguishes
- * `invalid_request_error` from `api_error` without saying which one.
- *
- * Reach for this only where a code has a distinct remedy the user can act on.
- * Mapping the whole vocabulary would couple the SDK to strings frontline does
- * not version; falling back to a generic failure is the right default.
- */
-declare function apiErrorCode(error: unknown): string | null;
-
-/**
- * Structural interface satisfied by both {@link AuthenticatedApiClient} and
- * {@link ApiClient}. Used by the shared frontline API functions so they can
- * be called from either the client or server without any browser dependencies.
- */
-interface Sender {
-    send<T>(request: HttpRequest): Promise<T>;
-}
-
-/**
- * Where the SDK sends its on-chain reads, per chain.
- *
- * Leave it undefined and reads go through CoinList's authenticated JSON-RPC
- * proxy (`POST /v1/chains/{chain}/rpc`), which needs no setup but does need a
- * logged-in user - the proxy is OAuth-gated, so a read on a chain the SDK is
- * proxying fails with its `401`, surfaced as the viem error wrapping it. A
- * chain you name here is read straight from your own node instead, and needs
- * no CoinList session at all.
- *
- * Each entry is either:
- *
- * - an RPC URL, which the SDK wraps in viem's `http()` transport, or
- * - a viem {@link Transport} used as it stands - `fallback([...])`,
- *   `webSocket()`, or your app's own.
- *
- * Chains you leave out fall back to the proxy individually, so overriding
- * mainnet does not opt Sepolia out. The SDK always constructs the viem
- * `PublicClient` itself, so the chain definition, batching and retry policy
- * stay the SDK's regardless of the transport you supply.
- *
- * @example
- * ```ts
- * createCoinListClient({
- *   clientId,
- *   redirectUri,
- *   rpc: {
- *     ethereum_mainnet: 'https://eth-mainnet.g.alchemy.com/v2/KEY',
- *     ethereum_sepolia: fallback([http(primary), http(backup)]),
- *     // base_* unset -> proxied through CoinList
- *   },
- * });
- * ```
- */
-type RpcConfig = Partial<Record<EthereumChain, string | Transport>>;
-interface Config {
-    /** OAuth2 public identifier. */
-    readonly clientId: ClientId;
-    /**
-     * OAuth2 redirect URI. Recommended to point to a frontend page where
-     * {@link CoinListClient#completeOauth} can be called to complete the PKCE
-     * flow on the client side.
-     */
-    readonly redirectUri: RedirectUri;
-    /**
-     * Recommended to leave undefined. Used to change the CoinList environment;
-     * default is production.
-     */
-    readonly baseUrl?: string;
-    /**
-     * Recommended to leave undefined. Overrides the base URL of the public
-     * token registry backing `coinlist.tokens`; default is the production
-     * registry.
-     */
-    readonly tokensBaseUrl?: string;
-    /**
-     * Where the SDK reports what it is doing. **Omit it and the SDK logs nothing
-     * at all** - no `console` fallback, at any level, on any codepath. Supply
-     * one and every request, every classified failure and every hook state
-     * transition is reported at the level your logger asks for.
-     *
-     * Absent, the SDK says nothing at all - there is no fallback to `console`,
-     * at any level, on any codepath.
-     *
-     * **Running the SDK's logging in production is not advised.** The safest
-     * posture is to leave this undefined outside development, staging and
-     * incident reproduction: a seam that emits nothing cannot disclose anything,
-     * and that property does not depend on the SDK continuing to get redaction
-     * right.
-     *
-     * If you do run one there, run it at `'info'` or above and know what that
-     * does and does not buy you. Those levels are **redacted by construction**:
-     * they carry only SDK-authored classification and server-authored
-     * identifiers, and the type system holds that line rather than a convention -
-     * an event at those levels accepts scalar fields only, so a body, a DTO or
-     * an operation's parameters cannot be put on one. What the SDK does **not**
-     * give you is a warranty that the result is safe for your environment. The
-     * mechanism is checkable and stated; the conclusion depends on your sink,
-     * your retention and your threat model, and it is yours to draw.
-     *
-     * **`'debug'` is not.** It reports request and response bodies, full URLs,
-     * headers and operation parameters verbatim - bearer tokens, KYC answers,
-     * tax-document fields, wallet signatures - and **the SDK does not redact**.
-     * Run it on a developer's machine, in tests, and in beta or staging
-     * environments where the data flowing through is not real customer data.
-     * The shipped implementations make that structural: built with
-     * `isDev: false`, `'debug'` does not typecheck. Either way, filtering,
-     * redaction and retention at your sink are yours, not the SDK's.
-     *
-     * Every method you implement here **must be total**: the SDK calls them on
-     * the codepath of the work they report and does not catch them, so a logger
-     * that throws fails the operation it was describing.
-     *
-     * See {@link Logger} for the full contract, and {@link pinoClientLogger} or
-     * {@link pinoServerLogger} for a ready-made implementation over pino.
-     */
-    readonly logger?: Logger;
-    /**
-     * Where on-chain reads go. Omit it and they are proxied through CoinList.
-     * See {@link RpcConfig}.
-     */
-    readonly rpc?: RpcConfig;
-    /**
-     * Called when the SDK has **confirmed** that the user's CoinList session is
-     * gone - its refresh token expired or was revoked - so you can clear your
-     * own state and show a sign-in entry point.
-     *
-     * Confirmed, because the backend answers "rotated a moment ago by a
-     * concurrent request" and "dead" identically. A single rejection is only a
-     * suspicion: the SDK acts on it only once the same session is rejected again
-     * after a settle window, so a lost refresh race never signs a user out.
-     *
-     * Each environment reports what it confirmed itself, so it fires in the
-     * one that drove the confirmation:
-     *
-     * - **`CoinListClient`**: fires when the SDK moves from `'logged-in'` to
-     *   `'logged-out'` because your `getAccessToken` answered `null` (or the
-     *   very token the API just refused) twice, a second apart.
-     * - **`CoinListServer`**: fires when the same process sees a refresh token
-     *   rejected twice, 5 to 60 seconds apart, or an expired session that
-     *   carries no refresh token. The SDK clears the session from your
-     *   `SessionStore` just before. The browser's confirmation, through your
-     *   `getAccessToken` endpoint, comes a second after the first rejection, so
-     *   it does not reach this verdict: when the browser drives renewal, expect
-     *   the `CoinListClient` callback, and this one only if a later request
-     *   presents the dead session 5 to 60 seconds on.
-     *
-     * It never fires on `auth.logout()`, on a 5xx, a timeout or a network
-     * failure - those mean the SDK could not find out, not that the session
-     * ended. Per environment it fires at most once per session, within a
-     * 60-second memory: the server remembers a verdict for 60 seconds per
-     * process (per JavaScript module instance, so Next.js middleware and route
-     * handlers count separately). The same dead session presented again after
-     * that, or to another instance, can be reported again, so make your handler
-     * idempotent.
-     *
-     * It is called on the next microtask and not awaited. A rejection is
-     * logged and dropped, so it cannot fail or delay the request that
-     * discovered the expiry. A synchronous handler is written `async () => {}`.
-     */
-    readonly onSessionExpired?: () => Promise<void>;
-}
-
-/**
- * Resolves a chain to the viem `PublicClient` the SDK reads it through.
- *
- * One function rather than a client per read, because the client is where the
- * batching lives: viem's multicall scheduler is keyed on the client's `uid`,
- * so two reads only ever share an `eth_call` if they share a client. Hence the
- * memoisation - it is correctness for batching, not a performance tweak.
- */
-type PublicClients = (chain: EthereumChain) => PublicClient;
-
-interface UniversalNamespaceContext {
-    readonly api: Sender;
-    /**
-     * The viem `PublicClient` for a chain, over whichever transport that chain
-     * resolved to - the host's own node, or CoinList's proxy.
-     *
-     * A factory rather than a client, because a namespace serves every chain and
-     * only the call knows which. Built once per client instance so that
-     * concurrent reads share a batch; see `publicClients`.
-     */
-    readonly rpc: PublicClients;
-    /**
-     * The host's logger, or `null` when they supplied none.
-     *
-     * Deliberately the raw port rather than a pre-scoped {@link InternalLogger}:
-     * one context serves every namespace, and each namespace owns its own scope.
-     * A namespace turns it into something usable in its constructor, with
-     * `internalLogger(ctx.logger, 'OFFERS')`.
-     */
-    readonly logger: Logger | null;
-    ensureUserAuthenticated(): Promise<void>;
-}
-
-/**
- * Generic ERC-20 reads shared across on-chain flows (swap, token sale): the
- * allowance an owner has granted a spender, and the raw token balance an owner
- * holds. These are plain token reads, not tied to any single product flow.
- *
- * Read from the chain rather than from a CoinList endpoint. By default that
- * goes through CoinList's authenticated JSON-RPC proxy, so a logged-out caller
- * gets the proxy's `401` - surfaced as a viem error wrapping the SDK's
- * `HttpError`, not as `NotAuthenticatedError`, since viem re-wraps whatever a
- * `Transport` throws. Point `Config.rpc` at your own node for this chain and no
- * CoinList session is involved at all. See {@link RpcConfig}.
- */
-interface Erc20Namespace {
-    /**
-     * Reads the ERC-20 allowance an `owner` has granted a `spender`, as a raw
-     * on-chain integer.
-     */
-    getAllowance(params: GetTokenAllowanceParams): Promise<Uint256>;
-    /**
-     * Reads the raw ERC-20 balance an `owner` holds of a token.
-     */
-    getBalance(params: GetTokenBalanceParams): Promise<Uint256>;
-}
-declare class Erc20NamespaceImpl implements Erc20Namespace {
-    private readonly ctx;
-    private readonly log;
-    constructor(ctx: UniversalNamespaceContext);
-    getAllowance(params: GetTokenAllowanceParams): Promise<Uint256>;
-    getBalance(params: GetTokenBalanceParams): Promise<Uint256>;
-}
-
-type GetCentrifugeVaultStatusParams = {
-    /** Share token symbol of the vault, e.g. `deJTRSY`. */
-    symbol: AssetSymbol;
-    /**
-     * The chain whose proxy answers. Only chains this offer has a proxy on
-     * are accepted; the offer's `vault_contracts` lists them.
-     */
-    chain: EthereumChain;
-};
-type GetCentrifugeVaultQuoteParams = GetCentrifugeVaultStatusParams & {
-    /**
-     * Amount to price, in the base units of the funding token. Must be greater
-     * than zero. No fee is deducted; this product charges none.
-     *
-     * Sized by `amount` alone: the quote is a free read of one spend, not a
-     * dollar figure converted later.
-     */
-    amount: BlockchainAmount;
-};
-/**
- * One wallet on one vault: what every position read and every claim is keyed
- * by. There is no order id - a wallet has one pooled position per vault per
- * direction.
- */
-type CentrifugeWalletParams = GetCentrifugeVaultStatusParams & {
-    /**
-     * The wallet whose position is read, or claimed for. A claim must then be
-     * broadcast from this same wallet: the proxy credits the sender.
-     */
-    walletAddress: EvmWalletAddress;
-};
-/**
- * What `POST /v1/centrifuge/vault/invest` is asked for: the wallet that will
- * broadcast the request and fund it, plus the deposit.
- *
- * Built once, when the user confirms an amount. Broadcasting the result places
- * a request; it does not buy shares.
- */
-type BuildCentrifugeVaultBuyParams = CentrifugeWalletParams & {
-    /** How much of the funding token to deposit, in its base units. */
-    amount: BlockchainAmount;
-};
-
-/**
- * The logging surface SDK code uses. Never exported to hosts: they implement
- * {@link Logger}, which is deliberately smaller.
- */
-type InternalLogger = {
-    /**
-     * A logger narrowed by one more {@link LogBinding}, which every line it
-     * emits carries as its own field.
-     */
-    child(binding: LogBinding): InternalLogger;
-    /**
-     * The unredacted level. Request and response bodies, full URLs, headers,
-     * operation params and raw thrown errors belong here and **only** here.
-     */
-    debug(event: () => InternalDebugEvent): void;
-    info(event: () => InternalSafeEvent): void;
-    warn(event: () => InternalSafeEvent): void;
-    /**
-     * Reports a failure whose cause is already known, or has none. Prefer
-     * {@link failure}, which classifies a thrown error for you.
-     */
-    error(event: () => InternalSafeEvent): void;
-    /**
-     * Reports a thrown error, classifying it into a {@link LogCause}. Prefer
-     * this over `error` at a `catch`: classification only happens when the level
-     * admits it.
-     *
-     * The `error` line names the error's class but never its message, since an
-     * error the SDK did not author may say anything at all. The verbatim
-     * rendering goes onto a paired `debug` line instead.
-     *
-     * For a failure the SDK recovers from, use {@link warning} instead. An
-     * `error` line a host cannot act on is worse than no line at all: it trains
-     * them to ignore the ones that matter.
-     */
-    failure(event: () => InternalSafeEvent, error: unknown): void;
-    /**
-     * {@link failure} for trouble that did not break anything: a poll tick that
-     * failed while the last value still stands, a retried request.
-     *
-     * Carries the classified {@link LogCause} exactly as `failure` does. The two
-     * differ in level and in nothing else, because what separates them is
-     * whether anything actually broke - not how much is known about it.
-     */
-    warning(event: () => InternalSafeEvent, error: unknown): void;
-    /**
-     * Runs one namespace operation with logging around it: the call and its
-     * params at `debug`, and any throw at `error` with the cause classified.
-     * Every line carries `op` as a binding.
-     *
-     * **The params never reach the `error` line.** They routinely hold the
-     * things this SDK must not put in front of a production error tracker - an
-     * app bearer token, a document's signing fields, a wallet signature - and
-     * the `debug` line plus the request id is how you get them back. The type
-     * says so: `params` is `unknown`, which is not a {@link SafeFields} value.
-     *
-     * Always rethrows. Logging observes behaviour, it never changes it.
-     */
-    wrap<T>(op: string, params: unknown, run: () => Promise<T>): Promise<T>;
-};
-/**
- * What a call site hands to `info`, `warn`, `error`, `failure` or `warning` -
- * a {@link SafeEvent} minus the scope and bindings the logger stamps itself.
- */
-type InternalSafeEvent = {
-    /** A **constant** string literal. Every varying value belongs in `fields`. */
-    readonly msg: string;
-    readonly fields?: SafeFields;
-    readonly cause?: LogCause;
-};
-/** What a call site hands to `debug`. Its fields accept anything. */
-type InternalDebugEvent = {
-    /** A **constant** string literal. Every varying value belongs in `fields`. */
-    readonly msg: string;
-    readonly fields?: UnredactedFields;
-};
-
-/**
- * Wire shapes for frontline's `/v1/centrifuge/vault/*` endpoints, as published
- * in frontline's OpenAPI schema (ENG-1936). Every uint256 crosses as a decimal
- * string, every price as a decimal string, every timestamp as ISO 8601.
- *
- * **A vault deposit does not settle in the transaction that places it.** The
- * fund fulfils requests on its own epoch, in whole or in part, at a price set
- * then, and the user claims the resulting shares in a second transaction. So
- * every share figure before a fill is an estimate.
- *
- * The three GETs are free to poll. The two POSTs return calldata to broadcast:
- * `invest` is signed for one wallet and called once on confirmation, `claim`
- * collects everything claimable and carries no amount.
- */
-/**
- * Why a deposit cannot be placed right now. A closed set, so a client can
- * branch on every value. `vault_unlinked` is terminal for the offer's proxy on
- * that chain; the rest clear on their own or by hand.
- *
- * `below_minimum` is the one reason that depends on an amount, so only a quote
- * can report it - see {@link CentrifugeVaultReasonDto}.
- */
-type CentrifugeOrderReasonDto = 'vault_unlinked' | 'vault_halted' | 'proxy_not_permissioned' | 'price_unavailable' | 'below_minimum';
-/** What a vault status can report: every reason but the amount-dependent one. */
-type CentrifugeVaultReasonDto = Exclude<CentrifugeOrderReasonDto, 'below_minimum'>;
-/**
- * Where a wallet stands on a vault, derived from its amounts rather than
- * stored. Not a lifecycle: a new request moves any of these back to `pending`
- * while earlier shares stay claimed.
- */
-type CentrifugePositionStatusDto = 'none' | 'pending' | 'partially_filled' | 'filled' | 'claimed';
-/** `GET /v1/centrifuge/vault/quote?symbol&chain&amount`. Indicative only. */
-type CentrifugeVaultQuoteDto = {
-    object: 'centrifuge_vault_quote';
-    /** The vault's share token symbol, e.g. `deJTRSY`. */
-    symbol: string;
-    chain: string;
-    /** The amount priced, echoed back, in `spend_input_decimals`. No fee. */
-    spend_input_amount: string;
-    spend_input_decimals: number;
-    /** An estimate, not a floor: the fill can price either side of it. */
-    estimated_shares: string;
-    share_decimals: number;
-    /** Funding token per whole share. Null when the vault has no price. */
-    indicative_price: string | null;
-    /** In `spend_input_decimals`. Null when the offer sets no minimum. */
-    minimum_input_amount: string | null;
-    can_order: boolean;
-    /** Empty exactly when `can_order` is true. */
-    reasons: CentrifugeOrderReasonDto[];
-};
-/**
- * `GET /v1/centrifuge/vault/status?symbol&chain`. The vault's own state, read
- * from the chain on every call; the gate to poll, because Centrifuge announces
- * none of these changes.
- */
-type CentrifugeVaultStatusDto = {
-    object: 'centrifuge_vault_status';
-    symbol: string;
-    chain: string;
-    /** Centrifuge's vault, read from the proxy. Fixed for the proxy's life. */
-    vault_address: string;
-    /** False is terminal for this proxy: a replacement has to be deployed. */
-    linked: boolean;
-    /** Whether the proxy is on the share token's memberlist. */
-    permissioned: boolean;
-    membership_valid_until: string | null;
-    /** Set by the proxy after a force-cancel; cleared only by hand. */
-    halted: boolean;
-    price_updated_at: string | null;
-    can_order: boolean;
-    reasons: CentrifugeVaultReasonDto[];
-    as_of: string;
-};
-/**
- * What both POSTs return: calldata for the wallet to broadcast verbatim.
- * Unlike Ondo's, `expires_at` is nullable - a claim carries no signature, so
- * it is always null there.
- */
-type CentrifugeBroadcastDto = {
-    action: 'broadcast_transaction';
-    /** The offer's proxy on the chain. Lower case: compare case-insensitively. */
-    to: string;
-    data: string;
-    expires_at: string | null;
-};
-/**
- * `POST /v1/centrifuge/vault/invest` with `{ symbol, chain, wallet_address,
- * amount }`. Broadcasting it places a request in the vault's queue and buys
- * nothing yet.
- */
-type CentrifugeVaultBuyDto = CentrifugeBroadcastDto & {
-    /** Exactly what the approval has to cover: no fee comes off it. */
-    spend_input_amount: string;
-    spend_input_decimals: number;
-    /** Not a quantity purchased: the fill prices later. */
-    estimated_shares: string;
-    share_decimals: number;
-};
-/**
- * `GET /v1/centrifuge/vault/position?symbol&chain&wallet_address`. The six
- * amounts are independent: a wallet can hold a pending request, a claimable
- * balance and claimed shares at once. There is no per-fulfilment breakdown;
- * settlement pools every fulfilment into one rate.
- */
-type CentrifugeVaultPositionDto = {
-    object: 'centrifuge_vault_position';
-    symbol: string;
-    chain: string;
-    wallet_address: string;
-    status: CentrifugePositionStatusDto;
-    /** Funding token ever requested, in `asset_decimals`. */
-    requested: string;
-    /** Of that, still queued. */
-    pending: string;
-    /** Of that, fulfilled. */
-    filled_assets: string;
-    /** Shares the fulfilments earned, in `share_decimals`. Held by the proxy until claimed. */
-    earned_shares: string;
-    claimed_shares: string;
-    /** Non-zero means the claim endpoint will return calldata. */
-    claimable_shares: string;
-    /** Read from the share token; can exceed `claimed_shares`. */
-    share_balance: string;
-    asset_decimals: number;
-    share_decimals: number;
-    /** Null before the first claim. */
-    average_price: string | null;
-    /** Centrifuge froze the wallet on the share token; blocks claiming. */
-    frozen: boolean;
-    as_of: string;
-};
-/**
- * `POST /v1/centrifuge/vault/claim` with `{ symbol, chain, wallet_address }`.
- * The wallet named must be the one that broadcasts: the proxy credits the
- * sender.
- */
-type CentrifugeVaultClaimDto = CentrifugeBroadcastDto & {
-    /** A floor: a fill landing before the broadcast raises it. */
-    claimable_shares: string;
-    share_decimals: number;
-};
-/**
- * `GET /v1/centrifuge/vault/redeem-position?symbol&chain&wallet_address`. The
- * redeem side of {@link CentrifugeVaultPositionDto}, with the units swapped:
- * what is queued is shares, and what a fill makes claimable is the funding
- * token.
- *
- * TODO(frontline, ENG-1909): guessed. Frontline publishes no redeem endpoint
- * yet; this mirrors the invest position field for field so the SDK can be
- * built against it. Replace with the published schema when it lands.
- */
-type CentrifugeVaultRedeemPositionDto = {
-    object: 'centrifuge_vault_redeem_position';
-    symbol: string;
-    chain: string;
-    wallet_address: string;
-    status: CentrifugePositionStatusDto;
-    /** Shares still queued for redemption, in `share_decimals`. */
-    pending: string;
-    /**
-     * Funding token a claim would pay out now, in `asset_decimals`. An
-     * estimate: the vault holds the claimable amount in shares and prices it
-     * at the claim.
-     */
-    claimable_assets: string;
-    asset_decimals: number;
-    share_decimals: number;
-    /** Centrifuge froze the wallet on the share token. */
-    frozen: boolean;
-    as_of: string;
-};
-/**
- * `POST /v1/centrifuge/vault/claim-proceeds` with `{ symbol, chain,
- * wallet_address }`. Collects everything claimable on the redeem side; the
- * proxy pays the sender.
- *
- * TODO(frontline, ENG-1909): guessed, as {@link CentrifugeVaultRedeemPositionDto}.
- */
-type CentrifugeVaultClaimProceedsDto = CentrifugeBroadcastDto & {
-    /** An estimate read when the calldata was built, in `asset_decimals`. */
-    claimable_assets: string;
-    asset_decimals: number;
-};
-
-/**
- * Which leg of a vault trade: `invest` turns the funding token into shares,
- * `redeem` turns shares back into the funding token. Each wallet holds one
- * pooled position per vault per direction, and a claim settles one of them.
- */
-type CentrifugeClaimDirection = 'invest' | 'redeem';
-/**
- * Why a deposit cannot be placed on a vault right now. Kept verbatim from the
- * wire: frontline publishes it as a closed set for clients to branch on.
- */
-type CentrifugeOrderReason = CentrifugeOrderReasonDto;
-/** The reasons a vault status can report - all but `below_minimum`. */
-type CentrifugeVaultReason = CentrifugeVaultReasonDto;
-/**
- * Where a wallet stands on a vault. Not a lifecycle - see
- * {@link CentrifugeVaultPosition.status}.
- */
-type CentrifugePositionStatus = CentrifugePositionStatusDto;
-/**
- * Whether a deposit can be placed, as one union rather than the wire's
- * `can_order` beside `reasons`: a blocked answer always says why, and an
- * orderable one has nothing to say. The wire pair can contradict itself; this
- * cannot, because `fromDto` refuses the payloads that do.
- */
-type CentrifugeOrderability<R extends CentrifugeOrderReason> = {
-    type: 'orderable';
-} | {
-    type: 'blocked';
-    reasons: [R, ...R[]];
-};
-/**
- * What a deposit of a given size would buy, and whether it can be placed.
- *
- * **Indicative only.** The price is read from the vault now and the fund
- * prices the fulfilment on its own epoch, so neither {@link indicativePrice}
- * nor {@link estimatedShares} is a commitment. Free to poll while the user
- * sizes a deposit.
- */
-type CentrifugeVaultQuote = {
-    chain: EthereumChain;
-    /** The vault's share token symbol, e.g. `deJTRSY`. */
-    symbol: AssetSymbol;
-    /** The amount priced, in the funding token's decimals. No fee is taken. */
-    spendInputAmount: BlockchainAmount;
-    /** Shares at the indicative price, in the share token's decimals. */
-    estimatedShares: BlockchainAmount;
-    /** Funding token per whole share. Null when the vault publishes no price. */
-    indicativePrice: DecimalString | null;
-    /** Null when the offer sets no minimum. Same decimals as the spend. */
-    minimumInputAmount: BlockchainAmount | null;
-    orderability: CentrifugeOrderability<CentrifugeOrderReason>;
-};
-declare const CentrifugeVaultQuote: {
-    fromDto: (dto: CentrifugeVaultQuoteDto) => CentrifugeVaultQuote;
-};
-/**
- * A vault's own state, independent of any wallet or amount: the gate to poll.
- * Centrifuge announces none of these changes, and an unlinked vault leaves the
- * offer's proxy permanently dead, so a cached answer goes wrong silently.
- */
-type CentrifugeVaultStatus = {
-    chain: EthereumChain;
-    symbol: AssetSymbol;
-    /** Centrifuge's vault behind the proxy. Fixed for the proxy's life. */
-    vaultAddress: EvmContractAddress;
-    /**
-     * Whether Centrifuge still links the vault to its pool. False is terminal
-     * for this proxy: no request or claim succeeds until a new one is deployed.
-     */
-    linked: boolean;
-    /**
-     * Whether the proxy is on the share token's memberlist. It holds shares for
-     * every wallet, so one expired entry stops the whole offer.
-     */
-    permissioned: boolean;
-    /** Watch it: {@link permissioned} goes false the moment it passes. */
-    membershipValidUntil: Date | null;
-    /** The proxy halted itself after a force-cancel; cleared only by hand. */
-    halted: boolean;
-    /** A stale value is the signal that a quote's price is old. */
-    priceUpdatedAt: Date | null;
-    orderability: CentrifugeOrderability<CentrifugeVaultReason>;
-    /** When the chain was read: how old everything above is. */
-    asOf: Date;
-};
-declare const CentrifugeVaultStatus: {
-    fromDto: (dto: CentrifugeVaultStatusDto) => CentrifugeVaultStatus;
-};
-/**
- * What both vault transactions share: calldata to broadcast verbatim, and the
- * deadline on it.
- */
-type CentrifugeVaultTransactionCore = {
-    /** The `to` is the offer's proxy: the spender the deposit was approved to. */
-    tx: Tx;
-    /**
-     * When the calldata stops being accepted, or null when it carries no
-     * deadline - always the case for a claim, which nobody signs.
-     */
-    expiresAt: Date | null;
-};
-/**
- * A signed deposit request, ready to broadcast.
- *
- * **Broadcasting it buys nothing yet.** It places a request in the vault's
- * queue; the fund fulfils it later at a price set then, and the user comes
- * back to claim. {@link estimatedShares} is therefore never a quantity
- * purchased. Single-use: built once on confirmation, never on a timer.
- */
-type CentrifugeVaultBuyTransaction = CentrifugeVaultTransactionCore & {
-    /** Exactly what the approval has to cover: no fee comes off it. */
-    spendInputAmount: BlockchainAmount;
-    /** At the price read when the calldata was built. An estimate, not a floor. */
-    estimatedShares: BlockchainAmount;
-};
-declare const CentrifugeVaultBuyTransaction: {
-    fromDto: (dto: CentrifugeVaultBuyDto) => CentrifugeVaultBuyTransaction;
-};
-/**
- * The claim that moves fulfilled shares from the proxy to the wallet: the
- * second transaction every vault purchase needs. The wallet that broadcasts it
- * is the one credited.
- */
-type CentrifugeVaultClaimTransaction = CentrifugeVaultTransactionCore & {
-    /**
-     * Read when the calldata was built. A floor: a fill landing before the
-     * broadcast raises it, and the claim still collects everything.
-     */
-    claimableShares: BlockchainAmount;
-};
-declare const CentrifugeVaultClaimTransaction: {
-    fromDto: (dto: CentrifugeVaultClaimDto) => CentrifugeVaultClaimTransaction;
-};
-/**
- * One wallet's standing on one vault: what it put in, what has settled, and
- * what it can claim. The endpoint a returning user lands on, and the one that
- * says whether to offer the claim.
- *
- * The amounts are independent of each other: each piece of a request settles
- * and is claimed on its own, so a wallet can be pending, claimable and claimed
- * at once. There is no per-fulfilment breakdown; settlement pools every
- * fulfilment into one {@link averagePrice}.
- */
-type CentrifugeVaultPosition = {
-    chain: EthereumChain;
-    symbol: AssetSymbol;
-    walletAddress: EvmWalletAddress;
-    /**
-     * Derived by frontline from the amounts. Not a lifecycle: a new request
-     * moves it back to `pending` while earlier shares stay claimed.
-     */
-    status: CentrifugePositionStatus;
-    /** Funding token ever requested. */
-    requested: BlockchainAmount;
-    /** Of {@link requested}, what is still queued. */
-    pending: BlockchainAmount;
-    /** Of {@link requested}, what has been fulfilled. */
-    filledAssets: BlockchainAmount;
-    /** Shares the fulfilments earned. Held by the proxy until claimed. */
-    earnedShares: BlockchainAmount;
-    claimedShares: BlockchainAmount;
-    /** Non-zero means a claim will return calldata. */
-    claimableShares: BlockchainAmount;
-    /**
-     * What the wallet holds on the share token. Can exceed
-     * {@link claimedShares}: shares acquired any other way count here.
-     */
-    shareBalance: BlockchainAmount;
-    /** Pooled rate over everything claimed. Null before the first claim. */
-    averagePrice: DecimalString | null;
-    /** Centrifuge froze this wallet on the share token. Blocks claiming. */
-    frozen: boolean;
-    asOf: Date;
-};
-declare const CentrifugeVaultPosition: {
-    fromDto: (dto: CentrifugeVaultPositionDto) => CentrifugeVaultPosition;
-};
-/**
- * One wallet's standing on the redeem side of a vault: shares queued to sell,
- * and the funding token a fill has made claimable. The mirror of
- * {@link CentrifugeVaultPosition}, and as independent of it: a wallet can be
- * investing and redeeming on the same vault at once.
- *
- * TODO(frontline, ENG-1909): built against a guessed wire shape - see
- * `CentrifugeVaultRedeemPositionDto`.
- */
-type CentrifugeVaultRedeemPosition = {
-    chain: EthereumChain;
-    symbol: AssetSymbol;
-    walletAddress: EvmWalletAddress;
-    status: CentrifugePositionStatus;
-    /** Shares still queued for redemption. */
-    pending: BlockchainAmount;
-    /**
-     * Funding token a claim would pay out now. An estimate: the vault prices the
-     * claimable shares at the claim. Non-zero means a claim returns calldata.
-     */
-    claimableAssets: BlockchainAmount;
-    /** Centrifuge froze this wallet on the share token. Blocks claiming. */
-    frozen: boolean;
-    asOf: Date;
-};
-declare const CentrifugeVaultRedeemPosition: {
-    fromDto: (dto: CentrifugeVaultRedeemPositionDto) => CentrifugeVaultRedeemPosition;
-};
-/**
- * One wallet's position on one leg of a vault trade, tagged with the leg. The
- * two legs are read from two endpoints and settle in opposite units - the
- * invest leg queues the funding token and pays out shares, the redeem leg the
- * reverse - so the tag is what says which unit each figure is in.
- */
-type CentrifugeVaultLeg = {
-    direction: 'invest';
-    position: CentrifugeVaultPosition;
-} | {
-    direction: 'redeem';
-    position: CentrifugeVaultRedeemPosition;
-};
-declare const CentrifugeVaultLeg: {
-    /**
-     * What a claim on the leg would collect: shares for `invest`, the funding
-     * token for `redeem`.
-     */
-    claimable: (leg: CentrifugeVaultLeg) => BlockchainAmount;
-    /** Whether the leg has anything queued or anything ready to claim. */
-    isActive: (leg: CentrifugeVaultLeg) => boolean;
-};
-/**
- * One wallet's position on one leg of one vault: what a claim targets. A
- * wallet holds at most one per direction per chain, so the three together
- * name it.
- */
-type CentrifugeVaultLegId = Newtype<string, 'CentrifugeVaultLegId'>;
-declare const CentrifugeVaultLegId: {
-    /** Addresses compare case-insensitively: frontline echoes them lower case. */
-    of: (leg: CentrifugeVaultLeg) => CentrifugeVaultLegId;
-};
-/**
- * The claim that pays a filled redemption out in the funding token: the
- * second transaction every vault sale needs. The wallet that broadcasts it is
- * the one paid.
- *
- * TODO(frontline, ENG-1909): built against a guessed wire shape - see
- * `CentrifugeVaultClaimProceedsDto`.
- */
-type CentrifugeVaultClaimProceedsTransaction = CentrifugeVaultTransactionCore & {
-    /** An estimate read when the calldata was built; the claim pays it all. */
-    claimableAssets: BlockchainAmount;
-};
-declare const CentrifugeVaultClaimProceedsTransaction: {
-    fromDto: (dto: CentrifugeVaultClaimProceedsDto) => CentrifugeVaultClaimProceedsTransaction;
-};
-
-/**
- * Centrifuge vault reads and claims: an indicative quote, the vault-wide
- * ordering gate, each wallet's position per direction, and the calldata that
- * claims a filled request.
- *
- * The reads are free to poll - none spends an attestation, so a client may
- * call them while the user sizes a deposit or waits on a fill. The quote has
- * no expiry: it is indicative, the fund prices fulfilment later, and a
- * countdown would imply a commitment the API does not make.
- *
- * A vault trade settles in two legs: a request the fund fills on its own
- * schedule, then a claim. There is no order id - each wallet has one pooled
- * position per vault per direction - so the claims take a wallet, not an
- * order, and collect everything claimable.
- *
- * The calldata builders are the exception: {@link CentrifugeNamespace.buildBuyTransaction}
- * and the claims are each called once, when the user confirms, and never on a
- * timer. Broadcasting the buy calldata places a request. It does not buy
- * shares.
- *
- * Every method requires `AuthState === 'logged-in'` and throws
- * {@link NotAuthenticatedError} otherwise.
- */
-interface CentrifugeNamespace {
-    getQuote(params: GetCentrifugeVaultQuoteParams): Promise<CentrifugeVaultQuote>;
-    getVaultStatus(params: GetCentrifugeVaultStatusParams): Promise<CentrifugeVaultStatus>;
-    /** The wallet's invest position: funding queued, shares claimable. */
-    getPosition(params: CentrifugeWalletParams): Promise<CentrifugeVaultPosition>;
-    /**
-     * The wallet's redeem position: shares queued, funding claimable.
-     *
-     * TODO(frontline, ENG-1909): built against a guessed endpoint.
-     */
-    getRedeemPosition(params: CentrifugeWalletParams): Promise<CentrifugeVaultRedeemPosition>;
-    /**
-     * Calldata claiming every claimable share. Broadcast it from
-     * `params.walletAddress`: the proxy credits the sender.
-     */
-    createClaim(params: CentrifugeWalletParams): Promise<CentrifugeVaultClaimTransaction>;
-    /**
-     * Calldata paying out every claimable redemption in the funding token.
-     * Broadcast it from `params.walletAddress`.
-     *
-     * TODO(frontline, ENG-1909): built against a guessed endpoint.
-     */
-    createClaimProceeds(params: CentrifugeWalletParams): Promise<CentrifugeVaultClaimProceedsTransaction>;
-    /**
-     * Builds the calldata that places a deposit request.
-     *
-     * Called once on confirmation. The reads above are the ones a checkout polls.
-     */
-    buildBuyTransaction(params: BuildCentrifugeVaultBuyParams): Promise<CentrifugeVaultBuyTransaction>;
-}
-declare class CentrifugeNamespaceImpl implements CentrifugeNamespace {
-    private readonly ctx;
-    protected readonly log: InternalLogger;
-    constructor(ctx: UniversalNamespaceContext);
-    getQuote(params: GetCentrifugeVaultQuoteParams): Promise<CentrifugeVaultQuote>;
-    getVaultStatus(params: GetCentrifugeVaultStatusParams): Promise<CentrifugeVaultStatus>;
-    getPosition(params: CentrifugeWalletParams): Promise<CentrifugeVaultPosition>;
-    getRedeemPosition(params: CentrifugeWalletParams): Promise<CentrifugeVaultRedeemPosition>;
-    createClaim(params: CentrifugeWalletParams): Promise<CentrifugeVaultClaimTransaction>;
-    createClaimProceeds(params: CentrifugeWalletParams): Promise<CentrifugeVaultClaimProceedsTransaction>;
-    buildBuyTransaction(params: BuildCentrifugeVaultBuyParams): Promise<CentrifugeVaultBuyTransaction>;
-}
-
-type AssetDto = {
-    code: string;
-    fractional_digits: number;
-    id: string;
-    name: string;
-};
-
-type AssetId = Newtype<string, 'AssetId'>;
-declare const AssetId: (value: string) => AssetId;
-type AssetCode = Newtype<string, 'AssetCode'>;
-declare const AssetCode: (value: string) => AssetCode;
-type Asset = {
-    id: AssetId;
-    code: AssetCode;
-    name: string;
-    fractionalDigits: number;
-};
-declare const Asset: {
-    fromDto: (dto: AssetDto) => Asset;
-};
-
-/**
- * The product an offer is checked out through. The backend sends one compound
- * `{supplier}::{saleType}` string, verbatim as spelled below: a double colon
- * between the two halves, `snake_case` within each. CoinList's token sale is
- * `coinlist::token_sale`; there is no `coinlist::sale` and no
- * `coinlist_token_sale`.
- *
- * Kept flat rather than split into a supplier and a sale type, because a flat
- * union makes a `switch` over it exhaustive: adding a provider without
- * handling it becomes a compile error.
- */
-type OfferTypeDto = 'coinlist::token_sale' | 'superstate::swap' | 'ondo::swap' | 'centrifuge::vault';
-/**
- * One variant per {@link OfferTypeDto}, mirroring frontline#1365, which keys
- * `GET /v1/offers` on `type`. Read `type` first: it decides which of the
- * fields below mean anything.
- */
-type OfferDto = CoinListTokenSaleOfferDto | SuperstateSwapOfferDto | OndoSwapOfferDto | CentrifugeVaultOfferDto;
-type OfferBaseDto = {
-    id: string;
-    slug: string;
-    ends_at: string | null;
-    tokens: OfferTokenDto[];
-};
-/**
- * A curated sale window and the hand-authored copy that goes with it. Required
- * on every variant that runs such a campaign, which is every one but Ondo.
- */
-type OfferEditorialDto = {
-    tagline: string;
-    banner_url: string;
-    starts_at: string;
-};
-/**
- * What an Ondo swap or a Centrifuge vault sends in place of
- * {@link OfferEditorialDto}. Neither runs a campaign, so the keys arrive as
- * `null` and carry nothing, and the backend may stop sending them at all.
- * Declared so a fixture can describe the real payload; no `fromDto` reads
- * them.
- */
-type OfferNoEditorialDto = {
-    tagline?: null;
-    banner_url?: null;
-    starts_at?: null;
-};
-type CoinListTokenSaleOfferDto = OfferBaseDto & OfferEditorialDto & {
-    type: 'coinlist::token_sale';
-    logo_url: string;
-};
-type SuperstateSwapOfferDto = OfferBaseDto & OfferEditorialDto & {
-    type: 'superstate::swap';
-    /** Publishing a swap does not require anyone to upload artwork for it. */
-    logo_url: string | null;
-};
-type OndoSwapOfferDto = OfferBaseDto & OfferNoEditorialDto & {
-    type: 'ondo::swap';
-    /** Publishing a swap does not require anyone to upload artwork for it. */
-    logo_url: string | null;
-};
-type CentrifugeVaultOfferDto = OfferBaseDto & OfferNoEditorialDto & {
-    type: 'centrifuge::vault';
-    /** Publishing a vault does not require anyone to upload artwork for it. */
-    logo_url: string | null;
-};
-type OfferTokenDto = {
-    /**
-     * `vault` is the share token a `centrifuge::vault` offer issues for
-     * deposits, as `swap` is the token a swap offer trades into.
-     */
-    role: 'funding' | 'distribution' | 'swap' | 'vault';
-    chain: string;
-    address: string;
-};
-
-/**
- * One variant per `OfferTypeDto`, the same split as `OfferDto` with what
- * `GET /v1/offers/:id` adds on top. Read `type` first.
- */
-type OfferDetailDto = CoinListTokenSaleOfferDetailDto | SuperstateSwapOfferDetailDto | OndoSwapOfferDetailDto | CentrifugeVaultOfferDetailDto;
-type CoinListTokenSaleOfferDetailDto = OfferDetailBaseDto & OfferEditorialDto & OfferDetailNoSwapContractsDto & OfferDetailNoVaultContractsDto & {
-    type: 'coinlist::token_sale';
-    logo_url: string;
-};
-type SuperstateSwapOfferDetailDto = OfferDetailBaseDto & OfferEditorialDto & OfferDetailNoSwapContractsDto & OfferDetailNoVaultContractsDto & {
-    type: 'superstate::swap';
-    logo_url: string | null;
-};
-type OndoSwapOfferDetailDto = OfferDetailBaseDto & OfferNoEditorialDto & OfferDetailNoVaultContractsDto & {
-    type: 'ondo::swap';
-    logo_url: string | null;
-    /**
-     * Every chain this offer swaps on, with the contract each settles
-     * through. `[]` is an answer - "swaps nowhere" - and a missing key is not.
-     */
-    swap_contracts: OfferDetailSwapContractDto[];
-};
-type CentrifugeVaultOfferDetailDto = OfferDetailBaseDto & OfferNoEditorialDto & OfferDetailNoSwapContractsDto & {
-    type: 'centrifuge::vault';
-    logo_url: string | null;
-    /**
-     * Every chain this vault takes deposits on, with the CoinList proxy each
-     * request goes through. `[]` is an answer - "deposits nowhere", which is
-     * every vault until a proxy is deployed - and a missing key is not.
-     */
-    vault_contracts: OfferDetailVaultContractDto[];
-};
-type OfferDetailNoVaultContractsDto = {
-    vault_contracts?: OfferDetailVaultContractDto[];
-};
-/**
- * An offer that does not settle through a CoinList swap contract sends `[]`
- * or no key at all, and either way there is nothing to read. Declared so a
- * fixture can describe the real payload.
- */
-type OfferDetailNoSwapContractsDto = {
-    swap_contracts?: OfferDetailSwapContractDto[];
-};
-type OfferDetailBaseDto = {
-    asset: AssetDto;
-    faqs: OfferDetailFaqDto[];
-    funding_assets: AssetDto[];
-    tokens: OfferTokenDto[];
-    id: string;
-    links: OfferDetailLinkDto[];
-    milestones: OfferDetailMilestoneDto[];
-    name: string;
-    object: 'offer_details';
-    options: OfferDetailOptionDto[];
-    slug: string;
-    terms: OfferDetailTermDto[];
-    about: string | null | undefined;
-    category: string;
-    ends_at: string | null;
-    /** Issuer of the *token*, not of the security it tracks. Ondo offers only. */
-    issuer: string | null;
-    /** ISO 6166 id of the underlying security. Null when the supplier has none. */
-    isin: string | null;
-    /** The underlying's symbol on its venue (`QQQ`), never the token's (`QQQon`). */
-    ticker: string | null;
-    /** Supplier vocabulary (`Stock`, `ETF`). Open set — display, do not branch. */
-    instrument_type: string | null;
-    /** Venue the underlying lists on. Not served by the supplier; entered by hand. */
-    listing_venue: string | null;
-};
-type OfferDetailFaqDto = {
-    answer: string | null;
-    question: string | null;
-};
-type OfferDetailLinkDto = {
-    label: string | null;
-    url: string | null;
-};
-type OfferDetailMilestoneDto = {
-    name: string | null;
-    schedule: string | null;
-    status: 'completed' | 'active' | 'upcoming';
-};
-type OfferDetailOptionDto = {
-    bid_increment: number | null;
-    floor_price_usd: number | null;
-    id: string;
-    minimum_purchase_usd: number | null;
-    price_usd: string | null;
-    sale_agreement_url: string | null;
-    slug: string;
-    total_token_supply: number | null;
-};
-type OfferDetailTermDto = {
-    key: string | null;
-    value: string | null;
-};
-type OfferDetailSwapContractDto = {
-    chain: string;
-    address: string;
-};
-type OfferDetailVaultContractDto = {
-    chain: string;
-    address: string;
-};
-
-type OfferId = Newtype<string, 'OfferId'>;
-declare const OfferId: (value: string) => OfferId;
-type OfferSlug = Newtype<string, 'OfferSlug'>;
-declare const OfferSlug: (value: string) => OfferSlug;
-type OfferType = OfferTypeDto;
-declare const isOfferType: (value: string) => value is OfferType;
-type OfferBase = {
-    id: OfferId;
-    slug: OfferSlug;
-    endsAt: Date | null;
-    tokens: OfferToken[];
-};
-type CoinListTokenSaleOffer = OfferBase & OfferEditorial & {
-    type: 'coinlist::token_sale';
-    logoUrl: string;
-};
-type SuperstateSwapOffer = OfferBase & OfferEditorial & {
-    type: 'superstate::swap';
-    /** Null when nobody has uploaded artwork: a swap publishes without it. */
-    logoUrl: string | null;
-};
-type OndoSwapOffer = OfferBase & {
-    type: 'ondo::swap';
-    /** Null when nobody has uploaded artwork: a swap publishes without it. */
-    logoUrl: string | null;
-};
-type CentrifugeVaultOffer = OfferBase & {
-    type: 'centrifuge::vault';
-    /** Null when nobody has uploaded artwork: a vault publishes without it. */
-    logoUrl: string | null;
-};
-/**
- * A curated sale window and the hand-authored copy that goes with it. Every
- * variant that runs such a campaign carries all three, validated; an Ondo swap
- * trades continuously and a Centrifuge vault takes deposits continuously, so
- * neither runs one and neither carries any.
- */
-type OfferEditorial = {
-    tagline: string;
-    bannerUrl: string;
-    startsAt: Date;
-};
-declare const OfferEditorial: {
-    /**
-     * `model` prefixes the field in the error (`'Offer'`, `'OfferDetail'`), so
-     * the same three checks name the payload that failed them.
-     */
-    fromDto: (dto: OfferEditorialDto, model: string) => OfferEditorial;
-};
-/**
- * An offer as `GET /v1/offers` lists it: a union on {@link OfferType}, each
- * variant carrying only the fields that mean something for it. Narrow on
- * `type` before reading anything beyond {@link OfferBase} - an Ondo swap has
- * no `startsAt` to read, and the compiler says so.
- */
-type Offer = CoinListTokenSaleOffer | SuperstateSwapOffer | OndoSwapOffer | CentrifugeVaultOffer;
-declare const Offer: {
-    fromDto: (dto: OfferDto) => Offer;
-    /**
-     * Maps a page of offers, dropping every offer whose `type` this SDK does not
-     * name. The same reasoning as {@link OfferToken.listFromDto}: a plain `.map`
-     * would throw out of `fromDto` and, through `PaginatedResponse.fromDto`,
-     * reject the whole page, so one offer of an unknown type would blank the
-     * grid for every offer beside it. A single offer fetched by id still
-     * throws, because there is nothing beside it to keep.
-     */
-    listFromDto: (dtos: OfferDto[]) => Offer[];
-};
-/**
- * `vault` is the share token a `centrifuge::vault` offer issues for deposits,
- * as `swap` is the token a swap offer trades into.
- */
-type TokenRole = 'funding' | 'distribution' | 'swap' | 'vault';
-type OfferToken = {
-    role: TokenRole;
-    chain: Chain;
-    address: EvmContractAddress;
-};
-declare const OfferToken: {
-    fromDto: (dto: OfferTokenDto) => OfferToken;
-    /**
-     * Maps an offer's token list, dropping every token on a chain this SDK does
-     * not name. Frontline's chain registry runs ahead of {@link Chain}, and a
-     * plain `.map` would throw out of `Offer.fromDto` and, through
-     * `PaginatedResponse.fromDto`, reject the whole offers page - which is how
-     * one Base token blanked production's offers list. Dropping costs that
-     * token's metadata alone: `coinlist.tokens.get` takes an `EthereumChain`,
-     * so nobody could have looked it up anyway.
-     *
-     * Same shape as `TokenMetadata.fromRegistryDto`.
-     */
-    listFromDto: (dtos: OfferTokenDto[]) => OfferToken[];
-};
-
-type Ticker = Newtype<string, 'Ticker'>;
-declare const Ticker: (value: string) => Ticker;
-/**
- * An ISO 6166 International Securities Identification Number, e.g.
- * `US0378331005`. Identifies the security itself, which is what makes it the
- * stable key across venues where a {@link Ticker} is not: the same security
- * trades under different tickers in different places, and the same ticker
- * means different securities in different places.
- *
- * Not validated on construction — the value comes from a supplier that has
- * already checked it, and a client-side check-digit test could only reject
- * data the SDK still has to display.
- */
-type Isin = Newtype<string, 'Isin'>;
-declare const Isin: (value: string) => Isin;
-type OrderBookSide = 'buy' | 'sell';
-
-/** The `type` of every {@link AsyncOfferDetail}. */
-type AsyncOfferType = AsyncOfferDetail['type'];
-/**
- * An offer whose trade settles later: the user places a request, the fund
- * fills it on its own schedule, and the user comes back to claim the result.
- * Only these have a second leg for `ClaimContainer` to show.
- *
- * A subset of {@link OfferDetail} picked by `type`, so it narrows like any
- * other variant and a new async provider is one more member here.
- */
-type AsyncOfferDetail = CentrifugeVaultOfferDetail;
-declare const AsyncOfferDetail: {
-    /**
-     * Narrows an offer fetched generically, e.g. on an offer page, to one with
-     * something to claim.
-     *
-     * An exhaustive `switch` rather than a list of async types, so a new offer
-     * type is a compile error here until someone decides whether it settles
-     * later.
-     */
-    is: (offer: OfferDetail) => offer is AsyncOfferDetail;
-};
-type CoinListTokenSaleOfferDetail = OfferDetailBase & OfferEditorial & {
-    type: 'coinlist::token_sale';
-    logoUrl: string;
-};
-type SuperstateSwapOfferDetail = OfferDetailBase & OfferEditorial & {
-    type: 'superstate::swap';
-    /** Null when nobody has uploaded artwork: a swap publishes without it. */
-    logoUrl: string | null;
-};
-type OndoSwapOfferDetail = OfferDetailBase & {
-    type: 'ondo::swap';
-    /** Null when nobody has uploaded artwork: a swap publishes without it. */
-    logoUrl: string | null;
-    /**
-     * Every chain this offer can be swapped on, with the CoinList contract each
-     * settles through. Empty means it cannot be swapped anywhere.
-     */
-    swapContracts: OfferSwapContract[];
-};
-type CentrifugeVaultOfferDetail = OfferDetailBase & {
-    type: 'centrifuge::vault';
-    /** Null when nobody has uploaded artwork: a vault publishes without it. */
-    logoUrl: string | null;
-    /**
-     * Every chain this vault takes deposits on, with the CoinList proxy each
-     * request goes through. Empty means it takes deposits nowhere yet.
-     */
-    vaultContracts: OfferVaultContract[];
-};
-type OfferDetailBase = {
-    id: OfferId;
-    slug: OfferSlug;
-    name: string;
-    asset: Asset;
-    fundingAssets: Asset[];
-    tokens: OfferToken[];
-    about: string | null;
-    category: string;
-    /**
-     * The legal issuer of the *token*, e.g. `'Ondo Global Markets'`. The issuer
-     * of the security it tracks is {@link OfferDetail.name} (`'Apple Inc.'`).
-     * Null on offers with no single named issuer.
-     */
-    issuer: string | null;
-    /**
-     * ISO 6166 identifier of the underlying security, e.g. `'US0378331005'`.
-     * Null both on offers that tokenize no security and on the few that do but
-     * whose supplier publishes no ISIN, so absence does not imply "not a
-     * security".
-     */
-    isin: Isin | null;
-    /**
-     * The underlying security's symbol on its listing venue, e.g. `'QQQ'`. This
-     * is *not* the token's symbol — that is `asset.code` (`'QQQon'`). Null on
-     * offers that tokenize no listed security.
-     */
-    ticker: Ticker | null;
-    /**
-     * What kind of instrument the underlying is, as the supplier classifies it:
-     * `'Stock'`, `'ETF'`. Distinct from {@link OfferDetail.category}, which is
-     * the broader class the offer is grouped under (`'Equities'`) — this field
-     * describes the single instrument, `category` describes the shelf it sits
-     * on.
-     *
-     * An open set: the vocabulary belongs to the supplier and may grow without
-     * notice, so render an unrecognized value rather than branching on it. Note
-     * the supplier's spelling is its own — a common stock arrives as `'Stock'`.
-     */
-    instrumentType: string | null;
-    /**
-     * The exchange the underlying security lists on, e.g. `'NASDAQ'`. Not
-     * derivable from {@link OfferDetail.isin}, whose country prefix is the
-     * country of issuance rather than the venue.
-     *
-     * Unlike the fields above, this one is recorded by hand rather than served
-     * by the supplier, so it is null until someone records it — on a newly
-     * listed offer that is the normal state, and it says nothing about whether
-     * the offer tokenizes a security.
-     */
-    listingVenue: string | null;
-    endsAt: Date | null;
-    faqs: FaqItem[];
-    links: Link[];
-    milestones: Milestone[];
-    options: OfferOption[];
-    terms: TermItem[];
-};
-type OfferOptionId = Newtype<string, 'OfferOptionId'>;
-declare const OfferOptionId: (value: string) => OfferOptionId;
-type OfferOptionSlug = Newtype<string, 'OfferOptionSlug'>;
-declare const OfferOptionSlug: (value: string) => OfferOptionSlug;
-/**
- * A chain an offer can be swapped on, with the CoinList contract the swap
- * settles through - the spender to approve before any quote exists.
- *
- * Carries no role, unlike {@link OfferToken}: there is one swap contract per
- * chain and it serves every Ondo asset on it, so which token is being traded
- * does not change the answer.
- */
-type OfferSwapContract = {
-    chain: Chain;
-    address: EvmContractAddress;
-};
-declare const OfferSwapContract: {
-    fromDto: (dto: OfferDetailSwapContractDto) => OfferSwapContract;
-};
-/**
- * A chain a Centrifuge vault takes deposits on, with the CoinList proxy the
- * request goes through. Not a token, so the token registry knows nothing about
- * it: it is the spender the user approves the funding token to, and the `to`
- * the buy and claim transactions are sent to.
- *
- * Its own type rather than an {@link OfferSwapContract}, although the shape is
- * the same, because the meaning is not: a swap contract serves every Ondo
- * asset on its chain, while a proxy belongs to one offer on one chain, so the
- * same chain carries a different address on every vault.
- */
-type OfferVaultContract = {
-    chain: Chain;
-    address: EvmContractAddress;
-};
-declare const OfferVaultContract: {
-    fromDto: (dto: OfferDetailVaultContractDto) => OfferVaultContract;
-    /**
-     * Drops every proxy on a chain this SDK does not name, as
-     * `OfferToken.listFromDto` does: frontline publishes the full offer-token
-     * chain list, which runs ahead of {@link Chain}, and one unmodelled chain
-     * should not throw away the proxies the SDK can use.
-     */
-    listFromDto: (dtos: OfferDetailVaultContractDto[]) => OfferVaultContract[];
-};
-/**
- * An offer as `GET /v1/offers/:id` serves it: the same union on `type` as
- * {@link Offer}, each variant carrying only the fields that mean something
- * for it. Narrow on `type` before reading anything beyond
- * {@link OfferDetailBase}.
- */
-type OfferDetail = CoinListTokenSaleOfferDetail | SuperstateSwapOfferDetail | OndoSwapOfferDetail | CentrifugeVaultOfferDetail;
-declare const OfferDetail: {
-    fromDto: (dto: OfferDetailDto) => OfferDetail;
-};
-type OfferOption = {
-    id: OfferOptionId;
-    slug: OfferOptionSlug;
-    bidIncrement: number | null;
-    floorPriceUsd: number | null;
-    minimumPurchaseUsd: number | null;
-    priceUsd: string | null;
-    saleAgreementUrl: string | null;
-    totalTokenSupply: number | null;
-};
-declare const OfferOption: {
-    fromDto: (dto: OfferDetailOptionDto) => OfferOption;
-};
-type FaqItem = {
-    question: string | null;
-    answer: string | null;
-};
-declare const FaqItem: {
-    fromDto: (dto: OfferDetailFaqDto) => FaqItem;
-};
-type Link = {
-    label: string | null;
-    url: string | null;
-};
-declare const Link: {
-    fromDto: (dto: OfferDetailLinkDto) => Link;
-};
-type TermItem = {
-    key: string | null;
-    value: string | null;
-};
-declare const TermItem: {
-    fromDto: (dto: OfferDetailTermDto) => TermItem;
-};
-type Milestone = {
-    name: string | null;
-    schedule: string | null;
-    status: 'completed' | 'active' | 'upcoming';
-};
-declare const Milestone: {
-    fromDto: (dto: OfferDetailMilestoneDto) => Milestone;
-};
-
-/**
- * The cursor-paginated envelope every list endpoint returns.
- *
- * Generic in its item type, so each resource pairs it with its own item DTO
- * rather than declaring an envelope of its own.
- */
-interface PaginatedResponseDto<T> {
-    data: T[];
-    starting_after?: string;
-    starting_before?: string;
-}
-
-type Cursor = Newtype<string, 'Cursor'>;
-declare const Cursor: (value: string) => Cursor;
-interface PaginatedResponse<T> {
-    data: T[];
-    startingAfter: Cursor | null;
-    startingBefore: Cursor | null;
-}
-declare const PaginatedResponse: {
-    fromDto: <A, B>(dto: PaginatedResponseDto<A>, itemMapper: (item: A) => B) => PaginatedResponse<B>;
-    /**
-     * For a mapper that decides the page as a whole - one that drops items it
-     * cannot map, such as `Offer.listFromDto` - rather than item by item. The
-     * cursors are the wire's either way: dropping an item changes what the
-     * page holds, not where the next page starts.
-     */
-    fromDtoPage: <A, B>(dto: PaginatedResponseDto<A>, pageMapper: (items: A[]) => B[]) => PaginatedResponse<B>;
-};
-/**
- * Cursor-based pagination input used when requesting paginated API resources.
- * Set `after` or `before` to navigate relative to a known cursor, and `limit`
- * to control the maximum number of returned items.
- */
-interface PaginationParams {
-    before?: Cursor;
-    after?: Cursor;
-    limit?: number;
-}
-declare const PaginationParams: {
-    toQueryParams: (params: PaginationParams) => Record<string, QueryParamValue>;
-};
-
-type ParticipationStatusDto = 'prepared' | 'pending' | 'submitted' | 'completed' | 'failed' | 'remit_submitted' | 'remitted' | 'remit_failed';
-type ParticipationDto = {
-    object: 'participation';
-    id: string;
-    offer_id: string;
-    offer_option_id: string;
-    status: ParticipationStatusDto;
-    amount: string;
-    amount_string: string;
-    asset: AssetDto;
-    chain: string;
-    inserted_at: string | null | undefined;
-    updated_at: string | null | undefined;
-    wallet_address: string | null | undefined;
-};
-type CreateParticipationDto = {
-    offer_id: string;
-    offer_option_id: string;
-    chain: string;
-    wallet_address: string;
-    amount: string;
-    asset_id: string;
-    approval_transaction_hash: string | null | undefined;
-};
-
-/** Unique identifier for a participation. */
-type ParticipationId = Newtype<string, 'ParticipationId'>;
-/** Casts a string into a typed {@link ParticipationId}. */
-declare const ParticipationId: (value: string) => ParticipationId;
-/** Blockchain identifier for where a participation is funded. */
-type Blockchain = Newtype<string, 'Blockchain'>;
-/** Casts a string into a typed {@link Blockchain}. */
-declare const Blockchain: (value: string) => Blockchain;
-/** Wallet address used for a participation. */
-type WalletAddress = Newtype<`0x${string}`, 'WalletAddress'>;
-/** Casts a `0x`-prefixed string into a typed {@link WalletAddress}. */
-declare const WalletAddress: (value: `0x${string}`) => WalletAddress;
-/** Possible participation lifecycle states returned by the API. */
-type ParticipationStatus = ParticipationStatusDto;
-/** Pagination params for listing participations, with an optional offer filter. */
-interface ParticipationsPaginationParams extends PaginationParams {
-    offerId?: OfferId;
-}
-declare const ParticipationsPaginationParams: {
-    toQueryParams: (params: ParticipationsPaginationParams) => Record<string, QueryParamValue>;
-};
-/** Domain model for a participation returned by CoinList APIs. */
-type Participation = {
-    /** Unique participation id. */
-    id: ParticipationId;
-    /** Parent offer id. */
-    offerId: OfferId;
-    /** Selected offer option id. */
-    offerOptionId: OfferOptionId;
-    /** Current processing status. */
-    status: ParticipationStatus;
-    /** Raw participation amount from API. */
-    amount: string;
-    /** Human-readable formatted amount from API. */
-    displayAmount: string;
-    /** Asset metadata for the participation amount. */
-    asset: Asset;
-    /** Funding chain identifier. */
-    chain: Blockchain;
-    /** Creation timestamp, if returned by API. */
-    insertedAt: Date | null;
-    /** Last update timestamp, if returned by API. */
-    updatedAt: Date | null;
-    /** Wallet used for participation, blank values normalized to null. */
-    walletAddress: WalletAddress | null;
-};
-declare const Participation: {
-    /** Maps API DTO shape into the SDK participation domain model. */
-    fromDto: (dto: ParticipationDto) => Participation;
-};
-/** Parameters required to create a new participation. */
-type CreateParticipationParams = {
-    /** Offer to participate in. */
-    offerId: OfferId;
-    /** Offer option selected for participation. */
-    offerOptionId: OfferOptionId;
-    /** Blockchain for funding. */
-    chain: Blockchain;
-    /** Wallet address that funds the participation. */
-    walletAddress: WalletAddress;
-    /**
-     * Decimal token amount to participate with (e.g. `"100"` for 100 USDC), NOT
-     * raw base units. The backend rescales this by the asset's decimals to verify
-     * it against the on-chain approval allowance.
-     */
-    amount: string;
-    /** Funding asset id. */
-    assetId: AssetId;
-    /**
-     * Hash of the ERC-20 `approve()` transaction covering this participation.
-     * Required: the backend verifies it on-chain (sender, token, spender, and
-     * approved amount) before confirming the participation.
-     */
-    approvalTransactionHash: string;
-};
-declare const CreateParticipationParams: {
-    /** Maps participation creation params into API DTO payload. */
-    toDto: (params: CreateParticipationParams) => CreateParticipationDto;
-};
-
-/**
- * Read/write operations for token sales: listing and reading the current user's
- * participations, and recording a new one. The on-chain execution flow
- * (`executeTokenSale`) is layered on top of this in the client-side namespace.
- */
-interface CoinListTokenSaleNamespace {
-    /**
-     * Fetches all participations by iterating through every paginated response,
-     * optionally filtered by offer.
-     *
-     * Requires an authenticated user; throws {@link NotAuthenticatedError}
-     * otherwise.
-     */
-    list(offerId?: OfferId): Promise<Participation[]>;
-    /**
-     * Fetches a single page of participations, optionally filtered by offer.
-     *
-     * Requires an authenticated user; throws {@link NotAuthenticatedError}
-     * otherwise.
-     */
-    listPage(params: ParticipationsPaginationParams): Promise<PaginatedResponse<Participation>>;
-    /**
-     * Fetches a participation by id.
-     *
-     * Requires an authenticated user; throws {@link NotAuthenticatedError}
-     * otherwise.
-     */
-    get(id: ParticipationId): Promise<Participation>;
-    /**
-     * Records a participation with CoinList.
-     *
-     * Requires an authenticated user; throws {@link NotAuthenticatedError}
-     * otherwise.
-     */
-    createParticipation(params: CreateParticipationParams): Promise<Participation>;
-}
-declare class CoinListTokenSaleNamespaceImpl implements CoinListTokenSaleNamespace {
-    private readonly ctx;
-    protected readonly log: InternalLogger;
-    constructor(ctx: UniversalNamespaceContext);
-    list(offerId?: OfferId): Promise<Participation[]>;
-    listPage(params: ParticipationsPaginationParams): Promise<PaginatedResponse<Participation>>;
-    get(id: ParticipationId): Promise<Participation>;
-    createParticipation(params: CreateParticipationParams): Promise<Participation>;
-}
-
-/**
- * No `chain` on the read params: Ondo runs no sandbox, so every environment
- * prices against Ondo production on Ethereum mainnet. Accepting a chain would
- * let a caller ask for Sepolia and silently receive mainnet pricing.
- * {@link BuildOndoSwapTransactionParams} is the exception, and says why.
- */
-type GetOndoTradingStatusParams = {
-    symbol: AssetSymbol;
-    /**
-     * Required, and deliberately not defaulted: `tradable` and both order caps
-     * describe this side only. Guessing `buy` would hand buy caps to someone
-     * sizing a sell. The endpoint answers 422 without it.
-     */
-    side: OrderBookSide;
-};
-/** How long Ondo should hold the price. Omit to take Ondo's own default. */
-type OndoQuoteDuration = 'short' | 'long';
-/**
- * A quote is sized by the quantity or by the dollar amount. The endpoint takes
- * exactly one; `getOndoQuote` sends whichever is present.
- */
-type OndoQuoteSize = {
-    tokenAmount: BlockchainAmount;
-} | {
-    notionalValue: DecimalString;
-};
-type GetOndoQuoteParams = {
-    symbol: AssetSymbol;
-    side: OrderBookSide;
-    duration?: OndoQuoteDuration;
-} & OndoQuoteSize;
-/**
- * What both builders take, before the one field whose meaning forks.
- *
- * There is no funding token and no asset here - frontline resolves both from
- * the offer, because Ninshubur signs a request bound to them and a caller that
- * could name them could have CoinList sign for a contract of its own. Which
- * endpoint was called is what says which of the two `amount` counts.
- *
- * `chain` is required although the read params refuse it, because these name a
- * real contract on a real chain rather than asking Ondo for a price.
- */
-type BuildOndoSwapParamsCore = {
-    symbol: AssetSymbol;
-    chain: EthereumChain;
-    /**
-     * The wallet that will *send* the transaction, and that receives the other
-     * token. The calldata is signed over it, so a transaction built for one
-     * wallet and broadcast by another reverts.
-     */
-    walletAddress: EvmWalletAddress;
-};
-/**
- * What it takes to turn an indicative price into signed, fillable calldata for
- * a purchase: `POST /v1/ondo/swap/buy`.
- *
- * Separate from {@link BuildOndoSellParams} although the fields match today,
- * because `amount` is denominated in a different token on each - which is
- * frontline's own reason for splitting the endpoint rather than taking a
- * `side`. Sharing one type would re-merge the distinction the split exists to
- * make, and the two will diverge the day either side gains a knob.
- */
-type BuildOndoBuyParams = BuildOndoSwapParamsCore & {
-    /**
-     * The **gross** deposit, in the base units of the funding token - the coin
-     * the user chose and approved.
-     *
-     * Sized by `amount` alone, with no `notionalValue` alternative: the calldata
-     * authorises a specific ERC-20 pull, so the number that ends up on chain has
-     * to be the number the caller meant rather than one derived from a dollar
-     * figure. CoinList's fee comes off it, and Ondo prices the remainder.
-     *
-     * Its `decimals` are also what the response's `spend_input_decimals` is
-     * checked against: frontline resolves the funding token from the offer
-     * rather than from this request, so the two are independent answers to the
-     * same question and a disagreement means the wrong token was sized.
-     */
-    amount: BlockchainAmount;
-};
-/**
- * What it takes to turn an indicative price into signed, fillable calldata for
- * a sale: `POST /v1/ondo/swap/sell`.
- *
- * See {@link BuildOndoBuyParams} for why this is its own type.
- */
-type BuildOndoSellParams = BuildOndoSwapParamsCore & {
-    /**
-     * The quantity of the **asset** to sell, in the asset's own base units - not
-     * in the funding token's, which is the same integer meaning something 1e12
-     * different.
-     *
-     * This is the figure the wallet must have approved: a sale delivers the
-     * asset, so the swap contract pulls it with `transferFrom` exactly as it
-     * pulls the deposit on a purchase.
-     *
-     * Its `decimals` are checked against the response's `spend_input_decimals`,
-     * which frontline reads on-chain from the asset on `chain`. The SDK's own
-     * answer comes from the quote, which resolves the asset on Ethereum mainnet,
-     * so on a testnet these are two independent resolutions of two different
-     * contracts - and the check is what says so.
-     */
-    amount: BlockchainAmount;
-};
-
-/**
- * Raw JSON models for the Ondo swap endpoints, mirroring
- * `OndoSwapTradingStatus`, `OndoSwapQuote`, `OndoSwapBuy` and `OndoSwapSell`
- * in frontline's OpenAPI schema. The two GETs are free to poll: neither spends
- * an attestation, so a client may call them while the user edits an order. The
- * two POSTs are not - each spends one and hands back signed calldata with a
- * deadline.
- *
- * **One endpoint per side, and therefore one model per side.** The reads take
- * a `side` and answer the same shape either way, so they stay single. The
- * writes do not: a buy commits to an exact quantity, a sell to a range with a
- * floor beneath it, and `amount` is the funding token on one and the asset on
- * the other. Only the transport fields mean the same thing on both.
- * `POST /v1/ondo/swap/transaction` survives as a deprecated alias of the buy
- * under the old `pay_input_*` names; the SDK does not call it.
- *
- * Neither GET takes a `chain`. Ondo runs no sandbox, so every environment
- * prices against Ondo production on Ethereum mainnet. The POSTs do carry one:
- * they target a real contract, which on every environment but production is
- * the Sepolia one with the mocked attestation.
- */
-/**
- * Whether an asset can be traded right now, and the caps if so.
- *
- * Every cap is a *human decimal* string and is nullable — Ondo answers a
- * restricted `/v1/limits/*` with a 403, which frontline turns into
- * `tradable: false` and three nulls rather than an error. A null cap therefore
- * means **Ondo restricted the asset, not that the cap is unlimited**. The
- * response carries no `asset_decimals`, so there is nothing to scale
- * `gross_max_tokens` by.
- *
- * There is no `reason` field. A restriction surfaces only as `tradable: false`
- * plus the nulls; frontline keeps Ondo's reason codes to its own admin surface
- * and does not forward them.
- */
-type OndoTradingStatusDto = {
-    object: 'ondo_swap_trading_status';
-    /** The `side` the request asked for, echoed back. */
-    side: 'buy' | 'sell';
-    /** For `side` only — an asset can be sellable while not buyable. */
-    tradable: boolean;
-    /** Whole tokens, for `side` only. E.g. `"100.000000000000000000"`. */
-    gross_max_tokens: string | null;
-    /** USD, for `side` only. E.g. `"1234.560000000000000000"`. */
-    gross_max_notional_value: string | null;
-    /**
-     * USD cap for the session the market is currently in, e.g. `"200000"`.
-     * Unlike the two above this comes from Ondo's sideless session endpoint, so
-     * it applies across buys and sells together.
-     */
-    gross_max_active_notional_value: string | null;
-};
-/** An indicative, size- and side-aware price for an Ondo asset. */
-type OndoQuoteDto = {
-    object: 'ondo_swap_quote';
-    /** EIP-155 chain id. Always `"1"`, per the no-sandbox note above. */
-    chain_id: string;
-    symbol: string;
-    /** Ticker of the underlying security, e.g. `"AAPL"` for `"AAPLon"`. */
-    ticker: string;
-    asset_address: string;
-    /** Decimals of the `asset_address` contract. Scales `token_base_units`. */
-    asset_decimals: number;
-    side: 'buy' | 'sell';
-    /**
-     * Quantity of the asset in its smallest unit, as a raw uint256 string:
-     * `"5000000000000000000"` is 5 tokens at 18 decimals. Map it with
-     * `blockchainAmountFromRawOrThrow`, not `parseBlockchainAmountOrThrow`.
-     *
-     * Not to be confused with the `token_amount` *request* parameter, which is
-     * the same quantity in whole tokens. Ondo names both `tokenAmount`, 1e18
-     * apart, so echoing one back as the other is a real hazard.
-     */
-    token_base_units: string;
-    /**
-     * USD price of one whole token as a human decimal string, e.g.
-     * `"225.273151158540753535"`. Already scaled, so it needs none of the
-     * handling `token_base_units` does.
-     */
-    price: string;
-};
-/**
- * The transport half of a built swap, identical on both sides.
- *
- * `spend_input_amount` is the only key here whose *token* depends on the side,
- * and `spend_input_decimals` is what says at what scale. Everything below this
- * point differs, which is why the two responses are two types rather than one
- * with nullable halves.
- *
- * There is no `object` envelope and no `side` echo. `action` says what to do
- * with the body, matching `AllowWalletResponseDto`; which trade it encodes is
- * settled by the endpoint that was called, so nothing on the wire has to say
- * it and nothing has to be checked against it.
- */
-type OndoSwapDtoCore = {
-    action: 'broadcast_transaction';
-    /** The swap contract the transaction is sent to. */
-    to: string;
-    /** ABI-encoded `swap(...)` calldata. Broadcast verbatim - never re-encode it. */
-    data: string;
-    /**
-     * When the signed calldata stops being accepted - RFC3339, e.g.
-     * `"2026-08-13T23:04:12Z"`. This is Ninshubur's `expiration`, which signs
-     * the same instant as the EIP-712 `deadline` in the calldata, so a
-     * transaction broadcast after it reverts.
-     */
-    expires_at: string;
-    /**
-     * Gross amount the wallet spends, echoing the requested `amount`, in the
-     * smallest unit of the token this side spends - the funding token on a buy,
-     * the asset on a sell. The approval is compared against this.
-     *
-     * Named `pay_input_amount` on the deprecated
-     * `POST /v1/ondo/swap/transaction`. `pay` was accurate only while a buy was
-     * the sole thing this could encode: a sell delivers the asset rather than
-     * paying for one.
-     */
-    spend_input_amount: string;
-    /**
-     * Decimals `spend_input_amount` is counted in.
-     *
-     * Frontline reads it on-chain from the token the side spends, which it
-     * resolves from the offer rather than from anything the caller sent. That
-     * makes it the only published scale for a token the request never names -
-     * and an independent answer to the one the SDK derived when it sized the
-     * order, which is why both builders compare the two.
-     *
-     * **The same key, two scales.** It counts whichever token the side spends:
-     * the funding token's 6 on a buy, the asset's 18 on a sell. Worth knowing
-     * before integrating against both.
-     */
-    spend_input_decimals: number;
-};
-/**
- * Signed, ready-to-broadcast calldata for a purchase, and the amounts it
- * commits to: `POST /v1/ondo/swap/buy`.
- *
- * Unlike {@link OndoQuoteDto} this **spends an attestation**, so it is not
- * pollable: one call per order, plus one per user-requested refresh. Frontline
- * also reads the wallet's allowance on the funding token before asking
- * Ninshubur for anything, so an unapproved wallet is refused here rather than
- * reverting on chain.
- *
- * The quantity is attested and exact, with no floor beneath it, which is what
- * separates a buy from an {@link OndoSellDto}.
- *
- * **Carries no identity and no price.** No `chain_id`, `symbol`, `ticker` or
- * `price` - the request named the first few and frontline drops Ninshubur's
- * `price` deliberately, because `GET /v1/ondo/swap/quote` already publishes
- * one under that name at a different scale. Anything the UI needs beyond the
- * amounts comes from that GET or from the offer.
- *
- * Two scales are on the wire: `fee` and `notional_value` are in
- * `spend_input_decimals`, and `receive_output_amount` is in
- * `receive_output_decimals`. Neither is interchangeable with the quote's
- * `asset_decimals`, which answers for a different number.
- */
-type OndoBuyDto = OndoSwapDtoCore & {
-    /**
-     * CoinList's cut of `spend_input_amount`, in the same units. `"0"` until
-     * ENG-1718 turns a fee on - frontline rejects a non-zero one today.
-     *
-     * Taken at execution rather than added on top, so the wallet never approves
-     * more than `spend_input_amount`.
-     */
-    fee: string;
-    /**
-     * `spend_input_amount` less `fee`, in `spend_input_decimals`: the part that
-     * reaches Ondo, what the quantity was priced against, and what the
-     * signature commits to.
-     */
-    notional_value: string;
-    /**
-     * Quantity of the asset the wallet receives, in the asset's smallest unit.
-     * Scale it by `receive_output_decimals`, not by the funding token's and not
-     * by {@link OndoQuoteDto}'s `asset_decimals`.
-     */
-    receive_output_amount: string;
-    /**
-     * Decimals `receive_output_amount` is counted in.
-     *
-     * Reported by whatever priced the quantity, rather than looked up from the
-     * asset. That is not the same number as {@link OndoQuoteDto}'s
-     * `asset_decimals`, which frontline resolves from its own catalogue: the two
-     * are allowed to disagree, and only this one answers for the quantity in
-     * this response.
-     */
-    receive_output_decimals: number;
-};
-/**
- * Signed, ready-to-broadcast calldata for a sale, and the range it commits to:
- * `POST /v1/ondo/swap/sell`.
- *
- * Like {@link OndoBuyDto} it **spends an attestation** and expires, so it is
- * called once on confirmation and never on a timer. Frontline reads the
- * wallet's allowance on the **asset** before signing - a sell delivers it -
- * and refuses a short one with a 422 naming that address.
- *
- * **A sell commits to a range rather than a quantity.** Ondo settles through
- * USDon before converting to the settlement token, so the response publishes
- * what to expect and the floor the calldata enforces, each with the fee
- * charged at it. There is no `notional_value`: a sell commits on the output
- * side, so there is no fee-exclusive input to report and frontline declines to
- * relate numbers Ninshubur did not relate.
- *
- * All four amounts below are in `receive_output_decimals`. The one amount that
- * is not is `spend_input_amount`, in `spend_input_decimals` - see
- * {@link OndoSwapDtoCore}.
- *
- * One thing the response does not say, and the calldata does: the floor signed
- * into `data` is **gross** of CoinList's fee, so a caller decoding it finds a
- * larger number than `minimum_quantity`. Both are correct; `minimum_quantity`
- * is what the wallet actually receives.
- */
-type OndoSellDto = OndoSwapDtoCore & {
-    /**
-     * CoinList's cut at the expected outcome, in the settlement token. Already
-     * deducted from `expected_quantity` rather than charged on top of it.
-     *
-     * `"0"` until ENG-1718 turns a fee on - frontline rejects a non-zero one on
-     * either side today.
-     */
-    expected_fee: string;
-    /**
-     * What the sale is expected to return, **net of `expected_fee`**, in the
-     * settlement token's smallest unit.
-     *
-     * An expectation rather than a guarantee. What the contract enforces is
-     * {@link OndoSellDto.minimum_quantity}.
-     */
-    expected_quantity: string;
-    /**
-     * CoinList's cut at the floor, in the same units.
-     *
-     * A different number from `expected_fee` because the two are charged on
-     * different amounts - which is why frontline publishes both rather than one.
-     * This is the one to disclose worst-case cost with.
-     */
-    minimum_fee: string;
-    /**
-     * The least the wallet can receive, **net of `minimum_fee`**, in the same
-     * units. Below it the transaction reverts on chain.
-     *
-     * Frontline guarantees it is at most `expected_quantity` and greater than
-     * zero. The settlement lands somewhere between the two.
-     */
-    minimum_quantity: string;
-    /**
-     * Decimals both quantities and both fees are counted in, reported by
-     * whatever priced them rather than looked up from the token.
-     *
-     * Not the same number as {@link OndoQuoteDto}'s `asset_decimals`, which
-     * answers for the asset being sold rather than for the coin the proceeds
-     * arrive in.
-     */
-    receive_output_decimals: number;
-};
-
-/**
- * Whether an Ondo asset can be traded right now.
- *
- * The caps only mean anything while trading is open, so they live on the
- * `tradable` branch. They stay {@link DecimalString} rather than
- * {@link BlockchainAmount} because the response carries no `asset_decimals`:
- * there is no honest exponent to attach, and the USD caps arrive with more
- * fractional digits than a stablecoin has decimals.
- *
- * Each cap is independently nullable even when tradable — Ondo may open an
- * asset for trading without publishing every limit.
- *
- * `side` is carried through from the response rather than dropped: the whole
- * status describes one side, so a buy and a sell status are otherwise
- * indistinguishable once a caller holds both.
- */
-type OndoTradingStatus = {
-    type: 'tradable';
-    side: OrderBookSide;
-    /** Largest order in whole tokens. */
-    grossMaxTokens: DecimalString | null;
-    /** Largest order in USD. */
-    grossMaxNotionalValue: DecimalString | null;
-    /** USD cap for the session the market is currently in. */
-    grossMaxActiveNotionalValue: DecimalString | null;
-} | {
-    type: 'not-tradable';
-    side: OrderBookSide;
-};
-declare const OndoTradingStatus: {
-    fromDto: (dto: OndoTradingStatusDto) => OndoTradingStatus;
-};
-/**
- * An indicative price for an Ondo asset, free to poll while the user edits an
- * order.
- *
- * **No CoinList fee is applied to the quantity or the price.** Ondo prices
- * exactly the amount asked for. A CoinList approval is fee-inclusive, so
- * sizing a quote against one without netting the fee first overstates what the
- * user receives. Showing a gross/net breakdown needs a CoinList swap
- * contract's `preview`, and no such contract exists for Ondo yet.
- *
- * The quote carries no transaction to broadcast and no expiry. Building one is
- * a separate endpoint per side that spends an attestation - see
- * {@link OndoBuyTransaction} and {@link OndoSellTransaction}.
- */
-type OndoQuote = {
-    /** Always `ethereum_mainnet`: Ondo runs no sandbox in any environment. */
-    chain: EthereumChain;
-    ticker: Ticker;
-    /**
-     * Needed to approve or transfer the asset; the quote is the only source.
-     *
-     * **Resolved on Ethereum mainnet**, like everything else on this quote, and
-     * therefore not necessarily the contract the swap pulls from on the chain
-     * the order executes on. Frontline resolves that one per chain and publishes
-     * it nowhere, so on a testnet these are two different tokens. Tracked
-     * against the frontline stack that follows ENG-1756.
-     */
-    assetAddress: EvmContractAddress;
-    /**
-     * The asset as the quote resolves it, from frontline's own catalogue.
-     *
-     * Its `decimals` scale {@link tokenBaseUnits} and nothing else. They are
-     * **not** the scale of a built transaction's spend or output: those are
-     * reported by whatever priced them, the sources are allowed to disagree, and
-     * only the one that produced a number answers for it.
-     */
-    asset: Erc20Asset;
-    side: OrderBookSide;
-    tokenBaseUnits: BlockchainAmount;
-    /**
-     * USD price of one whole token. Unscaled because Ondo has already scaled it,
-     * and by USDon's 18 decimals rather than the stablecoin's 6 — re-scaling it
-     * by either would be wrong.
-     */
-    price: DecimalString;
-};
-declare const OndoQuote: {
-    fromDto: (dto: OndoQuoteDto) => OndoQuote;
-};
-/**
- * The half of a built swap that both sides share: the calldata, its deadline,
- * and what the wallet parts with.
- *
- * There is deliberately **no union over the two sides**. Each is built by its
- * own endpoint and its own namespace method, so a caller never holds one
- * without knowing which it is, and a union would only re-pose a question the
- * call site had already answered. What is genuinely common lives here, and
- * {@link executeOndoSwap} takes this rather than either arm - broadcasting
- * knows nothing about the direction of the trade.
- *
- * `side` is not on this type but on each arm, as a literal the SDK authors
- * from the method that was called. The wire stopped echoing one when the
- * endpoint split, and it is still worth carrying: `OndoOrderPlaced` is a union
- * the SDK builds from both, and that union needs a tag.
- */
-type OndoSwapTransactionCore = {
-    /**
-     * Broadcast as-is. The `to` is the swap contract, which is also the ERC-20
-     * spender the user must have approved.
-     */
-    tx: Tx;
-    /**
-     * When the calldata stops being accepted. A transaction broadcast after this
-     * reverts, so callers must compare against it before signing.
-     */
-    expiresAt: Date;
-    /**
-     * Gross amount the wallet spends, in the decimals of the token this side
-     * spends: the funding token on a buy, the asset on a sell.
-     *
-     * The same field at two scales, which is the whole reason the two sides are
-     * two types. It is also what the approval has to cover.
-     */
-    spendInputAmount: BlockchainAmount;
-};
-/**
- * A signed, expiring purchase: a funding token in, an exact quantity of the
- * asset out.
- *
- * Distinct from {@link OndoQuote} in three ways that matter: it costs an
- * attestation to obtain, it expires, and it carries a {@link Tx} the wallet
- * broadcasts verbatim. Treat it as single-use - once broadcast (or once
- * `expiresAt` passes) it is spent, and a new one must be built.
- *
- * **The quantity is attested and exact, with no floor beneath it.** That is
- * what separates it from an {@link OndoSellTransaction}, which commits to a
- * range: nothing here is an estimate.
- *
- * **It carries no other identity.** No chain, ticker or asset: the endpoint
- * publishes none of them, and inventing them from the request would assert
- * what the server resolved rather than report it. What it does publish is the
- * scale of every amount on it, so a caller needs nothing alongside it to read
- * the numbers - only to name the assets, which the offer already does.
- *
- * It carries no price either. See `computeOndoBuyPrice`, which derives it from
- * the amounts the response does carry - the price this transaction fills at,
- * rather than an indicative one that has since moved.
- */
-type OndoBuyTransaction = OndoSwapTransactionCore & {
-    side: 'buy';
-    /**
-     * CoinList's cut, in `spendInputAmount`'s decimals. Zero until ENG-1718
-     * lands - frontline rejects a non-zero one on either side today.
-     *
-     * Taken at execution rather than added on top, so the approval never has to
-     * cover more than `spendInputAmount`.
-     */
-    fee: BlockchainAmount;
-    /**
-     * `spendInputAmount` less `fee`, in the same decimals: what Ondo priced, and
-     * the numerator of the fill price.
-     *
-     * Read from the response rather than subtracted here. Whether the fee comes
-     * off the deposit or goes on top of it is the server's definition to change,
-     * and a client that derives this cannot notice when it does.
-     */
-    notionalValue: BlockchainAmount;
-    /**
-     * Quantity of the asset the wallet receives, at the scale whatever priced it
-     * reported - not at the {@link OndoQuote}'s `asset.decimals`.
-     */
-    receiveOutputAmount: BlockchainAmount;
-};
-declare const OndoBuyTransaction: {
-    fromDto: (dto: OndoBuyDto) => OndoBuyTransaction;
-};
-/**
- * One end of the range a sale commits to: what arrives, and what CoinList took
- * to get it there.
- *
- * The two travel together because they are charged against each other -
- * `quantity` is already **net** of `fee` - and because the pair a caller wants
- * is always both halves of the same outcome. Grouping them is what makes
- * "the expected quantity, less the fee at the floor" unrepresentable rather
- * than merely wrong.
- */
-type OndoSellOutcome = {
-    /** What the wallet receives at this outcome, net of {@link fee}. */
-    quantity: BlockchainAmount;
-    /**
-     * CoinList's cut at this outcome, in the same decimals. Zero until ENG-1718
-     * lands - frontline rejects a non-zero one on either side today.
-     *
-     * Already deducted from {@link quantity} rather than charged on top of it.
-     */
-    fee: BlockchainAmount;
-};
-/**
- * A signed, expiring sale: the asset in, a settlement coin out, somewhere
- * between two published outcomes.
- *
- * Single-use and expiring for the same reasons as an {@link OndoBuyTransaction},
- * and obtained the same way - one endpoint, one attestation.
- *
- * **A sale commits to a range, not a quantity.** Ondo settles through USDon
- * before converting to the settlement token, so {@link expected} is what to
- * expect and {@link minimum} is what the calldata enforces. A screen that
- * shows only the first presents a firm-looking number the contract may
- * legitimately fill below.
- *
- * There is deliberately no counterpart to a buy's `notionalValue`. A sale
- * commits on the output side, so frontline reports no fee-exclusive input and
- * refuses to relate numbers Ninshubur did not relate. What it does relate is
- * each quantity to the fee beside it, which is why {@link OndoSellOutcome}
- * pairs them.
- *
- * One thing this type cannot see: the floor signed into `tx.data` is gross of
- * the fee, so a caller decoding the calldata finds a larger number than
- * `minimum.quantity`. Both are correct; `minimum.quantity` is what the wallet
- * actually receives.
- */
-type OndoSellTransaction = OndoSwapTransactionCore & {
-    side: 'sell';
-    /** What the sale is expected to return. An expectation, not a guarantee. */
-    expected: OndoSellOutcome;
-    /**
-     * The floor the calldata enforces. A fill below it reverts on chain, so this
-     * - not {@link expected} - is what a seller is actually guaranteed.
-     */
-    minimum: OndoSellOutcome;
-};
-declare const OndoSellTransaction: {
-    fromDto: (dto: OndoSellDto) => OndoSellTransaction;
-};
-
-/**
- * Ondo swap reads, plus the write that turns one into a fillable transaction.
- *
- * The two reads are free to poll - neither spends an attestation, so a client
- * may call them while the user edits an order. The two builders are not:
- * budget one call per order placed, plus one per refresh the user asks for.
- *
- * **One builder per side, mirroring the endpoints.** A purchase and a sale
- * agree on how to broadcast and on nothing else: a purchase commits to an
- * exact quantity, a sale to a range with a floor beneath it, and `amount` is
- * the funding token on one and the asset on the other. A single method taking
- * a `side` would have to return a union the caller then re-narrows, having
- * already decided which trade it was placing.
- *
- * **No CoinList fee is applied to a read quote, and no read discloses one.**
- * Ondo prices exactly the amount passed. A CoinList approval is fee-inclusive,
- * so sizing a quote against a user's approval without subtracting the fee
- * first overstates what they receive. A built transaction carries the fee
- * explicitly, and it is zero until one lands (ENG-1718).
- *
- * Every method requires `AuthState === 'logged-in'` and throws
- * {@link NotAuthenticatedError} otherwise.
- */
-interface OndoNamespace {
-    getTradingStatus(params: GetOndoTradingStatusParams): Promise<OndoTradingStatus>;
-    /**
-     * An indicative price for `params`' size, from Ondo's live market.
-     *
-     * Ondo refuses to quote while the market is closed or paused, or the asset
-     * is paused or closed for the session - including for about a minute at
-     * every US session change, when `getTradingStatus` may still have reported
-     * the asset tradable. The request then rejects with a 409 carrying
-     * `code: "not_tradable"`; tell it apart from a failure with
-     * {@link isOndoNotTradableError}. Retrying before the market opens fails the
-     * same way.
-     */
-    getQuote(params: GetOndoQuoteParams): Promise<OndoQuote>;
-    /**
-     * Builds a purchase for a specific wallet and deposit: spends an attestation
-     * and returns calldata to broadcast, valid until
-     * {@link OndoBuyTransaction.expiresAt}.
-     *
-     * The wallet must have approved the swap contract to spend `amount` of the
-     * offer's **funding token** first. Frontline reads that allowance before
-     * asking Ninshubur for anything, and rejects a short one with a 422 carrying
-     * `code: "insufficient_allowance"`. See `prepareBuy` on the client
-     * namespace, which approves and then builds, in that order.
-     *
-     * The tokens themselves are the offer's rather than the caller's to name.
-     */
-    buildBuyTransaction(params: BuildOndoBuyParams): Promise<OndoBuyTransaction>;
-    /**
-     * Builds a sale for a specific wallet and quantity: spends an attestation
-     * and returns calldata to broadcast, valid until
-     * {@link OndoSellTransaction.expiresAt}.
-     *
-     * The approval this one needs is on the **asset**, not on a stablecoin - a
-     * sale delivers the asset, so the swap contract pulls it with `transferFrom`
-     * exactly as it pulls the deposit on a purchase. Same 422 when it is short,
-     * with a message naming that address. See `prepareSell` on the client
-     * namespace.
-     *
-     * Returns a range rather than a quantity: Ondo settles through USDon before
-     * converting to the settlement token, so disclose
-     * {@link OndoSellTransaction.minimum} and not only `expected`.
-     */
-    buildSellTransaction(params: BuildOndoSellParams): Promise<OndoSellTransaction>;
-}
-declare class OndoNamespaceImpl implements OndoNamespace {
-    private readonly ctx;
-    protected readonly log: InternalLogger;
-    constructor(ctx: UniversalNamespaceContext);
-    getTradingStatus(params: GetOndoTradingStatusParams): Promise<OndoTradingStatus>;
-    getQuote(params: GetOndoQuoteParams): Promise<OndoQuote>;
-    buildBuyTransaction(params: BuildOndoBuyParams): Promise<OndoBuyTransaction>;
-    buildSellTransaction(params: BuildOndoSellParams): Promise<OndoSellTransaction>;
-}
-
-/**
- * Raw JSON models for the Superstate swap endpoints that are still backend
- * calls.
- *
- * The contract *reads* no longer have DTOs: the SDK calls `status()`,
- * `preview()`, `authorized()` and `outputToken()` on-chain through
- * `@/universal/api/rpc`, so their wire shape is the ABI rather than JSON.
- * Allow-listing a wallet stays here because it is a backend write, not a read.
- */
-type AllowWalletResponseDto = {
-    action: 'broadcast_transaction';
-    to: string;
-    data: string;
-} | {
-    action: 'none';
-    already_allowed: boolean;
-};
-
-/**
- * A read-only quote for a swap: how much goes in, the protocol fee, and how
- * much would come out. All amounts are raw on-chain integers (uint256).
- */
-type SwapPreview = {
-    inputAmount: Uint256;
-    fee: Uint256;
-    outputAmount: Uint256;
-};
-declare const SwapPreview: {
-    /** Maps the contract's `Preview { input, fee, output }` struct. */
-    fromContract: (preview: {
-        input: bigint;
-        fee: bigint;
-        output: bigint;
-    }) => SwapPreview;
-};
-/**
- * The bitmask of operations a swap contract has paused, as `Operable.paused`
- * reports it. Each bit is one operation level; swapping is
- * {@link SWAP_LEVEL}.
- *
- * Meaningful only while the contract is paused, which is why it lives on that
- * arm of {@link SwapStatus} alone: an active contract has nothing paused, and
- * a stopped one is past caring which level was.
- */
-type PauseFlags = Newtype<number, 'PauseFlags'>;
-declare const PauseFlags: (value: number) => PauseFlags;
-/**
- * The on-chain state of a swap contract, as `status()` reports it.
- *
- * - `active` - operating normally.
- * - `paused` - one or more operations are suspended, and may be resumed.
- *   `pausedLevels` says which. **This does not by itself mean swapping is
- *   down**: a contract can pause an unrelated operation and keep swapping.
- *   Ask `isSwapAvailable` rather than reading the state.
- * - `stopped` - permanently halted, and cannot be reactivated.
- */
-type SwapStatus = {
-    state: 'active';
-} | {
-    state: 'paused';
-    pausedLevels: PauseFlags;
-} | {
-    state: 'stopped';
-};
-declare const SwapStatus: {
-    /**
-     * Maps the contract's `Status { uint32 flags; State state }` struct, where
-     * `State` is `0 = Active | 1 = Paused | 2 = Stopped`.
-     *
-     * `flags` is carried onto the `paused` arm only. On the other two the
-     * contract sets it to a self-identifying marker rather than to information -
-     * so repeating it would invite a caller to read meaning into a constant.
-     *
-     * @throws ValidationError on a `state` outside the enum. A contract that has
-     * grown a fourth state is one the SDK does not model, and guessing `active`
-     * would let a halted swap read as a live one.
-     */
-    fromContract: (status: {
-        flags: number;
-        state: number;
-    }) => SwapStatus;
-};
-/**
- * The backend's response to an allow-wallet request. Either the caller must
- * broadcast an on-chain transaction to complete allow-listing, or nothing is
- * required because the wallet is already allowed.
- */
-type AllowWalletResponse = {
-    action: 'broadcast_transaction';
-    to: EvmContractAddress;
-    data: HexEncodedTransactionData;
-} | {
-    action: 'none';
-    alreadyAllowed: boolean;
-};
-declare const AllowWalletResponse: {
-    fromDto: (dto: AllowWalletResponseDto) => AllowWalletResponse;
-};
-
-/** Parameters shared by contract reads scoped to a chain. */
-type SwapContractRef = {
-    contractAddress: EvmContractAddress;
-    chain: EthereumChain;
-};
-type GetSwapAuthorizationParams = SwapContractRef & {
-    walletAddress: EvmWalletAddress;
-};
-type GetSwapPreviewParams = SwapContractRef & {
-    inputToken: EvmContractAddress;
-    amount: bigint;
-};
-type AllowWalletParams = {
-    offerId: OfferId;
-    walletAddress: EvmWalletAddress;
-    chain: EthereumChain;
-    signature: string;
-};
-
-/**
- * Read/write operations for the on-chain swap flow: quoting a swap, inspecting
- * contract state, and proving/allow-listing wallet ownership.
- *
- * Every read here is a contract call the SDK makes itself. By default those go
- * through CoinList's authenticated JSON-RPC proxy, so a logged-out caller gets
- * the proxy's `401` - surfaced as a viem error wrapping the SDK's `HttpError`,
- * not as `NotAuthenticatedError`, since viem re-wraps whatever a `Transport`
- * throws. Point `Config.rpc` at your own node for this chain and no CoinList
- * session is involved at all. `allowWallet` is the exception: it is a backend
- * write and always needs one, and throws `NotAuthenticatedError` without.
- */
-interface SuperstateSwapNamespace {
-    /**
-     * Checks whether a wallet is authorized to swap against the given contract.
-     */
-    getAuthorization(params: GetSwapAuthorizationParams): Promise<boolean>;
-    /**
-     * Fetches a read-only quote for swapping `amount` of `inputToken`.
-     *
-     * The contract reverts rather than quoting when it is stopped, or when
-     * `inputToken` is not one it accepts, so this surfaces a viem
-     * `ContractFunctionRevertedError` naming the contract's own error. Check
-     * {@link getStatus} first if you would rather not provoke one.
-     */
-    getPreview(params: GetSwapPreviewParams): Promise<SwapPreview>;
-    /**
-     * Reads the current on-chain state of a swap contract. See
-     * {@link isSwapAvailable} before concluding that a `paused` contract cannot
-     * swap - the two are not the same question.
-     */
-    getStatus(params: SwapContractRef): Promise<SwapStatus>;
-    /**
-     * Reads the ERC-20 output token a swap contract pays out, with its metadata.
-     */
-    getOutputToken(params: SwapContractRef): Promise<Erc20Asset>;
-    /**
-     * Submits a signed wallet-ownership challenge to allow-list the wallet for
-     * an offer, identified by its offer id. Obtain the challenge from
-     * `WalletsNamespace.createOwnershipChallenge`.
-     *
-     * @throws NotAuthenticatedError without a logged-in user.
-     */
-    allowWallet(params: AllowWalletParams): Promise<AllowWalletResponse>;
-}
-declare class SuperstateSwapNamespaceImpl implements SuperstateSwapNamespace {
-    private readonly ctx;
-    protected readonly log: InternalLogger;
-    constructor(ctx: UniversalNamespaceContext);
-    getAuthorization(params: GetSwapAuthorizationParams): Promise<boolean>;
-    getPreview(params: GetSwapPreviewParams): Promise<SwapPreview>;
-    getStatus(params: SwapContractRef): Promise<SwapStatus>;
-    getOutputToken(params: SwapContractRef): Promise<Erc20Asset>;
-    allowWallet(params: AllowWalletParams): Promise<AllowWalletResponse>;
-}
-
-/** Request body for `POST /v1/offers/:offer_id/addresses`. */
-type CreateOfferOptionAddressDto = {
-    offer_option_id: string;
-    wallet_address: string;
-    chain: string;
-    signature: string;
-};
-/** Binding object returned by the `/v1/offers/:offer_id/addresses` resource. */
-type OfferOptionAddressDto = {
-    id: string;
-    offer_option_id: string;
-    address: string;
-    protocol: WalletProtocol;
-    created_at: string;
-};
-
-/** Unique identifier for a proven wallet binding on an offer option. */
-type OfferOptionAddressId = Newtype<string, 'OfferOptionAddressId'>;
-/** Casts a string into a typed {@link OfferOptionAddressId}. */
-declare const OfferOptionAddressId: (value: string) => OfferOptionAddressId;
-/**
- * A user's external wallet, proven via a wallet-ownership challenge and bound
- * to an offer option. Returned by the `/v1/offers/:offer_id/addresses` resource.
- */
-type OfferOptionAddress = {
-    /** Unique binding id. */
-    id: OfferOptionAddressId;
-    /** Offer option the wallet is bound to. */
-    offerOptionId: OfferOptionId;
-    /** The connected external wallet address. */
-    address: EvmWalletAddress;
-    /**
-     * Protocol the binding is scoped to. An EVM address binds once per option
-     * regardless of which EVM chain proved ownership.
-     */
-    protocol: WalletProtocol;
-    /** When the binding was created. */
-    createdAt: Date;
-};
-declare const OfferOptionAddress: {
-    /** Maps the API DTO into the SDK offer-option-address domain model. */
-    fromDto: (dto: OfferOptionAddressDto) => OfferOptionAddress;
-};
-/** Parameters required to connect a proven external wallet to an offer option. */
-type ConnectExternalWalletParams = {
-    /** Offer the option belongs to. */
-    offerId: OfferId;
-    /** Offer option to bind the wallet to. */
-    offerOptionId: OfferOptionId;
-    /** External wallet address that was proven. */
-    walletAddress: EvmWalletAddress;
-    /** Chain the ownership was proven on. */
-    chain: EthereumChain;
-    /** Signature of the wallet-ownership challenge message. */
-    signature: Hex;
-};
-declare const ConnectExternalWalletParams: {
-    /** Maps connect-wallet params into the API DTO payload. */
-    toDto: (params: ConnectExternalWalletParams) => CreateOfferOptionAddressDto;
-};
-
-/** Challenge kinds accepted by `POST /v1/wallet-ownership`. */
-type WalletOwnershipChallengeTypeDto = 'plain' | 'siwe';
-/**
- * Request body for `POST /v1/wallet-ownership`. `challenge_type` defaults to
- * `plain` on the backend; the SIWE fields (`domain`, `uri`, `statement`) are
- * required only when `challenge_type` is `siwe` and must be absent otherwise.
- */
-type CreateWalletOwnershipChallengeDto = {
-    wallet_address: string;
-    chain: string;
-    challenge_type?: WalletOwnershipChallengeTypeDto;
-    domain?: string;
-    uri?: string;
-    statement?: string;
-};
-/** Response body for `POST /v1/wallet-ownership`. */
-type WalletOwnershipChallengeDto = {
-    message: string;
-    expires_at: string;
-};
-
-/** Fields common to every wallet-ownership challenge request. */
-type WalletOwnershipChallengeParamsBase = {
-    /** Wallet address to prove ownership of. */
-    walletAddress: EvmWalletAddress;
-    /** Chain the wallet belongs to. */
-    chain: EthereumChain;
-};
-/**
- * How the ownership challenge is framed: a plain message or a Sign-In With
- * Ethereum challenge. Extracted as its own type so SDK consumers can pass it as
- * a standalone param without reaching into the {@link CreateWalletOwnershipChallengeParams}
- * union.
- */
-type WalletChallengeType = CreateWalletOwnershipChallengeParams['challengeType'];
-/**
- * A single-use ownership challenge returned by `POST /v1/wallet-ownership`.
- * The consumer signs {@link message} with their wallet, then submits the
- * signature to connect the wallet to an offer option.
- */
-type WalletOwnershipChallenge = {
-    /** The message the wallet must sign. */
-    message: string;
-    /** When the challenge expires and can no longer be consumed. */
-    expiresAt: Date;
-};
-declare const WalletOwnershipChallenge: {
-    /** Maps the API DTO into the SDK wallet-ownership-challenge domain model. */
-    fromDto: (dto: WalletOwnershipChallengeDto) => WalletOwnershipChallenge;
-};
-/**
- * Parameters for requesting a wallet-ownership challenge. Modeled as a
- * discriminated union on `challengeType` so a `siwe` challenge must carry
- * `domain`/`uri`/`statement`, matching the backend contract at compile time.
- */
-type CreateWalletOwnershipChallengeParams = (WalletOwnershipChallengeParamsBase & {
-    /** A bare message the wallet signs. */
-    challengeType: 'plain';
-}) | (WalletOwnershipChallengeParamsBase & {
-    /** Marks this as a Sign-In With Ethereum challenge. */
-    challengeType: 'siwe';
-    /** The requesting site's hostname (e.g. `example.com`). */
-    domain: string;
-    /** The requesting site's URI. */
-    uri: string;
-    /** Human-readable statement shown in the signing prompt. */
-    statement: string;
-});
-declare const CreateWalletOwnershipChallengeParams: {
-    /**
-     * Maps challenge-request params into the API DTO payload. The discriminated
-     * union guarantees SIWE fields are present exactly when `challengeType` is
-     * `siwe`, so the mapping narrows on the discriminant.
-     */
-    toDto: (params: CreateWalletOwnershipChallengeParams) => CreateWalletOwnershipChallengeDto;
-};
-
-type ListOptionAddressesParams = {
-    offerId: OfferId;
-    /** Offer option whose bindings to list. */
-    offerOptionId: OfferOptionId;
-};
-type RemoveOptionAddressParams = {
-    offerId: OfferId;
-    /** Binding to remove, as returned by {@link WalletsNamespace.list}. */
-    addressId: OfferOptionAddressId;
-};
-/**
- * The user's external wallets: proving ownership of one, binding it to an
- * offer option, and managing those bindings.
- *
- * Ownership proof is a provider-agnostic primitive — the swap flow uses the
- * same challenge to allow-list a wallet — so it lives here rather than being
- * duplicated per product namespace.
- *
- * Every method requires an authenticated user and throws
- * {@link NotAuthenticatedError} otherwise.
- */
-interface WalletsNamespace {
-    /**
-     * Creates a single-use challenge the user signs to prove they control a
-     * wallet. Supports both `plain` and `siwe` challenges. Pass the signature of
-     * the returned {@link WalletOwnershipChallenge.message} to
-     * {@link connectExternal}.
-     */
-    createOwnershipChallenge(params: CreateWalletOwnershipChallengeParams): Promise<WalletOwnershipChallenge>;
-    /**
-     * Binds a proven external wallet to an offer option, using a signature of a
-     * challenge from {@link createOwnershipChallenge}.
-     */
-    connectExternal(params: ConnectExternalWalletParams): Promise<OfferOptionAddress>;
-    /**
-     * Lists the user's proven wallet bindings for one offer option — the single
-     * bound address for an `external_wallet` option, or every allow-listed
-     * wallet for a `whitelisted_wallet` option.
-     */
-    list(params: ListOptionAddressesParams): Promise<OfferOptionAddress[]>;
-    /**
-     * Removes one of the user's wallet bindings and returns the removed binding.
-     */
-    remove(params: RemoveOptionAddressParams): Promise<OfferOptionAddress>;
-}
-declare class WalletsNamespaceImpl implements WalletsNamespace {
-    private readonly ctx;
-    private readonly log;
-    constructor(ctx: UniversalNamespaceContext);
-    createOwnershipChallenge(params: CreateWalletOwnershipChallengeParams): Promise<WalletOwnershipChallenge>;
-    connectExternal(params: ConnectExternalWalletParams): Promise<OfferOptionAddress>;
-    list(params: ListOptionAddressesParams): Promise<OfferOptionAddress[]>;
-    remove(params: RemoveOptionAddressParams): Promise<OfferOptionAddress>;
-}
-
-type DocumentSubmissionStatusDto = 'INITIALIZED' | 'SENT' | 'VIEWED' | 'COMPLETED' | 'DECLINED' | 'EXPIRED';
-type DocumentFormTypeDto = 'w8_ben' | 'w8_ben_e';
-type DocumentSubmissionDto = {
-    object: 'document_submission';
-    status: DocumentSubmissionStatusDto;
-    form_type: DocumentFormTypeDto;
-};
-
-/** Document types that can be signed via {@link CoinListClient.submitDocument}. */
-type DocumentType = 'tax_certification';
-/** Signing-state machine status for a document submission. */
-type DocumentSubmissionStatus = DocumentSubmissionStatusDto;
-/** The tax form derived from the entity's kind (individual vs company/trust). */
-type DocumentFormType = DocumentFormTypeDto;
-/** Result of starting (or resuming) a document signing submission. */
-type DocumentSubmission = {
-    status: DocumentSubmissionStatus;
-    formType: DocumentFormType;
-};
-declare const DocumentSubmission: {
-    fromDto: (dto: DocumentSubmissionDto) => DocumentSubmission;
-};
-
-type KycTokenDto = {
-    object: 'kyc_token';
-    token: string;
-};
-
-/**
- * Sumsub verification level name. Determines which screens the Sumsub WebSDK
- * shows (levels are configured in the Sumsub dashboard). The backend
- * prescribes the level (and whether the applicant must be reset first) in the
- * requirement statuses response — clients never compute levels themselves.
- */
-type KycLevelName = string;
-/** Short-lived Sumsub WebSDK access token scoped to the current user. */
-type KycToken = {
-    token: string;
-};
-declare const KycToken: {
-    fromDto: (dto: KycTokenDto) => KycToken;
-};
-
-type PiiKindDto = 'person' | 'company';
-type PiiJurisdictionDto = {
-    iso_2: string;
-    name: string | null;
-};
-type PiiAddressDto = {
-    street: string | null;
-    city: string | null;
-    state: string | null;
-    postal_code: string | null;
-    country: string | null;
-};
-type PiiDto = {
-    object: 'user_pii';
-    kind: PiiKindDto;
-    full_legal_name: string | null;
-    date_of_birth: string | null;
-    jurisdiction: PiiJurisdictionDto | null;
-    tax_id: string | null;
-    permanent_address: PiiAddressDto;
-};
-
-/** Whether the PII belongs to an individual or a company/trust entity. */
-type PiiKind = PiiKindDto;
-/** ISO 3166-1 alpha-2 country code (e.g. `'US'`). */
-type Iso2CountryCode = Newtype<string, 'Iso2CountryCode'>;
-declare const Iso2CountryCode: (value: string) => Iso2CountryCode;
-/** Jurisdiction derived from the entity's address country. */
-type PiiJurisdiction = {
-    iso2: Iso2CountryCode;
-    name: string | null;
-};
-declare const PiiJurisdiction: {
-    fromDto: (dto: PiiJurisdictionDto) => PiiJurisdiction;
-};
-/** Permanent address on file for the entity. */
-type PiiAddress = {
-    street: string | null;
-    city: string | null;
-    state: string | null;
-    postalCode: string | null;
-    country: string | null;
-};
-declare const PiiAddress: {
-    fromDto: (dto: PiiAddressDto) => PiiAddress;
-};
-/**
- * The current user's PII, used to pre-fill tax forms such as the W-8BEN.
- * Fields the entity hasn't provided are `null`.
- */
-type Pii = {
-    kind: PiiKind;
-    fullLegalName: string | null;
-    dateOfBirth: string | null;
-    jurisdiction: PiiJurisdiction | null;
-    taxId: string | null;
-    permanentAddress: PiiAddress;
-};
-declare const Pii: {
-    fromDto: (dto: PiiDto) => Pii;
-};
-
-type RequirementTypeDto = 'kyc_approved' | 'external_wallet' | 'whitelisted_wallet' | 'jurisdiction' | 'accreditation' | 'document';
-type RequirementDto = {
-    object: 'requirement';
-    id: string;
-    type: RequirementTypeDto;
-    details: Record<string, unknown> | null;
-};
-type RequirementStatusValueDto = 'not_started' | 'in_progress' | 'action_needed' | 'completed' | 'rejected';
-type RequirementActionNeededReasonDto = 'kyc_not_verified' | 'update_pii_data';
-/**
- * Object form of a requirement status, used when the status carries extra
- * data: the action-needed reason and/or the Sumsub flow that resolves the
- * requirement (kyc_level + kyc_reset, forwarded to the kyc-token endpoint).
- */
-type RequirementStatusObjectDto = {
-    status: RequirementStatusValueDto;
-    action?: RequirementActionNeededReasonDto;
-    kyc_level?: string;
-    kyc_reset?: boolean;
-};
-type RequirementStatusesDto = {
-    object: 'requirement_statuses';
-    offer_id: string;
-    statuses: Record<string, RequirementStatusValueDto | RequirementStatusObjectDto>;
-};
-
-type RequirementId = Newtype<string, 'RequirementId'>;
-declare const RequirementId: (value: string) => RequirementId;
-type RequirementType = RequirementTypeDto;
-type RequirementStatusValue = RequirementStatusValueDto;
-type RequirementActionNeededReason = RequirementActionNeededReasonDto;
-type Requirement = {
-    id: RequirementId;
-    type: RequirementType;
-    details: Record<string, unknown> | null;
-};
-declare const Requirement: {
-    fromDto: (dto: RequirementDto) => Requirement;
-};
-type RequirementStatusInfo = {
-    id: RequirementId;
-    status: RequirementStatusValue;
-    /** Why the requirement needs action (KYC-backed requirements only). */
-    action: RequirementActionNeededReason | null;
-    /**
-     * The Sumsub verification level that resolves this requirement, prescribed
-     * by the backend. Present exactly when an inline Sumsub flow can be started.
-     */
-    kycLevel?: KycLevelName;
-    /**
-     * Whether the Sumsub applicant must be reset before starting the flow
-     * (redoing an already-approved level, e.g. to update stale PII). Forward to
-     * the kyc-token request as-is.
-     */
-    kycReset?: boolean;
-};
-declare const RequirementStatusInfo: {
-    fromStatusesDto: (dto: RequirementStatusesDto) => RequirementStatusInfo[];
-};
-
-type CreateKycTokenParams = {
-    /**
-     * Sumsub verification level to run. Defaults to the backend's standard
-     * level.
-     */
-    levelName?: KycLevelName;
-    /**
-     * Resets the Sumsub applicant first, so an already-approved level can be
-     * executed again (e.g. to update stale PII). Pass the `kycReset` value from
-     * the requirement status, and never on mid-flow token refreshes.
-     */
-    reset?: boolean;
-};
-type SubmitDocumentParams = {
-    /** Currently only `tax_certification` (W-8BEN / W-8BEN-E). */
-    documentType: DocumentType;
-    /**
-     * Signing-form values keyed by the document's DocuSeal field names,
-     * forwarded verbatim to pre-fill the document.
-     */
-    fields: Record<string, string>;
-};
-/**
- * Everything a user must satisfy before they can participate in an offer:
- * reading the checklist and its live statuses, and the operations that satisfy
- * individual requirements — identity verification (KYC) and tax-document
- * signing.
- *
- * Wallet requirements (`external_wallet`, `whitelisted_wallet`) are satisfied
- * through `WalletsNamespace` instead, since wallet proofs are also used
- * outside the requirements flow.
- *
- * Every method requires an authenticated user and throws
- * {@link NotAuthenticatedError} otherwise.
- */
-interface RequirementsNamespace {
-    /**
-     * Fetches the requirements for every option of an offer, grouped by option
-     * id. This is the definition of the checklist; {@link statuses} tells you
-     * where the user stands against it.
-     */
-    forOffer(offerId: OfferId): Promise<Record<OfferOptionId, Requirement[]>>;
-    /**
-     * Fetches the current user's status for each requirement of an offer.
-     */
-    statuses(offerId: OfferId): Promise<RequirementStatusInfo[]>;
-    /**
-     * Creates a short-lived Sumsub WebSDK access token so an identity
-     * verification (KYC) flow can be started, e.g. by the `IdentityVerification`
-     * component.
-     */
-    createKycToken(params?: CreateKycTokenParams): Promise<KycToken>;
-    /**
-     * Fetches the current user's PII, used to pre-fill tax forms such as the
-     * W-8BEN. Fields the entity hasn't provided are `null`.
-     */
-    getPii(): Promise<Pii>;
-    /**
-     * Starts (or resumes) a document signing submission.
-     */
-    submitDocument(params: SubmitDocumentParams): Promise<DocumentSubmission>;
-}
-declare class RequirementsNamespaceImpl implements RequirementsNamespace {
-    protected readonly ctx: UniversalNamespaceContext;
-    protected readonly log: InternalLogger;
-    constructor(ctx: UniversalNamespaceContext);
-    forOffer(offerId: OfferId): Promise<Record<OfferOptionId, Requirement[]>>;
-    statuses(offerId: OfferId): Promise<RequirementStatusInfo[]>;
-    createKycToken(params?: CreateKycTokenParams): Promise<KycToken>;
-    getPii(): Promise<Pii>;
-    submitDocument(params: SubmitDocumentParams): Promise<DocumentSubmission>;
-}
-
-/**
- * Reads over CoinList's offers: the catalogue a user can browse, and the full
- * detail of a single offer.
- *
- * Every method requires an authenticated user and throws
- * {@link NotAuthenticatedError} otherwise. On the server, the same reads are
- * additionally available with an app-level token — see
- * `ServerOffersNamespace`.
- */
-interface OffersNamespace {
-    /**
-     * Fetches every offer, iterating through all pages. Prefer {@link listPage}
-     * when you render a paginated list yourself.
-     */
-    list(): Promise<Offer[]>;
-    /**
-     * Fetches a single page of offers. Pass the previous response's
-     * `startingAfter` as `after` to advance.
-     */
-    listPage(params: PaginationParams): Promise<PaginatedResponse<Offer>>;
-    /**
-     * Fetches the full detail of one offer, including its options. Note this
-     * returns {@link OfferDetail} — a richer model than the {@link Offer}
-     * summaries {@link list} returns.
-     */
-    get(id: OfferId): Promise<OfferDetail>;
-}
-declare class OffersNamespaceImpl implements OffersNamespace {
-    private readonly ctx;
-    private readonly log;
-    constructor(ctx: UniversalNamespaceContext);
-    list(): Promise<Offer[]>;
-    listPage(params: PaginationParams): Promise<PaginatedResponse<Offer>>;
-    get(id: OfferId): Promise<OfferDetail>;
-}
-
-/**
- * Raw JSON from the token registry (Nabu), a static CDN serving token display
- * metadata. It is a separate backend from frontline: responses omit optional
- * fields rather than sending `null`, and may grow unknown fields at any time;
- * we only read the fields named here.
- */
-type NabuLogoImageDto = {
-    url: string;
-    width: number;
-    height: number;
-};
-/**
- * A logo is either a single vector (valid at any size) or a dimensioned
- * raster original plus pre-scaled variants at ascending widths.
- */
-type NabuLogoDto = {
-    kind: 'VECTOR';
-    url: string;
-} | {
-    kind: 'RASTER';
-    original: NabuLogoImageDto;
-    variants: NabuLogoImageDto[];
-};
-/** One token from the registry's `/{chain}/token/{address}` route. */
-type NabuTokenDto = {
-    data_version: string;
-    schema_version: number;
-    chain: string;
-    protocol: string;
-    chain_id: number;
-    kind: string;
-    name: string;
-    symbol: string;
-    decimals: number;
-    logo: NabuLogoDto;
-    logo_dark?: NabuLogoDto;
-    coingecko_id?: string;
-    teller_code?: string;
-    address: string;
-};
-/**
- * One asset inside a chain snapshot. The snapshot mixes the chain's native
- * coin (`kind: 'COIN'`, no address) with its tokens (`kind: 'TOKEN'`), so
- * `address` is optional here where {@link NabuTokenDto} requires it.
- */
-type NabuChainAssetDto = {
-    kind: string;
-    name: string;
-    symbol: string;
-    decimals: number;
-    logo: NabuLogoDto;
-    logo_dark?: NabuLogoDto;
-    address?: string;
-};
-/** The registry's `/{chain}/assets.json` route: one chain, all its assets. */
-type NabuChainAssetsDto = {
-    data_version: string;
-    schema_version: number;
-    chain: string;
-    protocol: string;
-    assets: NabuChainAssetDto[];
-};
-/** The registry's `/assets.json` route: the complete snapshot, every chain. */
-type NabuRegistryDto = {
-    data_version: string;
-    schema_version: number;
-    chains: Array<{
-        chain: string;
-        protocol: string;
-        assets: NabuChainAssetDto[];
-    }>;
-};
-
-/**
- * An absolute URL to a logo image in the token registry. Registry image URLs
- * are content-fingerprinted and served immutable, so a value is safe to cache
- * for as long as you hold it.
- */
-type TokenLogoUrl = Newtype<string, 'TokenLogoUrl'>;
-declare const TokenLogoUrl: (value: string) => TokenLogoUrl;
-type TokenLogoImage = {
-    url: TokenLogoUrl;
-    width: number;
-    height: number;
-};
-/**
- * `VECTOR` is a single SVG. `RASTER` has webp variants at 32/64/128/256/512px
- * widths (never wider than the original): use the smallest one that covers
- * your render size, or `original` if none does.
- */
-type TokenLogo = {
-    kind: 'VECTOR';
-    url: TokenLogoUrl;
-} | {
-    kind: 'RASTER';
-    original: TokenLogoImage;
-    variants: TokenLogoImage[];
-};
-declare const TokenLogo: {
-    /** `baseUrl` is the registry origin; registry URLs are root-relative. */
-    fromDto: (dto: NabuLogoDto, baseUrl: string) => TokenLogo;
-};
-/**
- * Display metadata for one token, from CoinList's public token registry.
- *
- * Keyed by `(chain, address)` — never by symbol, which can collide. The
- * registry is curated: a token missing from it is an expected answer, not an
- * error, so lookups return `null` rather than throwing.
- */
-type TokenMetadata = {
-    identifier: TokenIdentifier;
-    name: string;
-    symbol: AssetSymbol;
-    decimals: AssetDecimals;
-    logo: TokenLogo;
-    /** Dark-theme logo; `null` when the registry configures none. */
-    logoDark: TokenLogo | null;
-};
-declare const TokenMetadata: {
-    /** `baseUrl` is the registry origin; registry logo URLs are root-relative. */
-    fromDto: (dto: NabuTokenDto, baseUrl: string) => TokenMetadata;
-    /**
-     * Maps the complete registry snapshot to every token it lists across the
-     * chains this SDK models, skipping native coins and chains outside
-     * {@link EthereumChain} (e.g. Solana) rather than failing on them — the
-     * registry may serve chains ahead of the SDK's type surface.
-     */
-    fromRegistryDto: (dto: NabuRegistryDto, baseUrl: string) => TokenMetadata[];
-    /**
-     * Maps a chain snapshot to the tokens it lists, skipping the chain's native
-     * coin (`kind: 'COIN'`, no contract address).
-     */
-    fromChainAssetsDto: (dto: NabuChainAssetsDto, baseUrl: string) => TokenMetadata[];
-};
-
-/**
- * Token display metadata — name, symbol, decimals, and logos — from
- * CoinList's public token registry, keyed by {@link TokenIdentifier} (the
- * same chain + address pairs `Offer.tokens` carries).
- *
- * Unlike the other namespaces, this one is public: no method requires an
- * authenticated user, and nothing here touches the CoinList API — reads go to
- * the registry's CDN.
- */
-interface TokensNamespace {
-    /**
-     * Fetches metadata for one token. Returns `null` when the registry does not
-     * list the token — the registry is curated, so callers must fall back to
-     * their own display defaults rather than treat this as an error.
-     */
-    get(token: TokenIdentifier): Promise<TokenMetadata | null>;
-    /**
-     * Fetches every token the registry lists, in one request: the complete
-     * snapshot with no `chain`, or one chain's snapshot with it. Prefer this
-     * over calling {@link get} in a loop when displaying a catalogue — two
-     * hundred tokens across three chains is still a single download.
-     *
-     * The complete snapshot spans every chain the registry knows; tokens on
-     * chains this SDK does not model (e.g. Solana) are left out of the result.
-     *
-     * Unlike {@link get}, a missing snapshot throws rather than returning `[]`:
-     * the registry always publishes the complete snapshot and one per chain it
-     * knows, so an absence is a deployment problem, not an empty catalogue.
-     */
-    list(chain?: EthereumChain): Promise<TokenMetadata[]>;
-}
-declare class TokensNamespaceImpl implements TokensNamespace {
-    private readonly api;
-    private readonly log;
-    /**
-     * Takes the registry origin rather than a `UniversalNamespaceContext`: the
-     * registry is unauthenticated and on its own host, so the frontline sender
-     * and the auth check would both be dead weight here.
-     */
-    constructor(baseUrl: string, logger?: Logger | null);
-    get(token: TokenIdentifier): Promise<TokenMetadata | null>;
-    list(chain?: EthereumChain): Promise<TokenMetadata[]>;
-}
-
-/**
- * An instant: milliseconds since the Unix epoch, as `Date.now()` reads it.
- * Distinct from {@link Millis}, a duration, so an instant cannot be passed
- * where a timeout is expected or the other way round.
- */
-type EpochMillis = Newtype<number, 'EpochMillis'>;
-declare const EpochMillis: {
-    /**
-     * @throws {@link ValidationError} unless `value` is an integer a `Date` can
-     * represent: at most {@link MAX_EPOCH_MILLIS} either side of the epoch.
-     */
-    of: (value: number) => EpochMillis;
-    /** The wall clock. Code that needs the time takes a `TimeEff` instead. */
-    now: () => EpochMillis;
-    /** @throws {@link ValidationError} for an invalid `Date`. */
-    fromDate: (date: Date) => EpochMillis;
-    /** How long after `from` the instant `to` is; negative if it is before. */
-    elapsed: (from: EpochMillis, to: EpochMillis) => Millis;
-    plus: (at: EpochMillis, duration: Millis) => EpochMillis;
-};
-/**
- * A duration in milliseconds. May be negative: the gap between two instants
- * read off a wall clock that stepped back in between.
- */
-type Millis = Newtype<number, 'Millis'>;
-declare const Millis: {
-    of: (value: number) => Millis;
-};
-/** A duration in whole, non-negative seconds. */
-type Seconds = Newtype<number, 'Seconds'>;
-declare const Seconds: {
-    /**
-     * @throws {@link ValidationError} unless `value` is a non-negative integer.
-     */
-    of: (value: number) => Seconds;
-    toMillis: (value: Seconds) => Millis;
-};
-/**
- * Whether `expiresAt` has passed at `now`, counting it as passed `buffer`
- * early. The boundary instant itself counts as expired.
- */
-declare function isExpired({ expiresAt, now, buffer, }: {
-    expiresAt: EpochMillis;
-    now: EpochMillis;
-    buffer?: Millis;
-}): boolean;
-
-export { AsyncOfferDetail as $, AuthorizationCode as A, BlockchainAmount as B, CodeVerifier as C, type OAuthAccessToken as D, type Erc20Namespace as E, type OffersNamespace as F, DecimalString as G, StablecoinSymbol as H, type Erc20Asset as I, OfferDetail as J, TokenMetadata as K, type Logger as L, type CentrifugeVaultOfferDetail as M, type OfferType as N, OfferVaultContract as O, Participation as P, type OndoSwapOfferDetail as Q, type RequirementsNamespace as R, type SuperstateSwapNamespace as S, type TokensNamespace as T, type UniversalNamespaceContext as U, type CoinListTokenSaleOfferDetail as V, type WalletError as W, type SuperstateSwapOfferDetail as X, CentrifugeVaultLegId as Y, Seconds as Z, type AsyncOfferType as _, EthereumChain as a, type CentrifugeVaultOffer as a$, Offer as a0, RequirementStatusInfo as a1, type RequirementType as a2, type RequirementStatusValue as a3, OfferOptionAddress as a4, RequirementId as a5, type KycLevelName as a6, DocumentSubmission as a7, type WalletChallengeType as a8, type PinoLoggerOptions as a9, type ProductionLogLevel as aA, RedactedWalletError as aB, type RequestId as aC, type RpcFailureReason as aD, type SafeEvent as aE, type SafeFields as aF, type UnredactedFields as aG, OAuthSession as aH, ClientCredentialsOAuth as aI, type Sender as aJ, PaginationParams as aK, PaginatedResponse as aL, ClientSecret as aM, OfferToken as aN, SwapStatus as aO, type Uint256 as aP, KnownAssetSymbol as aQ, type Newtype as aR, type AllowWalletParams as aS, AllowWalletResponse as aT, Asset as aU, AssetCode as aV, Blockchain as aW, type BuildOndoSwapParamsCore as aX, type CentrifugePositionStatus as aY, CentrifugeVaultClaimProceedsTransaction as aZ, CentrifugeVaultClaimTransaction as a_, AssetDecimals as aa, type BuildCentrifugeVaultBuyParams as ab, CentrifugeVaultQuote as ac, type CentrifugeOrderReason as ad, type CentrifugeOrderability as ae, OndoTradingStatus as af, type BuildOndoBuyParams as ag, type BuildOndoSellParams as ah, OndoQuote as ai, type OndoQuoteSize as aj, type TokenIdentifier as ak, CentrifugeVaultLeg as al, OfferOptionAddressId as am, CentrifugeVaultStatus as an, TokenLogo as ao, type DebugEvent as ap, type FrontlineEventId as aq, HttpError as ar, type HttpResponse as as, KycToken as at, type LogBinding as au, type LogBindings as av, type LogCause as aw, type LogLevel as ax, type LogScope as ay, type LogValue as az, EvmContractAddress as b, type RequirementActionNeededReason as b$, CentrifugeVaultPosition as b0, type CentrifugeVaultReason as b1, CentrifugeVaultRedeemPosition as b2, type CentrifugeVaultTransactionCore as b3, type CentrifugeWalletParams as b4, Chain as b5, ClientId as b6, CodeChallenge as b7, type CoinListTokenSaleOffer as b8, ConnectExternalWalletParams as b9, Milestone as bA, Millis as bB, OAuthRefreshToken as bC, type OfferBase as bD, type OfferDetailBase as bE, OfferEditorial as bF, OfferOption as bG, OfferOptionSlug as bH, OfferSlug as bI, OffersNamespaceImpl as bJ, type OndoQuoteDuration as bK, type OndoSellOutcome as bL, type OndoSwapOffer as bM, PKCEState as bN, type PaginatedResponseDto as bO, ParticipationId as bP, type ParticipationStatus as bQ, ParticipationsPaginationParams as bR, PauseFlags as bS, Pii as bT, PiiAddress as bU, PiiJurisdiction as bV, type PiiKind as bW, type QueryParamValue as bX, type QueryParamValues as bY, RedirectUri as bZ, type RemoveOptionAddressParams as b_, type CreateKycTokenParams as ba, CreateParticipationParams as bb, CreateWalletOwnershipChallengeParams as bc, Cursor as bd, type DocumentFormType as be, type DocumentSubmissionStatus as bf, type DocumentType as bg, ETHEREUM_CHAINS as bh, EpochMillis as bi, Erc20NamespaceImpl as bj, FaqItem as bk, type GetCentrifugeVaultQuoteParams as bl, type GetCentrifugeVaultStatusParams as bm, type GetOndoQuoteParams as bn, type GetOndoTradingStatusParams as bo, type GetSwapAuthorizationParams as bp, type GetSwapPreviewParams as bq, type GetTokenAllowanceParams as br, type GetTokenBalanceParams as bs, HexEncodedTransactionData as bt, Isin as bu, Iso2CountryCode as bv, Link as bw, type ListOptionAddressesParams as bx, MAX_ASSET_DECIMALS as by, MAX_UINT_256 as bz, type CentrifugeNamespace as c, type RpcConfig as c0, SOLANA_CHAINS as c1, STABLE_DECIMALS as c2, SolanaChain as c3, type SubmitDocumentParams as c4, type SuperstateSwapOffer as c5, type SwapContractRef as c6, SwapPreview as c7, TermItem as c8, Ticker as c9, type TokenLogoImage as ca, TokenLogoUrl as cb, type TokenRole as cc, TokensNamespaceImpl as cd, type Tx as ce, WalletAddress as cf, WalletOwnershipChallenge as cg, type WalletProtocol as ch, WalletsNamespaceImpl as ci, apiErrorCode as cj, assertUint256 as ck, isChain as cl, isExpired as cm, isOfferType as cn, parseUint256 as co, AssetSymbol as d, CentrifugeVaultBuyTransaction as e, type CentrifugeClaimDirection as f, CentrifugeNamespaceImpl as g, type CoinListTokenSaleNamespace as h, OfferId as i, OfferOptionId as j, AssetId as k, CoinListTokenSaleNamespaceImpl as l, type OndoNamespace as m, OfferSwapContract as n, OndoBuyTransaction as o, OndoSellTransaction as p, type OndoSwapTransactionCore as q, type OrderBookSide as r, OndoNamespaceImpl as s, type WalletsNamespace as t, Bps as u, EvmWalletAddress as v, SuperstateSwapNamespaceImpl as w, Requirement as x, RequirementsNamespaceImpl as y, type Config as z };