@gibs/bridge-sdk 1.12.0 → 1.13.1

package/dist/routing/composed-route-quality.d.ts

@@ -0,0 +1,103 @@
+/**
+ * Whether a composed multi-signature route is good enough to offer at all.
+ *
+ * WHY A ROUTE NEEDS A GATE THAT A SINGLE CROSSING DOES NOT. A one-signature
+ * route that turns out badly costs the reader one transaction and they still
+ * hold something they chose. A composed route — an aggregator leg, then an
+ * omnibridge crossing, then a swap — strands them between signatures: after
+ * the first they hold an anchor token on a chain they did not ask for, and the
+ * only way out is to pay again. So a cheap first leg followed by a bad swap is
+ * worse than the route it replaced, and the difference has to be found BEFORE
+ * the route is listed rather than after the reader has signed.
+ *
+ * NOTHING HERE COSTS A REQUEST. Both figures the verdict reads are already in
+ * hand when a composer runs: the swap's price impact comes from the on-chain
+ * `getAmountsOut` pair the estimate already fetched, and the two dollar values
+ * come from the route's own basis. The gate is free, which is why it can run
+ * on every route rather than only on suspicious ones.
+ */
+/**
+ * The price impact above which a composed route is withdrawn, in percent.
+ *
+ * MEASURED RATHER THAN CHOSEN. Across the anchor and size combinations swept
+ * on 2026-09-21 — bridged wrapped ether, USD Coin, DAI and USDT into wrapped
+ * PulseChain coin, at roughly forty and one hundred and forty United States
+ * dollars — the impact ran from 0.008 percent to 0.037 percent, with bridged
+ * USDT the one outlier at 0.34 to 0.37 percent. Three percent is two orders of
+ * magnitude above the normal case and an order above the worst observed, so it
+ * cannot fire on an ordinary route; and it is still far below the point where
+ * a reader is quietly losing real money on a leg they cannot undo.
+ *
+ * See `docs/near-intents-conversion-composition.md` for the full sweep.
+ */
+export declare const COMPOSED_ROUTE_MAX_PRICE_IMPACT_PERCENT = 3;
+/**
+ * The end-to-end value loss above which a composed route is withdrawn, in
+ * percent of what the reader pays.
+ *
+ * A SECOND TEST BECAUSE THE FIRST CAN READ FINE ON A BROKEN POOL. Price impact
+ * is measured against a marginal reference quote taken from the same pool, so
+ * a pool that is uniformly mispriced — a stale pair, a pair holding almost
+ * nothing — reports a small impact while paying out far less than the tokens
+ * going in are worth. Only comparing the two ends of the journey catches that.
+ *
+ * Measured whole-journey loss on the same sweep ran from 0.81 to 1.36 percent,
+ * of which the swap fee alone is 0.29. Five percent leaves every observed
+ * route untouched and still stops a route that is quietly eating a twentieth
+ * of the reader's money.
+ */
+export declare const COMPOSED_ROUTE_MAX_VALUE_LOSS_PERCENT = 5;
+/**
+ * The verdict on one composed route.
+ *
+ * THREE STATES RATHER THAN A BOOLEAN, because "we have not priced this yet"
+ * and "we priced it and it is bad" are different facts and a caller must be
+ * able to act differently on them. Collapsing them would either hide a route
+ * that is merely still loading or offer one nobody has checked.
+ */
+export type ComposedRouteVerdict = {
+    readonly state: 'acceptable';
+} | {
+    readonly state: 'unknown';
+    readonly missing: 'price-impact' | 'route-value';
+} | {
+    readonly state: 'rejected';
+    readonly reason: 'price-impact' | 'value-loss';
+    /** The measured figure, in percent, that failed its ceiling. */
+    readonly measuredPercent: number;
+    /** The ceiling it failed. */
+    readonly ceilingPercent: number;
+};
+/**
+ * Judges a composed route against both ceilings.
+ *
+ * Checks price impact first and value loss second, because impact names the
+ * specific leg at fault while value loss only says the journey as a whole went
+ * wrong — so reporting impact when both fail is the more useful answer.
+ *
+ * @param options.priceImpactPercent - the swap leg's price impact, from the
+ *   estimate's marginal reference quote; null when not yet quoted
+ * @param options.paidUsdValue - what the reader spends at the origin, in
+ *   United States dollars; null when unpriced
+ * @param options.deliveredUsdValue - what the route delivers, valued on the
+ *   SAME basis as `paidUsdValue`; null when unpriced
+ * @returns the verdict
+ */
+export declare const assessComposedRoute: ({ priceImpactPercent, paidUsdValue, deliveredUsdValue, }: {
+    priceImpactPercent: number | null | undefined;
+    paidUsdValue: number | null | undefined;
+    deliveredUsdValue: number | null | undefined;
+}) => ComposedRouteVerdict;
+/**
+ * Whether a composed route may be listed on the strip.
+ *
+ * ONLY AN EXPLICIT PASS LISTS THE ROUTE. An unknown verdict withholds it, the
+ * same as a rejection, because a three-signature route nobody has checked is
+ * the case this gate exists for. The two remain distinct in
+ * {@link ComposedRouteVerdict} so a surface can tell the reader "still
+ * pricing" rather than "no route", which a boolean alone could not.
+ *
+ * @param verdict - the verdict from {@link assessComposedRoute}
+ * @returns true only when the route passed both ceilings
+ */
+export declare const composedRouteMayBeOffered: (verdict: ComposedRouteVerdict) => boolean;

