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

package/dist/token-registry-snapshot-B0xCp3GD.d.cts

@@ -1,245 +0,0 @@
-import { b6 as ClientId, bZ as RedirectUri, b7 as CodeChallenge, bN as PKCEState, C as CodeVerifier, v as EvmWalletAddress, a as EthereumChain, ce as Tx, B as BlockchainAmount, c7 as SwapPreview, aa as AssetDecimals, aR as Newtype, K as TokenMetadata, b5 as Chain, b as EvmContractAddress, aN as OfferToken } from './time-DJU6E8KK.cjs';
-import { Hex, Abi, Hash, TransactionReceipt } from 'viem';
-
-type PKCEParams = {
-    clientId: ClientId;
-    responseType: 'code';
-    redirectUri: RedirectUri;
-    codeChallenge: CodeChallenge;
-    codeChallengeMethod: 'S256';
-    state: PKCEState;
-    codeVerifier: CodeVerifier;
-};
-type PKCEConfig = {
-    clientId: ClientId;
-    redirectUri: RedirectUri;
-};
-/**
- * Generates PKCE parameters for an OAuth2 authorization code flow.
- * Pure crypto — no React, no DOM beyond Web Crypto API. Safe to use
- * in server-side code and Next.js middleware.
- */
-declare function generatePKCEParams(config: PKCEConfig): Promise<PKCEParams>;
-
-type WriteContractParams = {
-    abi: Abi;
-    address: `0x${string}`;
-    functionName: string;
-    args?: readonly unknown[];
-    value?: bigint;
-    chain: EthereumChain;
-};
-type BroadcastTxParams = Tx & {
-    chain: EthereumChain;
-};
-/**
- * The signing-only wallet capability: address + `signMessage`. This is all the
- * external-wallet ownership proof needs (see `useConnectWallet`), so hosts can
- * satisfy that flow without implementing on-chain capabilities. The richer
- * {@link EvmWallet} extends this for swap flows.
- *
- * SDK users implement this against their own wallet stack (e.g. viem, wagmi,
- * Privy). `signMessage` throws on failure and the SDK classifies it.
- */
-interface EvmSigner {
-    readonly address: EvmWalletAddress;
-    signMessage(message: string): Promise<Hex>;
-}
-/**
- * The full on-chain wallet the SDK needs to run the swap flows: an
- * {@link EvmSigner} plus contract writes, raw-tx broadcast, and confirmation.
- * SDK users implement this against their own wallet stack (e.g. viem, wagmi,
- * Privy).
- *
- * Methods throw on failure. The SDK catches and classifies the thrown error
- * (viem's `UserRejectedRequestError`, `InsufficientFundsError`, timeouts, …)
- * into a typed {@link WalletError}, so implementers can simply let their wallet
- * library's errors propagate.
- */
-interface EvmWallet extends EvmSigner {
-    writeContract(params: WriteContractParams): Promise<Hash>;
-    broadcastRawTx(params: BroadcastTxParams): Promise<Hash>;
-    awaitTx(hash: Hash, chain: EthereumChain): Promise<TransactionReceipt>;
-}
-/**
- * The host-provided wallet the ownership flow signs with: the signing-only
- * {@link EvmSigner} plus the {@link EthereumChain} the signature is proven on.
- * `chain` rides on the wallet (not the offer) because the binding is
- * chain-agnostic: it only records which EVM chain signed.
- */
-type ConnectWallet = EvmSigner & {
-    readonly chain: EthereumChain;
-};
-/**
- * The host's connector for an external wallet, as two lambdas: one opens it,
- * one tears the connection down. The SDK ships no wallet stack, so this is how
- * a screen offers "Connect wallet" without knowing whether AppKit, Privy or the
- * host's own modal is behind it.
- *
- * One product type rather than two optional lambdas, because they come as a
- * pair: a screen that can connect a wallet must be able to let it go again,
- * and a host that supports neither passes `null` for the whole adapter, which
- * hides the connect affordance entirely.
- */
-type ExternalWalletAdapter = {
-    /**
-     * Opens the host's wallet connector. Resolves once the attempt finishes; the
-     * SDK reads the outcome from the external wallet it is handed on the next
-     * render rather than from a return value, so a host that connects through a
-     * redirect still works.
-     *
-     * Rejecting is how a declined or failed connection is reported.
-     */
-    connect: () => Promise<void>;
-    /** Disconnects the external wallet. Resolves when it is gone. */
-    disconnect: () => Promise<void>;
-};
-
-/**
- * A read-only quote for a swap as domain amounts: how much goes in, the
- * protocol fee, and how much would come out. Derived from the raw
- * {@link SwapPreview} the swap contract returns.
- */
-type SwapQuote = {
-    inputTokenAmount: BlockchainAmount;
-    fee: BlockchainAmount;
-    outputTokenAmount: BlockchainAmount;
-};
-declare const SwapQuote: {
-    /**
-     * Assembles a {@link SwapQuote} from a raw contract {@link SwapPreview}. The
-     * input and fee are denominated in the input token; the output in the output
-     * token.
-     */
-    fromPreview: (preview: SwapPreview, inputDecimals: AssetDecimals, outputDecimals: AssetDecimals) => SwapQuote;
-};
-
-type FormattedAmountUi = Newtype<string, 'FormattedAmountUi'>;
-declare const FormattedAmountUi: (value: string) => FormattedAmountUi;
-type FormattedPercentUi = Newtype<string, 'FormattedPercentUi'>;
-declare const FormattedPercentUi: (value: string) => FormattedPercentUi;
-type TxExplorerUrl = Newtype<string, 'TxExplorerUrl'>;
-declare const TxExplorerUrl: (value: string) => TxExplorerUrl;
-/**
- * A wallet address shortened for display (e.g. `0x1234…5678`). Keeps a
- * `0x${string}` base but drops the runtime `0x` narrowing.
- */
-type ShortenedWalletAddress = Newtype<`0x${string}`, 'ShortenedWalletAddress'>;
-declare const ShortenedWalletAddress: (value: string) => ShortenedWalletAddress;
-type FormattedAmountAssetUi = Newtype<string, 'FormattedAmountAssetUi'>;
-declare const FormattedAmountAssetUi: (value: string) => FormattedAmountAssetUi;
-type AssetIconUrl = Newtype<string, 'AssetIconUrl'>;
-declare const AssetIconUrl: (value: string) => AssetIconUrl;
-
-/**
- * The wallets a screen reads for and acts from, supplied by the host.
- *
- * The SDK ships no wallet stack, so wallet discovery and connection are
- * inverted onto the host: it hands over ready {@link EvmWallet}s, and an
- * adapter for connecting an external one when it supports that. Every wallet
- * here is one that can sign for itself, so a screen can broadcast from the
- * wallet that holds a position.
- */
-type WalletSelection = {
-    /**
-     * The user's embedded (custodial) wallets, in display order. Empty when
-     * they have none, which is a normal state, not an error.
-     */
-    embedded: EvmWallet[];
-    /** The connected external wallet, or `null` while none is connected. */
-    external: EvmWallet | null;
-    /**
-     * The host's external-wallet connector, or `null` when it offers none - in
-     * which case the screen shows no connect affordance at all. A host may
-     * still pass a connected `external` without one, to show a wallet the user
-     * cannot change from here.
-     */
-    externalAdapter: ExternalWalletAdapter | null;
-};
-declare const WalletSelection: {
-    /**
-     * Every wallet in display order - embedded first, then the external one -
-     * each address once. Addresses compare case-insensitively, so a host that
-     * hands the same wallet over as both embedded and external sees it once.
-     */
-    all: (selection: WalletSelection) => EvmWallet[];
-};
-/**
- * Names a wallet for display, e.g. `'CoinList Wallet'` for the user's
- * embedded one. `null` means it has no name, and the screen shows its
- * shortened address instead.
- */
-type WalletLabelResolver = (address: EvmWalletAddress) => string | null;
-
-/**
- * An array guaranteed to hold at least one element. Use it where an empty list
- * would be a bug (e.g. the set of assets a swap always offers).
- */
-type NonEmptyArray<T> = [T, ...T[]];
-
-/**
- * A token as a lookup names it. `Chain` rather than `EthereumChain` because
- * `OfferToken.chain` is the wider type; a Solana entry simply never matches,
- * since the snapshot models EVM chains only.
- */
-type TokenKey = {
-    chain: Chain;
-    address: EvmContractAddress;
-};
-/**
- * One `coinlist.tokens.list()` answer, indexed for the lookups a catalogue
- * makes: by the `(chain, address)` pairs `Offer.tokens` carries.
- *
- * The registry is fetched whole - a few hundred tokens across every chain in
- * one request - and then asked one question per offer. Building the index
- * once is what keeps that a map lookup per card rather than a scan of the
- * snapshot per card. The same rule frontline-web and every other host wrote
- * for themselves, kept here so that none of them has to.
- */
-type TokenRegistrySnapshot = {
-    /** Every token the snapshot lists, in registry order. */
-    readonly tokens: readonly TokenMetadata[];
-    /** `chain:address` (address lowercased) to its metadata. */
-    readonly byKey: ReadonlyMap<string, TokenMetadata>;
-};
-declare const TokenRegistrySnapshot: {
-    /** Indexes a `tokens.list()` result. `[]` is a valid, empty snapshot. */
-    fromTokens: (tokens: readonly TokenMetadata[]) => TokenRegistrySnapshot;
-    /**
-     * The registry's entry for one token, or `null` when it lists none. The
-     * registry is curated, so `null` is an ordinary answer rather than an
-     * error, and callers fall back to their own display defaults.
-     */
-    get: (snapshot: TokenRegistrySnapshot, token: TokenKey) => TokenMetadata | null;
-    /**
-     * The registry's entry for the token an offer is *about*, or `null` when
-     * it lists none of them.
-     *
-     * Resolution follows {@link offerDisplayTokens}: the token a sale
-     * distributes or a swap hands over, never the funding token the user pays
-     * with. An offer deployed on several chains carries one such token per
-     * chain, and the first the registry knows wins - they are the same asset,
-     * so any listed one answers for the offer.
-     */
-    forOffer: (snapshot: TokenRegistrySnapshot, offer: {
-        tokens: readonly OfferToken[];
-    }) => TokenMetadata | null;
-};
-/**
- * The tokens an offer is *about*, most specific first: every `swap` or
- * `vault` entry, then every `distribution` entry. `funding` entries name what
- * an offer is paid with (USDC, USDT) and never the asset on offer, so they are
- * left out.
- *
- * `swap` and `vault` rank together - no offer type carries both - and outrank
- * `distribution` because a swap or vault product names the token it hands over
- * precisely, while a sale's distribution entry names the same token for a sale
- * product and is accepted as the fallback. The checkout's
- * per-chain lookup and the catalogue's any-chain lookup both read this
- * ordering, which is why it is stated once, here.
- */
-declare function offerDisplayTokens(offer: {
-    tokens: readonly OfferToken[];
-}): OfferToken[];
-
-export { AssetIconUrl as A, type BroadcastTxParams as B, type ConnectWallet as C, type EvmWallet as E, FormattedAmountAssetUi as F, type NonEmptyArray as N, type PKCEConfig as P, SwapQuote as S, TxExplorerUrl as T, WalletSelection as W, ShortenedWalletAddress as a, FormattedPercentUi as b, type WalletLabelResolver as c, TokenRegistrySnapshot as d, type EvmSigner as e, type ExternalWalletAdapter as f, type WriteContractParams as g, FormattedAmountUi as h, type PKCEParams as i, generatePKCEParams as j, offerDisplayTokens as o };