@coinlist-co/react 0.12.1-rc.e183ffd → 0.12.1-rc.f2804ef

package/dist/{collections-Biy3pQQL.d.cts → token-registry-snapshot-BNBNuDu1.d.ts}

@@ -1,4 +1,4 @@
-import { aI as ClientId, bw as RedirectUri, aJ as CodeChallenge, bk as PKCEState, C as CodeVerifier, q as EvmWalletAddress, a as EthereumChain, bN as Tx, B as BlockchainAmount, bG as SwapPreview, a0 as AssetDecimals, aA as Newtype } from './tokens-namespace-CIWBtgt2.cjs';
+import { aI as ClientId, bw as RedirectUri, aJ as CodeChallenge, bk as PKCEState, C as CodeVerifier, q as EvmWalletAddress, a as EthereumChain, bN as Tx, B as BlockchainAmount, bG as SwapPreview, a0 as AssetDecimals, aA as Newtype, D as TokenMetadata, aH as Chain, b as EvmContractAddress, bf as OfferToken } from './tokens-namespace-CIWBtgt2.js';
 import { Hex, Abi, Hash, TransactionReceipt } from 'viem';
 
 type PKCEParams = {
@@ -113,4 +113,67 @@ declare const AssetIconUrl: (value: string) => AssetIconUrl;
  */
 type NonEmptyArray<T> = [T, ...T[]];
 
-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, type WriteContractParams as W, ShortenedWalletAddress as a, FormattedPercentUi as b, type EvmSigner as c, FormattedAmountUi as d, type PKCEParams as e, generatePKCEParams as g };
+/**
+ * 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` entry,
+ * then every `distribution` entry. `funding` entries name what a swap is paid
+ * with (USDC, USDT) and never the asset on offer, so they are left out.
+ *
+ * `swap` outranks `distribution` because a swap product names the asset 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, type WriteContractParams as W, ShortenedWalletAddress as a, FormattedPercentUi as b, TokenRegistrySnapshot as c, type EvmSigner as d, FormattedAmountUi as e, type PKCEParams as f, generatePKCEParams as g, offerDisplayTokens as o };

package/dist/{collections-JfNDG8Tc.d.ts → token-registry-snapshot-CqI6dXM_.d.cts}

@@ -1,4 +1,4 @@
-import { aI as ClientId, bw as RedirectUri, aJ as CodeChallenge, bk as PKCEState, C as CodeVerifier, q as EvmWalletAddress, a as EthereumChain, bN as Tx, B as BlockchainAmount, bG as SwapPreview, a0 as AssetDecimals, aA as Newtype } from './tokens-namespace-CIWBtgt2.js';
+import { aI as ClientId, bw as RedirectUri, aJ as CodeChallenge, bk as PKCEState, C as CodeVerifier, q as EvmWalletAddress, a as EthereumChain, bN as Tx, B as BlockchainAmount, bG as SwapPreview, a0 as AssetDecimals, aA as Newtype, D as TokenMetadata, aH as Chain, b as EvmContractAddress, bf as OfferToken } from './tokens-namespace-CIWBtgt2.cjs';
 import { Hex, Abi, Hash, TransactionReceipt } from 'viem';
 
 type PKCEParams = {
@@ -113,4 +113,67 @@ declare const AssetIconUrl: (value: string) => AssetIconUrl;
  */
 type NonEmptyArray<T> = [T, ...T[]];
 