package/dist/routing/composed-route-quality.js

@@ -0,0 +1,108 @@
+/**
+ * Whether a composed multi-signature route is good enough to offer at all.
+ *
+ * WHY A ROUTE NEEDS A GATE THAT A SINGLE CROSSING DOES NOT. A one-signature
+ * route that turns out badly costs the reader one transaction and they still
+ * hold something they chose. A composed route — an aggregator leg, then an
+ * omnibridge crossing, then a swap — strands them between signatures: after
+ * the first they hold an anchor token on a chain they did not ask for, and the
+ * only way out is to pay again. So a cheap first leg followed by a bad swap is
+ * worse than the route it replaced, and the difference has to be found BEFORE
+ * the route is listed rather than after the reader has signed.
+ *
+ * NOTHING HERE COSTS A REQUEST. Both figures the verdict reads are already in
+ * hand when a composer runs: the swap's price impact comes from the on-chain
+ * `getAmountsOut` pair the estimate already fetched, and the two dollar values
+ * come from the route's own basis. The gate is free, which is why it can run
+ * on every route rather than only on suspicious ones.
+ */
+/**
+ * The price impact above which a composed route is withdrawn, in percent.
+ *
+ * MEASURED RATHER THAN CHOSEN. Across the anchor and size combinations swept
+ * on 2026-09-21 — bridged wrapped ether, USD Coin, DAI and USDT into wrapped
+ * PulseChain coin, at roughly forty and one hundred and forty United States
+ * dollars — the impact ran from 0.008 percent to 0.037 percent, with bridged
+ * USDT the one outlier at 0.34 to 0.37 percent. Three percent is two orders of
+ * magnitude above the normal case and an order above the worst observed, so it
+ * cannot fire on an ordinary route; and it is still far below the point where
+ * a reader is quietly losing real money on a leg they cannot undo.
+ *
+ * See `docs/near-intents-conversion-composition.md` for the full sweep.
+ */
+export const COMPOSED_ROUTE_MAX_PRICE_IMPACT_PERCENT = 3;
+/**
+ * The end-to-end value loss above which a composed route is withdrawn, in
+ * percent of what the reader pays.
+ *
+ * A SECOND TEST BECAUSE THE FIRST CAN READ FINE ON A BROKEN POOL. Price impact
+ * is measured against a marginal reference quote taken from the same pool, so
+ * a pool that is uniformly mispriced — a stale pair, a pair holding almost
+ * nothing — reports a small impact while paying out far less than the tokens
+ * going in are worth. Only comparing the two ends of the journey catches that.
+ *
+ * Measured whole-journey loss on the same sweep ran from 0.81 to 1.36 percent,
+ * of which the swap fee alone is 0.29. Five percent leaves every observed
+ * route untouched and still stops a route that is quietly eating a twentieth
+ * of the reader's money.
+ */
+export const COMPOSED_ROUTE_MAX_VALUE_LOSS_PERCENT = 5;
+/**
+ * Judges a composed route against both ceilings.
+ *
+ * Checks price impact first and value loss second, because impact names the
+ * specific leg at fault while value loss only says the journey as a whole went
+ * wrong — so reporting impact when both fail is the more useful answer.
+ *
+ * @param options.priceImpactPercent - the swap leg's price impact, from the
+ *   estimate's marginal reference quote; null when not yet quoted
+ * @param options.paidUsdValue - what the reader spends at the origin, in
+ *   United States dollars; null when unpriced
+ * @param options.deliveredUsdValue - what the route delivers, valued on the
+ *   SAME basis as `paidUsdValue`; null when unpriced
+ * @returns the verdict
+ */
+export const assessComposedRoute = ({ priceImpactPercent, paidUsdValue, deliveredUsdValue, }) => {
+    if (typeof priceImpactPercent !== 'number' || !Number.isFinite(priceImpactPercent)) {
+        return { state: 'unknown', missing: 'price-impact' };
+    }
+    if (priceImpactPercent > COMPOSED_ROUTE_MAX_PRICE_IMPACT_PERCENT) {
+        return {
+            state: 'rejected',
+            reason: 'price-impact',
+            measuredPercent: priceImpactPercent,
+            ceilingPercent: COMPOSED_ROUTE_MAX_PRICE_IMPACT_PERCENT,
+        };
+    }
+    const bothValuesKnown = typeof paidUsdValue === 'number' &&
+        Number.isFinite(paidUsdValue) &&
+        paidUsdValue > 0 &&
+        typeof deliveredUsdValue === 'number' &&
+        Number.isFinite(deliveredUsdValue);
+    if (!bothValuesKnown) {
+        return { state: 'unknown', missing: 'route-value' };
+    }
+    const lossPercent = ((paidUsdValue - deliveredUsdValue) / paidUsdValue) * 100;
+    if (lossPercent > COMPOSED_ROUTE_MAX_VALUE_LOSS_PERCENT) {
+        return {
+            state: 'rejected',
+            reason: 'value-loss',
+            measuredPercent: lossPercent,
+            ceilingPercent: COMPOSED_ROUTE_MAX_VALUE_LOSS_PERCENT,
+        };
+    }
+    return { state: 'acceptable' };
+};
+/**
+ * Whether a composed route may be listed on the strip.
+ *
+ * ONLY AN EXPLICIT PASS LISTS THE ROUTE. An unknown verdict withholds it, the
+ * same as a rejection, because a three-signature route nobody has checked is
+ * the case this gate exists for. The two remain distinct in
+ * {@link ComposedRouteVerdict} so a surface can tell the reader "still
+ * pricing" rather than "no route", which a boolean alone could not.
+ *
+ * @param verdict - the verdict from {@link assessComposedRoute}
+ * @returns true only when the route passed both ceilings
+ */
+export const composedRouteMayBeOffered = (verdict) => verdict.state === 'acceptable';

