thunder-bridge 2.2.1 → 3.0.1

package/dist/{bank-BgA45yOU.d.ts → nwc-BivXGSPY.d.ts}

@@ -1,5 +1,5 @@
-import { R as Resolved, Q as QrOptions } from './qr-CF-YeXU1.js';
 import { A as Amount, T as Ticker, C as Charge, f as MintedPayment, h as PaymentStatus, i as Priced, g as Msat, S as Settlement, P as Payment, Q as Quote, e as Held, H as Handover, j as SocketTicket } from './types-DYZ9EkmJ.js';
+import { R as Resolved, Q as QrOptions } from './qr-CF-YeXU1.js';
 
 type Sent = {
     method?: string;
@@ -15,6 +15,47 @@ type Verified = {
 /** Carries one request to an address ask() already verified, so nothing resolves the name again */
 type Send = (url: string, sent: Sent, signal: AbortSignal, at: readonly Verified[]) => Promise<Response>;
 
+/** The wallet's own LUD-21 URL and the hash its preimage has to match */
+interface Relayed {
+    url: string;
+    hash: string;
+}
+/** Where your own verify endpoint is mounted, and the secret it was given */
+interface VerifyThrough {
+    endpoint: string;
+    secret: string;
+}
+/**
+ * Who the gateway polls. `verifyThrough` is an endpoint of yours, which needs a
+ * server and keeps the wallet and the amount from the gateway. `gatewayMints`
+ * lets the gateway mint and poll the wallet itself, for a client with no server
+ */
+type VerifyPath = {
+    verifyThrough: VerifyThrough;
+    gatewayMints?: never;
+} | {
+    gatewayMints: true;
+    verifyThrough?: never;
+};
+/** The verify endpoint that asks the wallet for the gateway, and how often it may be asked */
+interface LightningVerifyConfig {
+    /** The secret the sealed wallet URL was made with, and nothing else uses it */
+    secret: string;
+    /**
+     * How often you want the gateway to ask, in seconds. It goes out as
+     * `Cache-Control: max-age`, so the pace is yours rather than the operator's.
+     * Five by default, which is what a Lightning checkout wants
+     */
+    pollEverySecs?: number;
+    /** How the relay reaches the wallet, pinned to the address it verified unless you say otherwise */
+    send?: Send;
+}
+/**
+ * The URL to hand the gateway instead of the wallet's own, with the wallet's
+ * sealed inside it. Point it at wherever `serve.lightningVerify` is mounted
+ */
+declare function relayedVerifyUrl(endpoint: string, wallet: Relayed, secret: string): Promise<string>;
+
 /** A wallet reachable over NIP-47, as its `nostr+walletconnect://` URI describes it */
 interface NwcConnection {
     /** The wallet service's public key, which is what its answers have to be signed by */
@@ -74,21 +115,9 @@ declare function nwcSettlement(connection: NwcConnection, paymentHash: string, t
  * a lie rather than a receipt, so it throws instead of being passed on
  */
 declare function nwcPay(connection: NwcConnection, bolt11: string, timeoutMs?: number): Promise<string>;
-/**
- * A verify endpoint of your own that asks your wallet over NIP-47, so the gateway
- * polls you and never learns the connection, the relay, or which wallet it is.
- *
- * `nwcVerifyUrl` seals the payment hash into the query with your secret, which is
- * what stops a stranger driving your wallet through this handler. It answers the
- * LUD-21 shape the gateway already speaks, so nothing on that side changes.
- *
- * A wallet it cannot reach answers `502` rather than "not settled", because those
- * are different claims and only one of them is true.
- */
-declare function nwcVerifyEndpoint(config: NwcVerifyConfig): (request: Request) => Promise<Response>;
 /**
  * The URL to hand the gateway, with the payment hash sealed inside it. Point it at
- * wherever `nwcVerifyEndpoint` is mounted
+ * wherever `serve.nwcVerify` is mounted
  */
 declare function nwcVerifyUrl(endpoint: string, paymentHash: string, secret: string): Promise<string>;
 /**
@@ -109,25 +138,15 @@ interface NwcRailConfig extends RailConfig {
     /** Where the default conversion gets its rate, the median of four venues by default */
     rate?: Ticker;
     /** Where `serve.nwcVerify` is mounted, and the secret the hash is sealed with */
-    verifyThrough: {
-        endpoint: string;
-        secret: string;
-    };
+    verifyThrough: VerifyThrough;
     /** What the payer's wallet shows, the order's reference by default */
     description?: (order: Order) => string;
-    /** Sealed before the gateway sees it, the way the blind Lightning rail does */
+    /** Sealed before the gateway sees it, the way the Lightning rail does */
     sealed?: {
         secret: string;
         data: (order: Order) => unknown;
     };
 }
-/**
- * Sell for Lightning against a wallet of your own over NIP-47, for a wallet that
- * has no LUD-21 address to be watched at. Your node mints the invoice and releases
- * the preimage, so the proof comes from one hop nearer than any hosted address can
- * manage, and the gateway sees a hash and a URL of yours
- */
-declare function nwcRail(gateway: ThunderBridge, config: NwcRailConfig): Rail;
 
 /** What a shop knows about a sale before any rail exists */
 interface Order {
@@ -167,8 +186,8 @@ interface RailConfig {
     /** What `Leg.rail` says, so two rails of one kind can be told apart */
     name?: string;
 }
-/** A Lightning rail the gateway mints for, bound once and then given one order at a time */
-interface LightningRailConfig extends RailConfig {
+/** Who a Lightning rail pays and what one order costs there, whichever path verifies it */
+interface LightningRailSettings extends RailConfig {
     /** Priority list, the first address that can prove an invoice wins */
     paidTo: string | string[];
     /**
@@ -178,11 +197,8 @@ interface LightningRailConfig extends RailConfig {
     amount?: (order: Order) => Amount;
     /** Where the default conversion gets its rate, the median of four venues by default */
     rate?: Ticker;
-    /** Makes the mint safe to retry, the order's reference by default */
+    /** Makes the gateway's mint safe to retry, so it applies with `gatewayMints` only */
     idempotencyKey?: (order: Order) => string | undefined;
-}
-/** The same rail with the invoice resolved here, so the gateway is told neither address nor amount */
-interface BlindLightningRailConfig extends LightningRailConfig {
     /**
      * What the watcher needs and the gateway must not read, sealed under `secret`
      * for the invoice's payment hash before it goes anywhere near the gateway
@@ -191,18 +207,16 @@ interface BlindLightningRailConfig extends LightningRailConfig {
         secret: string;
         data: (order: Order) => unknown;
     };
-    /**
-     * Where your own `serve.verify` endpoint is mounted, and its secret. Without
-     * it the gateway is handed the wallet's own URL, which a gateway enforcing its
-     * verify challenge will refuse to poll
-     */
-    relayThrough?: {
-        endpoint: string;
-        secret: string;
-    };
     /** How the rail reaches wallets, pinned to the address it verified unless you say otherwise */
     send?: Send;
 }
+/**
+ * A Lightning rail, bound once and then given one order at a time. With
+ * `verifyThrough` the invoice is resolved here and the gateway polls your
+ * `serve.lightningVerify`, learning neither who is paid nor how much. With
+ * `gatewayMints` the gateway is told both, mints, and polls the wallet itself
+ */
+type LightningRailConfig = LightningRailSettings & VerifyPath;
 /** A bank rail: the account the money lands in, and where its arrival is read back from */
 interface BankRailConfig extends RailConfig {
     /** Long lived and server side. Every preimage is derived from it, so losing it loses every proof */
@@ -213,7 +227,7 @@ interface BankRailConfig extends RailConfig {
     verifyUrl: string;
     /** When this leg stops being payable, in unix seconds */
     expiresAt: (order: Order) => number;
-    /** Sealed before the gateway sees it, the way the blind Lightning rail does */
+    /** Sealed before the gateway sees it, the way the Lightning rail does */
     sealed?: {
         secret: string;
         data: (order: Order) => unknown;
@@ -244,13 +258,11 @@ declare function invoiceFrom(paidTo: string | string[], amount: Amount, send?: S
 declare class Rails {
     private readonly gateway;
     constructor(gateway: ThunderBridge);
-    /** Lightning, with the gateway minting against a priority list of addresses */
-    lightning(config: LightningRailConfig): Rail;
     /**
-     * Lightning, with the invoice resolved here so the gateway is told neither the
-     * address nor the amount
+     * Lightning against a priority list of addresses, verified through your
+     * `serve.lightningVerify`, or minted by the gateway when you say `gatewayMints`
      */
-    blindLightning(config: BlindLightningRailConfig): Rail;
+    lightning(config: LightningRailConfig): Rail;
     /** A bank transfer, proved the way a Lightning payment is */
     bank(config: BankRailConfig): Rail;
     /**
@@ -325,32 +337,8 @@ interface PaymentRequest {
     prove(): Promise<string | null>;
 }
 
-/** The wallet's own LUD-21 URL and the hash its preimage has to match */
-interface Relayed {
-    url: string;
-    hash: string;
-}
-/** The verify endpoint that asks the wallet for the gateway, and how often it may be asked */
-interface LightningVerifyConfig {
-    /** The secret the sealed wallet URL was made with, and nothing else uses it */
-    secret: string;
-    /**
-     * How often you want the gateway to ask, in seconds. It goes out as
-     * `Cache-Control: max-age`, so the pace is yours rather than the operator's.
-     * Five by default, which is what a Lightning checkout wants
-     */
-    pollEverySecs?: number;
-    /** How the relay reaches the wallet, pinned to the address it verified unless you say otherwise */
-    send?: Send;
-}
-/**
- * The URL to hand the gateway instead of the wallet's own, with the wallet's
- * sealed inside it. Point it at wherever `lightningVerifyEndpoint` is mounted
- */
-declare function relayedVerifyUrl(endpoint: string, wallet: Relayed, secret: string): Promise<string>;
-
 /** An LNURL-pay endpoint of your own: whose wallets it stands for, and what it charges */
-interface TriggerConfig {
+interface TriggerSettings {
     /** Priority list, quoted at payRequest and then pinned for the callback */
     paidTo: string | string[];
     /**
@@ -379,26 +367,6 @@ interface TriggerConfig {
     send?: Send;
     /** Override when a proxy hides the public URL from the request, no trailing slash */
     baseUrl?: string;
-    /**
-     * Resolve the address here and hand the gateway only a hash and a URL to poll,
-     * instead of asking it to mint. It then cannot tell who is being paid beyond
-     * the domain in the verify URL, nor how much at all, so the only refusal left
-     * to it is refusing everyone. Costs one more round trip and gives up the
-     * gateway's CORS proxying, which a server does not need anyway.
-     *
-     * A gateway that enforces its verify challenge will not poll a wallet's own
-     * LUD-21 URL, so pass `relayThrough` as well and the poll comes to you
-     */
-    blind?: boolean;
-    /**
-     * Where your own `serve.verify` endpoint is mounted, and the secret it was
-     * given. The wallet's URL is sealed inside the one the gateway is handed, so
-     * the gateway polls you and learns neither the wallet nor its provider
-     */
-    relayThrough?: {
-        endpoint: string;
-        secret: string;
-    };
     /**
      * What the watcher needs and the gateway must not have. `data` returns it and
      * `secret` encrypts it, so there is no way to hand the gateway something it
@@ -410,7 +378,13 @@ interface TriggerConfig {
         data: (minted: Minted) => unknown;
     };
 }
-/** What a blind mint produced, which is what the sealed payload is built from */
+/**
+ * The endpoint's settings and who the gateway polls. With `verifyThrough` the
+ * address is resolved here and the gateway polls your `serve.lightningVerify`,
+ * learning neither who is paid nor how much. With `gatewayMints` it quotes and
+ * mints, and polls the wallet itself
+ */
+type TriggerConfig = TriggerSettings & VerifyPath;
 /**
  * What a payer may choose to send, when the endpoint lets them choose at all.
  * Both ends are asked once per payRequest, so a fiat range moves with the rate
@@ -419,7 +393,7 @@ interface Range {
     least: Amount;
     most: Amount;
 }
-/** What a blind mint produced, which is what the sealed payload is built from */
+/** What a mint through your endpoint produced, which is what the sealed payload is built from */
 interface Minted {
     lnAddress: string;
     amountMsat: number;
@@ -486,12 +460,6 @@ type SelfConsistent<T extends Provable> = T & {
     status: "paid";
     preimage: string;
 };
-/**
- * What `SelfConsistent` was called before 2.2.0
- *
- * @deprecated Use `SelfConsistent`, which says the report was checked against itself and nothing else
- */
-type Proven<T extends Provable> = SelfConsistent<T>;
 /**
  * Whether a report agrees with itself: it says paid, and it carries a preimage
  * that hashes to the payment hash it itself names. Where an invoice comes with it,
@@ -506,12 +474,6 @@ type Proven<T extends Provable> = SelfConsistent<T>;
  * `proveSettlement` asks the recipient
  */
 declare function agreesWithItself<T extends Provable>(report: T): report is SelfConsistent<T>;
-/**
- * What `agreesWithItself` was called before 2.2.0
- *
- * @deprecated Use `agreesWithItself`, because it proves nothing beyond the report itself
- */
-declare const carriesProof: typeof agreesWithItself;
 /**
  * The most an operator may add over the recipient's own amount, in millisatoshi.
  * The proportion is what routing and the liquidity behind it costs, and the base
@@ -626,12 +588,6 @@ declare class Serve {
      * the gateway polls you and never the wallet
      */
     lightningVerify(config: LightningVerifyConfig): Handler;
-    /**
-     * What `lightningVerify` was called before 2.2.0
-     *
-     * @deprecated Use `lightningVerify`, beside `bankVerify` and `nwcVerify`
-     */
-    verify(config: LightningVerifyConfig): Handler;
     /** The verify endpoint a bank rail is polled at, answering off your own statement */
     bankVerify(config: BankVerifyConfig): Handler;
     /**
@@ -952,7 +908,7 @@ interface BankTransferParams {
     /** The account the money goes to, as an IBAN */
     iban: string;
     /**
-     * Where `bankVerifyEndpoint` is mounted, a public https URL with no query of
+     * Where `serve.bankVerify` is mounted, a public https URL with no query of
      * its own. Not needed when `answerBy` is "agent", because then nothing is polled
      */
     verifyUrl?: string;
@@ -1061,4 +1017,4 @@ interface BankAgentConfig {
  */
 declare function bankAgent(config: BankAgentConfig): () => void;
 
-export { type WebhookOptions as $, type AttendOptions as A, type BankAgentConfig as B, type Credit as C, type Proven as D, type RailConfig as E, type FollowOptions as F, Rails as G, type Handler as H, type Range as I, type Relayed as J, type SelfConsistent as K, type Leg as L, type Minted as M, type NwcConnection as N, type Order as O, type PaymentRequest as P, type Send as Q, type Rail as R, type Statement as S, ThunderBridge as T, Serve as U, type TicketOptions as V, type WaitOptions as W, type TriggerConfig as X, type WatchTicketConfig as Y, type WebhookCredential as Z, type WebhookHandlers as _, type BankOrder as a, type WrapAllowance as a0, agreesWithItself as a1, answerVerifyChallenge as a2, carriesProof as a3, invoiceFrom as a4, proveOrigin as a5, proveSettlement as a6, proveWrapped as a7, relayedVerifyUrl as a8, wrapFeeCeiling as a9, type BankTransfer as b, type BankTransferParams as c, type BankVerifyConfig as d, bankAgent as e, nwcVerifyEndpoint as f, type NwcInvoice as g, type NwcRailConfig as h, type NwcVerifyConfig as i, askWallet as j, nwcConnection as k, nwcHoldInvoice as l, nwcInvoice as m, nwcRail as n, nwcPay as o, nwcSettlement as p, nwcVerifyUrl as q, type ThunderBridgeOptions as r, type BankRailConfig as s, type BlindLightningRailConfig as t, type CreateOptions as u, type LightningRailConfig as v, type LightningVerifyConfig as w, type PaymentRequestInit as x, type PaymentRequestOptions as y, type Provable as z };
+export { relayedVerifyUrl as $, type AttendOptions as A, type BankAgentConfig as B, type Credit as C, type VerifyThrough as D, type WatchTicketConfig as E, type FollowOptions as F, type WebhookCredential as G, type Handler as H, type WebhookHandlers as I, type WebhookOptions as J, type WrapAllowance as K, type Leg as L, type Minted as M, type NwcConnection as N, type Order as O, type PaymentRequest as P, agreesWithItself as Q, type Rail as R, type Statement as S, ThunderBridge as T, answerVerifyChallenge as U, type VerifyPath as V, type WaitOptions as W, invoiceFrom as X, proveOrigin as Y, proveSettlement as Z, proveWrapped as _, type BankOrder as a, wrapFeeCeiling as a0, type NwcInvoice as a1, askWallet as a2, nwcConnection as a3, nwcHoldInvoice as a4, nwcInvoice as a5, nwcPay as a6, nwcSettlement as a7, nwcVerifyUrl as a8, type BankTransfer as b, type BankTransferParams as c, type BankVerifyConfig as d, bankAgent as e, type ThunderBridgeOptions as f, type BankRailConfig as g, type CreateOptions as h, type LightningRailConfig as i, type LightningRailSettings as j, type LightningVerifyConfig as k, type NwcRailConfig as l, type NwcVerifyConfig as m, type PaymentRequestInit as n, type PaymentRequestOptions as o, type Provable as p, type RailConfig as q, Rails as r, type Range as s, type Relayed as t, type SelfConsistent as u, type Send as v, Serve as w, type TicketOptions as x, type TriggerConfig as y, type TriggerSettings as z };

package/dist/{bank-DvcV85sa.d.cts → nwc-h_-cGvMb.d.cts}

@@ -1,5 +1,5 @@
-import { R as Resolved, Q as QrOptions } from './qr-CF-YeXU1.cjs';
 import { A as Amount, T as Ticker, C as Charge, f as MintedPayment, h as PaymentStatus, i as Priced, g as Msat, S as Settlement, P as Payment, Q as Quote, e as Held, H as Handover, j as SocketTicket } from './types-DYZ9EkmJ.cjs';
+import { R as Resolved, Q as QrOptions } from './qr-CF-YeXU1.cjs';
 
 type Sent = {
     method?: string;
@@ -15,6 +15,47 @@ type Verified = {
 /** Carries one request to an address ask() already verified, so nothing resolves the name again */
 type Send = (url: string, sent: Sent, signal: AbortSignal, at: readonly Verified[]) => Promise<Response>;
 
+/** The wallet's own LUD-21 URL and the hash its preimage has to match */
+interface Relayed {
+    url: string;
+    hash: string;
+}
+/** Where your own verify endpoint is mounted, and the secret it was given */
+interface VerifyThrough {
+    endpoint: string;
+    secret: string;
+}
+/**
+ * Who the gateway polls. `verifyThrough` is an endpoint of yours, which needs a
+ * server and keeps the wallet and the amount from the gateway. `gatewayMints`
+ * lets the gateway mint and poll the wallet itself, for a client with no server
+ */
+type VerifyPath = {
+    verifyThrough: VerifyThrough;
+    gatewayMints?: never;
+} | {
+    gatewayMints: true;
+    verifyThrough?: never;
+};
+/** The verify endpoint that asks the wallet for the gateway, and how often it may be asked */
+interface LightningVerifyConfig {
+    /** The secret the sealed wallet URL was made with, and nothing else uses it */
+    secret: string;
+    /**
+     * How often you want the gateway to ask, in seconds. It goes out as
+     * `Cache-Control: max-age`, so the pace is yours rather than the operator's.
+     * Five by default, which is what a Lightning checkout wants
+     */
+    pollEverySecs?: number;
+    /** How the relay reaches the wallet, pinned to the address it verified unless you say otherwise */
+    send?: Send;
+}
+/**
+ * The URL to hand the gateway instead of the wallet's own, with the wallet's
+ * sealed inside it. Point it at wherever `serve.lightningVerify` is mounted
+ */
+declare function relayedVerifyUrl(endpoint: string, wallet: Relayed, secret: string): Promise<string>;
+
 /** A wallet reachable over NIP-47, as its `nostr+walletconnect://` URI describes it */
 interface NwcConnection {
     /** The wallet service's public key, which is what its answers have to be signed by */
@@ -74,21 +115,9 @@ declare function nwcSettlement(connection: NwcConnection, paymentHash: string, t
  * a lie rather than a receipt, so it throws instead of being passed on
  */
 declare function nwcPay(connection: NwcConnection, bolt11: string, timeoutMs?: number): Promise<string>;
-/**
- * A verify endpoint of your own that asks your wallet over NIP-47, so the gateway
- * polls you and never learns the connection, the relay, or which wallet it is.
- *
- * `nwcVerifyUrl` seals the payment hash into the query with your secret, which is
- * what stops a stranger driving your wallet through this handler. It answers the
- * LUD-21 shape the gateway already speaks, so nothing on that side changes.
- *
- * A wallet it cannot reach answers `502` rather than "not settled", because those
- * are different claims and only one of them is true.
- */
-declare function nwcVerifyEndpoint(config: NwcVerifyConfig): (request: Request) => Promise<Response>;
 /**
  * The URL to hand the gateway, with the payment hash sealed inside it. Point it at
- * wherever `nwcVerifyEndpoint` is mounted
+ * wherever `serve.nwcVerify` is mounted
  */
 declare function nwcVerifyUrl(endpoint: string, paymentHash: string, secret: string): Promise<string>;
 /**
@@ -109,25 +138,15 @@ interface NwcRailConfig extends RailConfig {
     /** Where the default conversion gets its rate, the median of four venues by default */
     rate?: Ticker;
     /** Where `serve.nwcVerify` is mounted, and the secret the hash is sealed with */
-    verifyThrough: {
-        endpoint: string;
-        secret: string;
-    };
+    verifyThrough: VerifyThrough;
     /** What the payer's wallet shows, the order's reference by default */
     description?: (order: Order) => string;
-    /** Sealed before the gateway sees it, the way the blind Lightning rail does */
+    /** Sealed before the gateway sees it, the way the Lightning rail does */
     sealed?: {
         secret: string;
         data: (order: Order) => unknown;
     };
 }
-/**
- * Sell for Lightning against a wallet of your own over NIP-47, for a wallet that
- * has no LUD-21 address to be watched at. Your node mints the invoice and releases
- * the preimage, so the proof comes from one hop nearer than any hosted address can
- * manage, and the gateway sees a hash and a URL of yours
- */
-declare function nwcRail(gateway: ThunderBridge, config: NwcRailConfig): Rail;
 
 /** What a shop knows about a sale before any rail exists */
 interface Order {
@@ -167,8 +186,8 @@ interface RailConfig {
     /** What `Leg.rail` says, so two rails of one kind can be told apart */
     name?: string;
 }
-/** A Lightning rail the gateway mints for, bound once and then given one order at a time */
-interface LightningRailConfig extends RailConfig {
+/** Who a Lightning rail pays and what one order costs there, whichever path verifies it */
+interface LightningRailSettings extends RailConfig {
     /** Priority list, the first address that can prove an invoice wins */
     paidTo: string | string[];
     /**
@@ -178,11 +197,8 @@ interface LightningRailConfig extends RailConfig {
     amount?: (order: Order) => Amount;
     /** Where the default conversion gets its rate, the median of four venues by default */
     rate?: Ticker;
-    /** Makes the mint safe to retry, the order's reference by default */
+    /** Makes the gateway's mint safe to retry, so it applies with `gatewayMints` only */
     idempotencyKey?: (order: Order) => string | undefined;
-}
-/** The same rail with the invoice resolved here, so the gateway is told neither address nor amount */
-interface BlindLightningRailConfig extends LightningRailConfig {
     /**
      * What the watcher needs and the gateway must not read, sealed under `secret`
      * for the invoice's payment hash before it goes anywhere near the gateway
@@ -191,18 +207,16 @@ interface BlindLightningRailConfig extends LightningRailConfig {
         secret: string;
         data: (order: Order) => unknown;
     };
-    /**
-     * Where your own `serve.verify` endpoint is mounted, and its secret. Without
-     * it the gateway is handed the wallet's own URL, which a gateway enforcing its
-     * verify challenge will refuse to poll
-     */
-    relayThrough?: {
-        endpoint: string;
-        secret: string;
-    };
     /** How the rail reaches wallets, pinned to the address it verified unless you say otherwise */
     send?: Send;
 }
+/**
+ * A Lightning rail, bound once and then given one order at a time. With
+ * `verifyThrough` the invoice is resolved here and the gateway polls your
+ * `serve.lightningVerify`, learning neither who is paid nor how much. With
+ * `gatewayMints` the gateway is told both, mints, and polls the wallet itself
+ */
+type LightningRailConfig = LightningRailSettings & VerifyPath;
 /** A bank rail: the account the money lands in, and where its arrival is read back from */
 interface BankRailConfig extends RailConfig {
     /** Long lived and server side. Every preimage is derived from it, so losing it loses every proof */
@@ -213,7 +227,7 @@ interface BankRailConfig extends RailConfig {
     verifyUrl: string;
     /** When this leg stops being payable, in unix seconds */
     expiresAt: (order: Order) => number;
-    /** Sealed before the gateway sees it, the way the blind Lightning rail does */
+    /** Sealed before the gateway sees it, the way the Lightning rail does */
     sealed?: {
         secret: string;
         data: (order: Order) => unknown;
@@ -244,13 +258,11 @@ declare function invoiceFrom(paidTo: string | string[], amount: Amount, send?: S
 declare class Rails {
     private readonly gateway;
     constructor(gateway: ThunderBridge);
-    /** Lightning, with the gateway minting against a priority list of addresses */
-    lightning(config: LightningRailConfig): Rail;
     /**
-     * Lightning, with the invoice resolved here so the gateway is told neither the
-     * address nor the amount
+     * Lightning against a priority list of addresses, verified through your
+     * `serve.lightningVerify`, or minted by the gateway when you say `gatewayMints`
      */
-    blindLightning(config: BlindLightningRailConfig): Rail;
+    lightning(config: LightningRailConfig): Rail;
     /** A bank transfer, proved the way a Lightning payment is */
     bank(config: BankRailConfig): Rail;
     /**
@@ -325,32 +337,8 @@ interface PaymentRequest {
     prove(): Promise<string | null>;
 }
 
-/** The wallet's own LUD-21 URL and the hash its preimage has to match */
-interface Relayed {
-    url: string;
-    hash: string;
-}
-/** The verify endpoint that asks the wallet for the gateway, and how often it may be asked */
-interface LightningVerifyConfig {
-    /** The secret the sealed wallet URL was made with, and nothing else uses it */
-    secret: string;
-    /**
-     * How often you want the gateway to ask, in seconds. It goes out as
-     * `Cache-Control: max-age`, so the pace is yours rather than the operator's.
-     * Five by default, which is what a Lightning checkout wants
-     */
-    pollEverySecs?: number;
-    /** How the relay reaches the wallet, pinned to the address it verified unless you say otherwise */
-    send?: Send;
-}
-/**
- * The URL to hand the gateway instead of the wallet's own, with the wallet's
- * sealed inside it. Point it at wherever `lightningVerifyEndpoint` is mounted
- */
-declare function relayedVerifyUrl(endpoint: string, wallet: Relayed, secret: string): Promise<string>;
-
 /** An LNURL-pay endpoint of your own: whose wallets it stands for, and what it charges */
-interface TriggerConfig {
+interface TriggerSettings {
     /** Priority list, quoted at payRequest and then pinned for the callback */
     paidTo: string | string[];
     /**
@@ -379,26 +367,6 @@ interface TriggerConfig {
     send?: Send;
     /** Override when a proxy hides the public URL from the request, no trailing slash */
     baseUrl?: string;
-    /**
-     * Resolve the address here and hand the gateway only a hash and a URL to poll,
-     * instead of asking it to mint. It then cannot tell who is being paid beyond
-     * the domain in the verify URL, nor how much at all, so the only refusal left
-     * to it is refusing everyone. Costs one more round trip and gives up the
-     * gateway's CORS proxying, which a server does not need anyway.
-     *
-     * A gateway that enforces its verify challenge will not poll a wallet's own
-     * LUD-21 URL, so pass `relayThrough` as well and the poll comes to you
-     */
-    blind?: boolean;
-    /**
-     * Where your own `serve.verify` endpoint is mounted, and the secret it was
-     * given. The wallet's URL is sealed inside the one the gateway is handed, so
-     * the gateway polls you and learns neither the wallet nor its provider
-     */
-    relayThrough?: {
-        endpoint: string;
-        secret: string;
-    };
     /**
      * What the watcher needs and the gateway must not have. `data` returns it and
      * `secret` encrypts it, so there is no way to hand the gateway something it
@@ -410,7 +378,13 @@ interface TriggerConfig {
         data: (minted: Minted) => unknown;
     };
 }
-/** What a blind mint produced, which is what the sealed payload is built from */
+/**
+ * The endpoint's settings and who the gateway polls. With `verifyThrough` the
+ * address is resolved here and the gateway polls your `serve.lightningVerify`,
+ * learning neither who is paid nor how much. With `gatewayMints` it quotes and
+ * mints, and polls the wallet itself
+ */
+type TriggerConfig = TriggerSettings & VerifyPath;
 /**
  * What a payer may choose to send, when the endpoint lets them choose at all.
  * Both ends are asked once per payRequest, so a fiat range moves with the rate
@@ -419,7 +393,7 @@ interface Range {
     least: Amount;
     most: Amount;
 }
-/** What a blind mint produced, which is what the sealed payload is built from */
+/** What a mint through your endpoint produced, which is what the sealed payload is built from */
 interface Minted {
     lnAddress: string;
     amountMsat: number;
@@ -486,12 +460,6 @@ type SelfConsistent<T extends Provable> = T & {
     status: "paid";
     preimage: string;
 };
-/**
- * What `SelfConsistent` was called before 2.2.0
- *
- * @deprecated Use `SelfConsistent`, which says the report was checked against itself and nothing else
- */
-type Proven<T extends Provable> = SelfConsistent<T>;
 /**
  * Whether a report agrees with itself: it says paid, and it carries a preimage
  * that hashes to the payment hash it itself names. Where an invoice comes with it,
@@ -506,12 +474,6 @@ type Proven<T extends Provable> = SelfConsistent<T>;
  * `proveSettlement` asks the recipient
  */
 declare function agreesWithItself<T extends Provable>(report: T): report is SelfConsistent<T>;
-/**
- * What `agreesWithItself` was called before 2.2.0
- *
- * @deprecated Use `agreesWithItself`, because it proves nothing beyond the report itself
- */
-declare const carriesProof: typeof agreesWithItself;
 /**
  * The most an operator may add over the recipient's own amount, in millisatoshi.
  * The proportion is what routing and the liquidity behind it costs, and the base
@@ -626,12 +588,6 @@ declare class Serve {
      * the gateway polls you and never the wallet
      */
     lightningVerify(config: LightningVerifyConfig): Handler;
-    /**
-     * What `lightningVerify` was called before 2.2.0
-     *
-     * @deprecated Use `lightningVerify`, beside `bankVerify` and `nwcVerify`
-     */
-    verify(config: LightningVerifyConfig): Handler;
     /** The verify endpoint a bank rail is polled at, answering off your own statement */
     bankVerify(config: BankVerifyConfig): Handler;
     /**
@@ -952,7 +908,7 @@ interface BankTransferParams {
     /** The account the money goes to, as an IBAN */
     iban: string;
     /**
-     * Where `bankVerifyEndpoint` is mounted, a public https URL with no query of
+     * Where `serve.bankVerify` is mounted, a public https URL with no query of
      * its own. Not needed when `answerBy` is "agent", because then nothing is polled
      */
     verifyUrl?: string;
@@ -1061,4 +1017,4 @@ interface BankAgentConfig {
  */
 declare function bankAgent(config: BankAgentConfig): () => void;
 
-export { type WebhookOptions as $, type AttendOptions as A, type BankAgentConfig as B, type Credit as C, type Proven as D, type RailConfig as E, type FollowOptions as F, Rails as G, type Handler as H, type Range as I, type Relayed as J, type SelfConsistent as K, type Leg as L, type Minted as M, type NwcConnection as N, type Order as O, type PaymentRequest as P, type Send as Q, type Rail as R, type Statement as S, ThunderBridge as T, Serve as U, type TicketOptions as V, type WaitOptions as W, type TriggerConfig as X, type WatchTicketConfig as Y, type WebhookCredential as Z, type WebhookHandlers as _, type BankOrder as a, type WrapAllowance as a0, agreesWithItself as a1, answerVerifyChallenge as a2, carriesProof as a3, invoiceFrom as a4, proveOrigin as a5, proveSettlement as a6, proveWrapped as a7, relayedVerifyUrl as a8, wrapFeeCeiling as a9, type BankTransfer as b, type BankTransferParams as c, type BankVerifyConfig as d, bankAgent as e, nwcVerifyEndpoint as f, type NwcInvoice as g, type NwcRailConfig as h, type NwcVerifyConfig as i, askWallet as j, nwcConnection as k, nwcHoldInvoice as l, nwcInvoice as m, nwcRail as n, nwcPay as o, nwcSettlement as p, nwcVerifyUrl as q, type ThunderBridgeOptions as r, type BankRailConfig as s, type BlindLightningRailConfig as t, type CreateOptions as u, type LightningRailConfig as v, type LightningVerifyConfig as w, type PaymentRequestInit as x, type PaymentRequestOptions as y, type Provable as z };
+export { relayedVerifyUrl as $, type AttendOptions as A, type BankAgentConfig as B, type Credit as C, type VerifyThrough as D, type WatchTicketConfig as E, type FollowOptions as F, type WebhookCredential as G, type Handler as H, type WebhookHandlers as I, type WebhookOptions as J, type WrapAllowance as K, type Leg as L, type Minted as M, type NwcConnection as N, type Order as O, type PaymentRequest as P, agreesWithItself as Q, type Rail as R, type Statement as S, ThunderBridge as T, answerVerifyChallenge as U, type VerifyPath as V, type WaitOptions as W, invoiceFrom as X, proveOrigin as Y, proveSettlement as Z, proveWrapped as _, type BankOrder as a, wrapFeeCeiling as a0, type NwcInvoice as a1, askWallet as a2, nwcConnection as a3, nwcHoldInvoice as a4, nwcInvoice as a5, nwcPay as a6, nwcSettlement as a7, nwcVerifyUrl as a8, type BankTransfer as b, type BankTransferParams as c, type BankVerifyConfig as d, bankAgent as e, type ThunderBridgeOptions as f, type BankRailConfig as g, type CreateOptions as h, type LightningRailConfig as i, type LightningRailSettings as j, type LightningVerifyConfig as k, type NwcRailConfig as l, type NwcVerifyConfig as m, type PaymentRequestInit as n, type PaymentRequestOptions as o, type Provable as p, type RailConfig as q, Rails as r, type Range as s, type Relayed as t, type SelfConsistent as u, type Send as v, Serve as w, type TicketOptions as x, type TriggerConfig as y, type TriggerSettings as z };