-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, type WriteContractParams as W, ShortenedWalletAddress as a, FormattedPercentUi as b, type EvmSigner as c, FormattedAmountUi as d, type PKCEParams as e, generatePKCEParams as g };
+/**
+ * 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` entry,
+ * then every `distribution` entry. `funding` entries name what a swap is paid
+ * with (USDC, USDT) and never the asset on offer, so they are left out.
+ *
+ * `swap` outranks `distribution` because a swap product names the asset 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, type WriteContractParams as W, ShortenedWalletAddress as a, FormattedPercentUi as b, TokenRegistrySnapshot as c, type EvmSigner as d, FormattedAmountUi as e, type PKCEParams as f, generatePKCEParams as g, offerDisplayTokens as o };

package/dist/universal/index.cjs

@@ -77,7 +77,7 @@ __export(universal_exports, {
   OAuthRefreshToken: () => OAuthRefreshToken,
   OAuthSession: () => OAuthSession,
   ONDO_POLL_INTERVAL_MS: () => ONDO_POLL_INTERVAL_MS,
-  ONDO_QUOTE_EXPIRY_THRESHOLD_MS: () => ONDO_QUOTE_EXPIRY_THRESHOLD_MS,
+  ONDO_QUOTE_MAX_TTL_MS: () => ONDO_QUOTE_MAX_TTL_MS,
   ONDO_SETTLEMENT_ASSET: () => ONDO_SETTLEMENT_ASSET,
   ONDO_SUPPORTED_INPUT_ASSETS: () => ONDO_SUPPORTED_INPUT_ASSETS,
   Offer: () => Offer,
@@ -136,6 +136,7 @@ __export(universal_exports, {
   TokenLogo: () => TokenLogo,
   TokenLogoUrl: () => TokenLogoUrl,
   TokenMetadata: () => TokenMetadata,
+  TokenRegistrySnapshot: () => TokenRegistrySnapshot,
   TokensNamespaceImpl: () => TokensNamespaceImpl,
   TxExplorerUrl: () => TxExplorerUrl,
   USDC: () => USDC,
@@ -173,6 +174,8 @@ __export(universal_exports, {
   isChain: () => isChain,
   isOfferType: () => isOfferType,
   isSwapAvailable: () => isSwapAvailable,
+  offerDisplayTokens: () => offerDisplayTokens,
+  ondoQuoteOfferDeadline: () => ondoQuoteOfferDeadline,
   parseBlockchainAmount: () => parseBlockchainAmount,
   parseUint256: () => parseUint256,
   shortenAddress: () => shortenAddress,
@@ -1191,7 +1194,7 @@ var TOKEN_REGISTRY = {
 
 // src/universal/core/checkout/ondo/constants.ts
 var ONDO_POLL_INTERVAL_MS = 15e3;
-var ONDO_QUOTE_EXPIRY_THRESHOLD_MS = 5e3;
+var ONDO_QUOTE_MAX_TTL_MS = 15e3;
 var DEFAULT_ONDO_AMOUNT_TO_COMPUTE_PRICE = DecimalString("1000");
 var ONDO_SETTLEMENT_ASSET = USDC_SYMBOL;
 var DEFAULT_ONDO_SELL_TOKENS_TO_COMPUTE_PRICE = 1;
@@ -1214,6 +1217,9 @@ function computeOndoSellPrice(transaction) {
     shares: spendInputAmount
   });
 }
+function ondoQuoteOfferDeadline(expiresAt, nowMs = Date.now()) {
+  return new Date(Math.min(expiresAt.getTime(), nowMs + ONDO_QUOTE_MAX_TTL_MS));
+}
 function grossProceeds(expected) {
   const raw = expected.quantity.raw + expected.fee.raw;
   if (raw > MAX_UINT_256) {
@@ -3272,6 +3278,52 @@ var Erc20NamespaceImpl = class {
   }
 };
 
+// src/universal/core/tokens/token-registry-snapshot.ts
+var TokenRegistrySnapshot = {
+  /** Indexes a `tokens.list()` result. `[]` is a valid, empty snapshot. */
+  fromTokens: (tokens) => ({
+    tokens,
+    byKey: new Map(
+      tokens.map((token) => [registryKey(token.identifier), token])
+    )
+  }),
+  /**
+   * 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, token) => snapshot.byKey.get(registryKey(token)) ?? 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, offer) => {
+    for (const token of offerDisplayTokens(offer)) {
+      const metadata = TokenRegistrySnapshot.get(snapshot, token);
+      if (metadata !== null) {
+        return metadata;
+      }
+    }
+    return null;
+  }
+};
+function offerDisplayTokens(offer) {
+  const swaps = offer.tokens.filter((token) => token.role === "swap");
+  const distributions = offer.tokens.filter(
+    (token) => token.role === "distribution"
+  );
+  return [...swaps, ...distributions];
+}
+function registryKey(token) {
+  return `${token.chain}:${token.address.toLowerCase()}`;
+}
+
 // src/universal/api/nabu/tokens.ts
 var import_viem5 = require("viem");
 
@@ -3865,7 +3917,7 @@ var User = {
   OAuthRefreshToken,
   OAuthSession,
   ONDO_POLL_INTERVAL_MS,
-  ONDO_QUOTE_EXPIRY_THRESHOLD_MS,
+  ONDO_QUOTE_MAX_TTL_MS,
   ONDO_SETTLEMENT_ASSET,
   ONDO_SUPPORTED_INPUT_ASSETS,
   Offer,
@@ -3924,6 +3976,7 @@ var User = {
   TokenLogo,
   TokenLogoUrl,
   TokenMetadata,
+  TokenRegistrySnapshot,
   TokensNamespaceImpl,
   TxExplorerUrl,
   USDC,
@@ -3961,6 +4014,8 @@ var User = {
   isChain,
   isOfferType,
   isSwapAvailable,
+  offerDisplayTokens,
+  ondoQuoteOfferDeadline,
   parseBlockchainAmount,
   parseUint256,
   shortenAddress,