package/dist/routing/entry-chain-anchor.d.ts

@@ -0,0 +1,88 @@
+import type { Token } from '../types.js';
+/**
+ * Which anchor tokens a non-executing aggregator may deliver on an omnibridge
+ * entry chain, and what the reader's own crossing signature then does with
+ * each one.
+ *
+ * WHY THE ANCHOR HAS TO BE A CHOICE RATHER THAN A DERIVATION. A two-signature
+ * route quotes towards one entry-chain token, taken straight from the
+ * destination pair. For a native-PulseChain destination that token is
+ * WRAPPED ether, because the omnibridge home list holds no entry for the
+ * native coin at all — measured on 2026-09-21, 657 Ethereum-side entries and
+ * not one at the zero address — so the pair a native destination resolves to
+ * is `WETH ↔ WETH from Ethereum`.
+ *
+ * NEAR Intents has NO LIQUIDITY IN WRAPPED ETHER ON ETHEREUM. Measured at
+ * 0.015, 0.05, 0.2 and 0.5 ether of input, every request answered
+ * `No liquidity available`. It carries the NATIVE coin on the same chain with
+ * plenty. So the one derived anchor is the one anchor the service cannot
+ * price, the quote is refused, and the route withdraws in silence — which is
+ * the correct response to a refusal and is also what hid this from us.
+ *
+ * WRAPPED NATIVE AND THE NATIVE COIN LAND IN THE SAME PLACE, which is what
+ * makes the substitution safe rather than merely convenient. The mediator's
+ * native router wraps on the way in: `wrapAndRelayTokens` takes the coin as
+ * transaction value and the crossing mints the SAME PulseChain token the
+ * wrapped entry would have minted. See `settings.ts`, the
+ * `assetIn.address === zeroAddress` branch. So swapping one anchor for the
+ * other changes what the aggregator delivers and changes nothing downstream.
+ *
+ * IT IS ALSO CHEAPER AND SHORTER, on both legs. Measured from Base native
+ * ether on 2026-09-21, one request batch per size:
+ *
+ * | anchor on Ethereum | 0.015 ether | 0.05 ether | 0.2 ether |
+ * | ------------------ | ----------- | ---------- | --------- |
+ * | native ether       | 0.494%      | 0.330%     | 0.278%    |
+ * | USD Coin           | 1.037%      | 0.651%     | 0.509%    |
+ * | Tether             | 1.052%      | 0.665%     | 0.506%    |
+ * | wrapped ether      | refused     | refused    | refused   |
+ *
+ * And the native coin needs no allowance, so its crossing is ONE signature
+ * where an entry-chain token's is an approval followed by a relay.
+ */
+/** What the reader's crossing signature calls with a given anchor. */
+export type EntryChainCrossingCall = 
+/** Native coin sent as transaction value; the router wraps and relays it. */
+'wrapAndRelayTokens'
+/** An entry-chain token handed to the mediator, which needs an allowance first. */
+ | 'relayTokens';
+/** One anchor the aggregator may be asked to deliver, and its consequences. */
+export type EntryChainAnchor = {
+    /** The token the aggregator delivers into the reader's own wallet. */
+    readonly token: Token;
+    /** What the reader's crossing signature calls with it. */
+    readonly crossingCall: EntryChainCrossingCall;
+    /**
+     * Whether the crossing needs a separate approval transaction first, which
+     * is an EXTRA signature on a route that already asks for several.
+     */
+    readonly requiresApproval: boolean;
+    /** The PulseChain token the crossing mints. Identical across every anchor here. */
+    readonly landsAs: Token;
+};
+/**
+ * Builds the ordered anchor list for one destination pair, cheapest and
+ * shortest first.
+ *
+ * The list is ordered, not ranked: a caller asks the aggregator for the first
+ * entry and moves to the next only on a refusal. That keeps the cost at ONE
+ * vendor request in the ordinary case, which matters against a limit of
+ * twelve hundred requests per sixty seconds.
+ *
+ * The substitution is narrow ON PURPOSE. Only the chain's wrapped native
+ * asset gains a second anchor, because only the native coin mints the same
+ * PulseChain token. A USD Coin pair does not gain an ether anchor here —
+ * ether would land as bridged ether, a different token, needing a different
+ * swap path. That is a different DESTINATION PAIR, and choosing between pairs
+ * already has a home in `selectAnchorDestinationPair`.
+ *
+ * @param options.entryChainToken - the destination pair's entry-chain side
+ * @param options.pulsechainToken - the destination pair's PulseChain side
+ * @param options.entryChainId - the omnibridge entry chain's decimal id
+ * @returns the anchors to try, in order; never empty
+ */
+export declare const entryChainAnchorsForPair: ({ entryChainToken, pulsechainToken, entryChainId, }: {
+    entryChainToken: Token;
+    pulsechainToken: Token;
+    entryChainId: number;
+}) => readonly EntryChainAnchor[];

package/dist/routing/entry-chain-anchor.js

@@ -0,0 +1,55 @@
+import { zeroAddress } from 'viem';
+import { nativeAssetOut, nativeTokenSymbol, toChain } from '../config.js';
+import { sameAddress } from '../ecosystems.js';
+/**
+ * Builds the ordered anchor list for one destination pair, cheapest and
+ * shortest first.
+ *
+ * The list is ordered, not ranked: a caller asks the aggregator for the first
+ * entry and moves to the next only on a refusal. That keeps the cost at ONE
+ * vendor request in the ordinary case, which matters against a limit of
+ * twelve hundred requests per sixty seconds.
+ *
+ * The substitution is narrow ON PURPOSE. Only the chain's wrapped native
+ * asset gains a second anchor, because only the native coin mints the same
+ * PulseChain token. A USD Coin pair does not gain an ether anchor here —
+ * ether would land as bridged ether, a different token, needing a different
+ * swap path. That is a different DESTINATION PAIR, and choosing between pairs
+ * already has a home in `selectAnchorDestinationPair`.
+ *
+ * @param options.entryChainToken - the destination pair's entry-chain side
+ * @param options.pulsechainToken - the destination pair's PulseChain side
+ * @param options.entryChainId - the omnibridge entry chain's decimal id
+ * @returns the anchors to try, in order; never empty
+ */
+export const entryChainAnchorsForPair = ({ entryChainToken, pulsechainToken, entryChainId, }) => {
+    const pairAnchor = {
+        token: entryChainToken,
+        crossingCall: 'relayTokens',
+        requiresApproval: true,
+        landsAs: pulsechainToken,
+    };
+    const entryChain = toChain(entryChainId);
+    // `nativeAssetOut` is typed as a total record and is not one — `toChain` is a
+    // cast, so an unmapped chain id yields a key that indexes to undefined. The
+    // runtime check outlives the static type on purpose.
+    const wrappedNativeAddress = nativeAssetOut[entryChain];
+    if (wrappedNativeAddress === undefined ||
+        !sameAddress(entryChainToken.address, wrappedNativeAddress, 'evm')) {
+        return [pairAnchor];
+    }
+    const nativeAnchor = {
+        token: {
+            // Decimals and name come from the WRAPPED token rather than from a
+            // constant, because the wrapped asset mirrors its coin exactly and a
+            // hard-coded eighteen would be a second source of the same fact.
+            ...entryChainToken,
+            address: zeroAddress,
+            symbol: nativeTokenSymbol[entryChain] ?? entryChainToken.symbol,
+        },
+        crossingCall: 'wrapAndRelayTokens',
+        requiresApproval: false,
+        landsAs: pulsechainToken,
+    };
+    return [nativeAnchor, pairAnchor];
+};

package/dist/routing/format.d.ts

@@ -0,0 +1,31 @@
+/**
+ * Formats a United States dollar number to a cent-precise string ("1,234.50",
+ * or "1.234,50" in German). No leading currency symbol — callers prepend it
+ * where the design needs one. The single source of truth shared by the raw
+ * producers (cent-rounding) and the display adapter (final formatting).
+ *
+ * `locale` defaults to `'en-US'` so every caller that does not read the
+ * reader's own language — the raw producers, and every existing test —
+ * keeps today's exact string. THE DISPLAY ADAPTER (`toRouteView.ts`) is the
+ * one caller that should pass the reader's own Lingui locale (`i18n.locale`):
+ * without it, the route strip's dollar figures stayed English-formatted
+ * inside every other translated screen, the one number on the page that
+ * never adopted the reader's language. The digit count never moves — only
+ * `toLocaleString`'s grouping and decimal separators do, per
+ * `minimumFractionDigits`/`maximumFractionDigits` staying pinned at 2.
+ *
+ * @param value - the United States dollar amount as a number
+ * @param locale - a BCP 47 locale tag to format with; defaults to `'en-US'`
+ * @returns the formatted two-decimal string, without a leading `$`
+ */
+export declare const formatUsd: (value: number, locale?: string) => string;
+/**
+ * Nullable {@link formatUsd}: null/undefined pass through as null so an unpriced
+ * value renders as absent rather than "0.00".
+ *
+ * @param value - the United States dollar amount, or null/undefined when unknown
+ * @param locale - a BCP 47 locale tag to format with; defaults to `'en-US'`
+ * @returns the formatted string, or null when the value is absent
+ */
+export declare const formatUsdNullable: (value: number | null | undefined, locale?: string) => string | null;
+export declare const roundUsdToCents: (value: number) => number;

package/dist/routing/format.js

@@ -0,0 +1,58 @@
+/**
+ * Formats a United States dollar number to a cent-precise string ("1,234.50",
+ * or "1.234,50" in German). No leading currency symbol — callers prepend it
+ * where the design needs one. The single source of truth shared by the raw
+ * producers (cent-rounding) and the display adapter (final formatting).
+ *
+ * `locale` defaults to `'en-US'` so every caller that does not read the
+ * reader's own language — the raw producers, and every existing test —
+ * keeps today's exact string. THE DISPLAY ADAPTER (`toRouteView.ts`) is the
+ * one caller that should pass the reader's own Lingui locale (`i18n.locale`):
+ * without it, the route strip's dollar figures stayed English-formatted
+ * inside every other translated screen, the one number on the page that
+ * never adopted the reader's language. The digit count never moves — only
+ * `toLocaleString`'s grouping and decimal separators do, per
+ * `minimumFractionDigits`/`maximumFractionDigits` staying pinned at 2.
+ *
+ * @param value - the United States dollar amount as a number
+ * @param locale - a BCP 47 locale tag to format with; defaults to `'en-US'`
+ * @returns the formatted two-decimal string, without a leading `$`
+ */
+export const formatUsd = (value, locale = 'en-US') => value.toLocaleString(locale, { minimumFractionDigits: 2, maximumFractionDigits: 2 });
+/**
+ * Nullable {@link formatUsd}: null/undefined pass through as null so an unpriced
+ * value renders as absent rather than "0.00".
+ *
+ * @param value - the United States dollar amount, or null/undefined when unknown
+ * @param locale - a BCP 47 locale tag to format with; defaults to `'en-US'`
+ * @returns the formatted string, or null when the value is absent
+ */
+export const formatUsdNullable = (value, locale) => value === null || value === undefined ? null : formatUsd(value, locale);
+/**
+ * Rounds a United States dollar amount to whole cents.
+ *
+ * This replaces cent-rounding that went through the DISPLAY formatter and parsed
+ * the result back — `Number(formatUsd(value).replace(/,/g, ''))`. That works
+ * only while the display is pinned to a locale which groups with commas and
+ * decimalises with a dot. The moment money follows the reader's language, a
+ * German build formats 1234.56 as "1.234,56", and stripping the commas from THAT
+ * yields 1.23456: a fee understated by a factor of a thousand, silently, with no
+ * NaN anywhere to make it visible.
+ *
+ * It keeps its OWN formatter rather than borrowing the display one, pinned to a
+ * fixed locale and with grouping switched off, so the string it parses has no
+ * separators to strip and no locale to disagree with. That also makes it exact
+ * rather than merely close: `Math.round(value * 100) / 100` looks equivalent and
+ * is not, because it rounds the binary double while the formatter rounds the
+ * decimal the reader typed — they disagree on 1.005, giving 1.00 against 1.01.
+ * Matching the old behaviour to the cent is the point, so the old engine stays.
+ *
+ * @param value - the United States dollar amount
+ * @returns the amount rounded to two decimal places
+ */
+const centRounder = new Intl.NumberFormat('en-US', {
+    minimumFractionDigits: 2,
+    maximumFractionDigits: 2,
+    useGrouping: false,
+});
+export const roundUsdToCents = (value) => Number(centRounder.format(value));

package/dist/routing/index.d.ts

@@ -0,0 +1,34 @@
+/**
+ * Framework-agnostic routing core for the Gibs bridge. Holds the raw numeric
+ * primitives, the candidate shape, and candidate construction — none of which
+ * depend on React or any display formatting. Display-coupled route builders
+ * remain in the user interface until the raw-versus-view RouteOption split.
+ */
+export { netDeliveredAmount, restateInDecimals, valueEquivalentAmount } from './amounts.js';
+export { omnibridgeProviderForEntryChain, pulseXConversionSwapPath } from './providers.js';
+export { buildDirectCrossingCandidate } from './candidate.js';
+export type { RouteCandidate, DeferredCrossing, DirectCrossingCandidateInputs } from './candidate.js';
+export { buildRouteDataForCandidate, routeSignatureCount } from './candidate-route.js';
+export { COMPOSED_ROUTE_MAX_PRICE_IMPACT_PERCENT, COMPOSED_ROUTE_MAX_VALUE_LOSS_PERCENT, assessComposedRoute, composedRouteMayBeOffered, } from './composed-route-quality.js';
+export type { ComposedRouteVerdict } from './composed-route-quality.js';
+export { entryChainAnchorsForPair } from './entry-chain-anchor.js';
+export type { EntryChainAnchor, EntryChainCrossingCall } from './entry-chain-anchor.js';
+export type { EstimateBasis, RouteData, RouteHopData, RouteKind, RouteOutputData, RouteSectionData, RouteTokenRef, } from './route-data.js';
+export { usdValueOfAmount } from './usd-value.js';
+export { formatUsd, formatUsdNullable } from './format.js';
+export { BRIDGE_SETTLEMENT_ETA_MINUTES, PULSEX_MARGINAL_REFERENCE_DIVISOR, pulsechainChainId, addUsdValues, providerDisplayName, resolveEntryChainName, buildCandidateRouteData, buildConversionRouteData, buildDirectRouteData, buildPulseXSwapEstimateData, buildPulseXSwapSectionData, buildOutboundRouteData, buildSameChainSwapRouteData, candidateDeliveredUsd, candidateNetValueUsd, candidateOutsideFeesUsd, candidatePaidUsd, } from './producers.js';
+export type { ConversionRouteComposition, PulseXSwapEstimateData, PulseXSwapSectionDataRoots, OutboundRouteRoots, OutboundOnwardHop, DirectRouteRoots, CrossingFeeRoots, SameChainSwapRouteRoots, } from './producers.js';
+export { RANKABLE_ESTIMATE_BASES, assetNodeKey, combineComposedPathBasis, compareRoutePlansByDeliveredAmount, groupHopsBySignature, hopComposedBasis, hopEdgeKey, isConfirmedBasis, isRankableBasis, isRateLimitedCarrier, planComposedBasis, planIsConfirmed, planIsRankable, routePlanPathKey, } from './search/graph.js';
+export type { AssetNode, CarrierId, ComposedPathBasis, HopCarrier, HopEdge, HopEdgeOrigin, HopFloor, HopOutcome, HopRequest, PlannedHop, RoutePlan, } from './search/graph.js';
+export { composableHopBasis, composeRouteDelivery, hopOutputAmount, } from './search/compose.js';
+export type { ComposableHop, ComposableHopFigure, ComposeRefusalReason, ComposedRouteDelivery, ExchangeRate, } from './search/compose.js';
+export { GAS_TOPUP_PENALTY_FLOOR_USD, GAS_TOPUP_PENALTY_PPM, SIGNATURE_PENALTY_FLOOR_USD, SIGNATURE_PENALTY_PPM, compareRoutePlansByGasAdjustedDeliveredAmount, compareRoutePlansByScoreAdjustedDeliveredAmount, gasAdjustedDeliveredAmount, scoreRoutePlan, sectionIsFundedByLanding, waitPenaltyPpm, zeroGasCostFor, } from './search/score.js';
+export type { GasCostFor, GasCostQuote, RouteScoreInputs } from './search/score.js';
+export { buildRouteCandidateFromPlan, buildRouteDataFromPlan, buildRouteScoreInputsFromPlan, deriveDeferredCrossingFromPlan, deriveEntryChainIdFromPlan, deriveOmnibridgeProviderFromPlan, deriveViaChainIdsFromPlan, derivePlanKind, } from './search/plan-route-data.js';
+export type { PlanCandidateInputs, PlanRouteDataInputs, PlanSectionPricing, PlanValuation, ResolveNodeToken, } from './search/plan-route-data.js';
+export { createOmnibridgeCarrier, withOmnibridgeEntryFusing, } from './carriers/omnibridge.js';
+export type { BridgeablePair, CreateOmnibridgeCarrierOptions, } from './carriers/omnibridge.js';
+export { createPulseXCarrier, pulseXPoolPath, pulseXRouterForEdge, pulseXVenues } from './carriers/pulsex.js';
+export type { CreatePulseXCarrierOptions, PulseXVenue } from './carriers/pulsex.js';
+export { createWrapCarrier } from './carriers/wrap.js';
+export type { CarrierAskAnswer, CarrierExactResult } from './carriers/ask-answer.js';

package/dist/routing/index.js

@@ -0,0 +1,42 @@
+/**
+ * Framework-agnostic routing core for the Gibs bridge. Holds the raw numeric
+ * primitives, the candidate shape, and candidate construction — none of which
+ * depend on React or any display formatting. Display-coupled route builders
+ * remain in the user interface until the raw-versus-view RouteOption split.
+ */
+export { netDeliveredAmount, restateInDecimals, valueEquivalentAmount } from './amounts.js';
+export { omnibridgeProviderForEntryChain, pulseXConversionSwapPath } from './providers.js';
+export { buildDirectCrossingCandidate } from './candidate.js';
+export { buildRouteDataForCandidate, routeSignatureCount } from './candidate-route.js';
+export { COMPOSED_ROUTE_MAX_PRICE_IMPACT_PERCENT, COMPOSED_ROUTE_MAX_VALUE_LOSS_PERCENT, assessComposedRoute, composedRouteMayBeOffered, } from './composed-route-quality.js';
+export { entryChainAnchorsForPair } from './entry-chain-anchor.js';
+export { usdValueOfAmount } from './usd-value.js';
+export { formatUsd, formatUsdNullable } from './format.js';
+export { BRIDGE_SETTLEMENT_ETA_MINUTES, PULSEX_MARGINAL_REFERENCE_DIVISOR, pulsechainChainId, addUsdValues, providerDisplayName, resolveEntryChainName, buildCandidateRouteData, buildConversionRouteData, buildDirectRouteData, buildPulseXSwapEstimateData, buildPulseXSwapSectionData, buildOutboundRouteData, buildSameChainSwapRouteData, candidateDeliveredUsd, candidateNetValueUsd, candidateOutsideFeesUsd, candidatePaidUsd, } from './producers.js';
+// The route-search engine's pure data model: node/edge shapes, path keying,
+// signature grouping, and the basis/rankability rules. The SEARCH ORCHESTRATION
+// built on top of this (`capabilities.ts`, `enumerate.ts`, `waves.ts`) now
+// lives in `@gibs/quotes`'s `search/` directory, carrier-agnostic — see
+// `docs/quote-service.md`'s "Carriers" section. This module stays here
+// because `search/plan-route-data.ts` (gibs's presentation layer, below)
+// calls its functions directly and `bridge-sdk` cannot depend on `@gibs/quotes`
+// (which already depends on `bridge-sdk`) without a circular package
+// dependency; `@gibs/quotes`'s `types.ts` re-exports the same declarations
+// under its `Carrier*` names.
+export { RANKABLE_ESTIMATE_BASES, assetNodeKey, combineComposedPathBasis, compareRoutePlansByDeliveredAmount, groupHopsBySignature, hopComposedBasis, hopEdgeKey, isConfirmedBasis, isRankableBasis, isRateLimitedCarrier, planComposedBasis, planIsConfirmed, planIsRankable, routePlanPathKey, } from './search/graph.js';
+export { composableHopBasis, composeRouteDelivery, hopOutputAmount, } from './search/compose.js';
+export { GAS_TOPUP_PENALTY_FLOOR_USD, GAS_TOPUP_PENALTY_PPM, SIGNATURE_PENALTY_FLOOR_USD, SIGNATURE_PENALTY_PPM, compareRoutePlansByGasAdjustedDeliveredAmount, compareRoutePlansByScoreAdjustedDeliveredAmount, gasAdjustedDeliveredAmount, scoreRoutePlan, sectionIsFundedByLanding, waitPenaltyPpm, zeroGasCostFor, } from './search/score.js';
+// General route search — Phase 1: plan-route-data.ts. Turns a priced
+// RoutePlan into the same RouteData/RouteCandidate/RouteScoreInputs shapes
+// today's four hand-written producers emit — see that module's head doc.
+export { buildRouteCandidateFromPlan, buildRouteDataFromPlan, buildRouteScoreInputsFromPlan, deriveDeferredCrossingFromPlan, deriveEntryChainIdFromPlan, deriveOmnibridgeProviderFromPlan, deriveViaChainIdsFromPlan, derivePlanKind, } from './search/plan-route-data.js';
+// The route-search maximization ENGINE — carrier registration
+// (`buildCapabilityIndex`), the depth-first search (`enumerateRoutes`) and
+// the wave-based quoting orchestrator (`searchRouteWaves`) — moved to
+// `@gibs/quotes`'s `search/` directory (`docs/quote-service.md`'s
+// "Carriers" section). Import `buildCapabilityIndex`, `enumerateRoutes`,
+// `searchRouteWaves` and their types from `@gibs/quotes/search`. Gibs's own
+// carriers (the omnibridge crossing, PulseX) live in `./carriers/`, below.
+export { createOmnibridgeCarrier, withOmnibridgeEntryFusing, } from './carriers/omnibridge.js';
+export { createPulseXCarrier, pulseXPoolPath, pulseXRouterForEdge, pulseXVenues } from './carriers/pulsex.js';
+export { createWrapCarrier } from './carriers/wrap.js';