@toon-protocol/client 0.14.2 → 0.14.4

package/README.md

@@ -2,17 +2,17 @@
 
 The **client library** for TOON Protocol — _pay-to-write Nostr over Interledger (ILP)_. Use it to **pay for and publish** writes to a network of service nodes. **Reads are free; writes cost a signed EIP-712 payment-channel claim** against an on-chain deposit.
 
-> **`client` vs `townhouse`.** This package (`@toon-protocol/client`) is what an _app or end user_ uses to **pay** and publish. It does **not** run any relay or node. The nodes are operated separately by **`@toon-protocol/townhouse`** (the operator product, which runs an _apex_ connector plus `town` / `mill` / `dvm` children). Don't confuse the **client** (pays) with **townhouse** (operates), or **`town`** (a single Nostr-relay node) with **townhouse** (the whole operator stack).
+> **`client` vs `relay`.** This package (`@toon-protocol/client`) is what an _app or end user_ uses to **pay** and publish. It does **not** run any relay or node. The nodes are operated separately by **`@toon-protocol/relay`** (the operator product, which runs an _apex_ connector plus `town` / `swap` / `store` children). Don't confuse the **client** (pays) with **relay** (operates), or **`town`** (a single Nostr-relay node) with **relay** (the whole operator stack).
 
 ## Which call pays which node
 
-Every write is an ILP packet carrying a signed payment-channel claim. The client reaches all node types **through a townhouse apex** (`g.townhouse`): the apex validates the claim, takes its fee, and forwards the packet to the destination node, which returns FULFILL (accepted) or REJECT. The method you call determines which node type you pay:
+Every write is an ILP packet carrying a signed payment-channel claim. The client reaches all node types **through a relay apex** (`g.proxy`): the apex validates the claim, takes its fee, and forwards the packet to the destination node, which returns FULFILL (accepted) or REJECT. The method you call determines which node type you pay:
 
 | Client call                       | Node type | What it does                                                                                                                                              |
 | --------------------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `client.publishEvent(event)`      | **town**  | Publish a Nostr event (e.g. `kind:1`) to the relay.                                                                                                       |
-| `requestBlobStorage(client, …)`   | **dvm**   | NIP-90 compute/storage. Builds and publishes a `kind:5094` event that uploads a blob to Arweave — the job request **is** the payment — and decodes the Arweave tx ID from the FULFILL response. |
-| `client.sendSwapPacket(…)`        | **mill**  | Multi-chain token swap (low-level). Most callers use the higher-level `streamSwap()` from `@toon-protocol/sdk`, which is built on `sendSwapPacket`.       |
+| `requestBlobStorage(client, …)`   | **store** | NIP-90 compute/storage. Builds and publishes a `kind:5094` event that uploads a blob to Arweave — the job request **is** the payment — and decodes the Arweave tx ID from the FULFILL response. |
+| `client.sendSwapPacket(…)`        | **swap**  | Multi-chain token swap (low-level). Most callers use the higher-level `streamSwap()` from `@toon-protocol/sdk`, which is built on `sendSwapPacket`.       |
 
 ## What It Does
 
@@ -21,7 +21,7 @@ This client handles:
 - **ILP Micropayments**: Pay to publish Nostr events (reads are free)
 - **Payment Channels**: Automatic on-chain channel creation with off-chain settlement via signed balance proofs
 - **Unified Identity**: One Nostr key = one EVM address (both secp256k1, derived automatically) — or a single BIP-39 **mnemonic** to derive a full multi-chain identity
-- **Multi-Chain Settlement**: Sign payment-channel claims on EVM (EIP-712), Solana (Ed25519), and Mina (Pallas) from one mnemonic. A Townhouse apex validates the claim and redeems it on-chain on the matching chain (EVM/Solana credit the recipient; Mina redeems each claim on-chain with recipient credit-at-close deferred — see [Multi-Chain Settlement notes](#identity--multi-chain-settlement))
+- **Multi-Chain Settlement**: Sign payment-channel claims on EVM (EIP-712), Solana (Ed25519), and Mina (Pallas) from one mnemonic. A relay apex validates the claim and redeems it on-chain on the matching chain (EVM/Solana credit the recipient; Mina redeems each claim on-chain with recipient credit-at-close deferred — see [Multi-Chain Settlement notes](#identity--multi-chain-settlement))
 - **Multi-Hop Routing**: Publish to any destination address (`destination` / `destinationAddress`), not just your direct peer
 - **Network Bootstrap**: Automatically discover and register with ILP peers via NIP-02 follow lists
 - **TOON Encoding**: Native binary format for agent-friendly event encoding
@@ -41,7 +41,7 @@ pnpm add mina-signer
 
 - **Node.js ≥ 20** — these packages are ESM.
 - **A TOON apex to pay.** You don't run any node yourself; you connect to a running
-  [`@toon-protocol/townhouse`](https://www.npmjs.com/package/@toon-protocol/townhouse) apex (or any
+  [`@toon-protocol/relay`](https://www.npmjs.com/package/@toon-protocol/relay) apex (or any
   TOON connector) and pay it. From its operator you need:
   - a **connector endpoint** — an HTTP `connectorUrl` and/or a BTP WebSocket `btpUrl`;
   - a **settlement-chain RPC URL** and a **funded key** on that chain, so the client can open a
@@ -167,13 +167,13 @@ console.log('Mina:  ', client.getMinaAddress());   // base58, after start() (nee
 - **Mina is optional**: it requires the `mina-signer` peer dependency (see Installation). Without it, the client still works for Nostr/EVM/Solana and `getMinaAddress()` returns `undefined`.
 - **Security**: JavaScript strings can't be zeroed from memory, so a `mnemonic` may linger in the heap. For high-security contexts, derive keys yourself (e.g. via `KeyManager`) and pass a pre-derived `secretKey`.
 - **Per-chain claim formats.** Each publish carries a balance-proof claim in the format that destination chain's connector verifier expects — EVM via EIP-712, Solana as a raw Ed25519 message over the on-chain payment-channel message (`channel_pda ‖ nonce ‖ transferredAmount`), Mina as a Pallas-Schnorr claim over a Poseidon `balanceCommitment`. `ToonClient` selects the right signer for the negotiated channel automatically; you do not pick the format. Canonical layouts live in `@toon-protocol/core` (`packages/core/src/settlement/`) so client signers and connector verifiers cannot drift.
-- **On-chain redemption is automatic, and driven by the apex — not the client.** You sign off-chain claims; the Townhouse apex validates them, fulfills, and (once a per-channel threshold is crossed) submits the on-chain redemption itself. EVM and Solana credit the recipient on-chain (Solana at channel close, `SETTLE_CHANNEL`). On **Mina** each paid publish redeems on-chain (`claimFromChannel`, the apex co-signs the counterparty signature; the zkApp nonce and balance commitment advance), and **the recipient's tokens are credited at channel close** via the Story 34.4 fund-custody zkApp (`@toon-protocol/connector` ≥3.10.0): the deposit is escrowed on the zkApp account and `settle()` drains it to the participants (recipient + depositor refund). Verified against `@toon-protocol/connector` 3.10.0.
+- **On-chain redemption is automatic, and driven by the apex — not the client.** You sign off-chain claims; the relay apex validates them, fulfills, and (once a per-channel threshold is crossed) submits the on-chain redemption itself. EVM and Solana credit the recipient on-chain (Solana at channel close, `SETTLE_CHANNEL`). On **Mina** each paid publish redeems on-chain (`claimFromChannel`, the apex co-signs the counterparty signature; the zkApp nonce and balance commitment advance), and **the recipient's tokens are credited at channel close** via the Story 34.4 fund-custody zkApp (`@toon-protocol/connector` ≥3.10.0): the deposit is escrowed on the zkApp account and `settle()` drains it to the participants (recipient + depositor refund). Verified against `@toon-protocol/connector` 3.10.0.
 
 ---
 
 ## Uploading a blob to a DVM (Arweave storage)
 
-To store a blob permanently on Arweave, pay a **dvm** node with a `kind:5094` NIP-90 request. The `requestBlobStorage` helper builds the signed event, publishes it through your `ToonClient` (reusing its claim/channel plumbing), and decodes the Arweave transaction ID from the FULFILL response:
+To store a blob permanently on Arweave, pay a **store** node with a `kind:5094` NIP-90 request. The `requestBlobStorage` helper builds the signed event, publishes it through your `ToonClient` (reusing its claim/channel plumbing), and decodes the Arweave transaction ID from the FULFILL response:
 
 ```typescript
 import { ToonClient, requestBlobStorage } from '@toon-protocol/client';
@@ -183,7 +183,7 @@ const result = await requestBlobStorage(client, secretKey, {
   blobData: new Uint8Array([1, 2, 3, 4]),
   contentType: 'application/octet-stream',
   ilpAmount: 50_000n, // USDC micro-units; also used as the event's `bid` if `bid` is omitted
-  destination: 'g.toon.peer1', // the DVM's ILP address (defaults to the client's destinationAddress)
+  destination: 'g.toon.peer1', // the store node's ILP address (defaults to the client's destinationAddress)
 });
 
 if (result.success) {
@@ -239,7 +239,7 @@ await client.publishEvent(event, { claim });
 2. **Channel Creation**: Opens an on-chain payment channel on the negotiated chain — using your derived EVM address (EVM), the Ed25519 channel PDA (Solana), or the deployed zkApp account (Mina) when the matching `solanaChannel` / `minaChannel` config is provided
 3. **Off-chain Payments**: Signed balance proofs (chain-appropriate format) settle payments off-chain
 4. **Auto-tracking**: ChannelManager automatically tracks channels and increments nonces
-5. **On-chain redemption**: A Townhouse apex auto-redeems claims on-chain once a per-channel threshold is crossed (see [Multi-Chain Settlement](#identity--multi-chain-settlement) for the EVM/Solana/Mina specifics and the Mina credit-at-close deferral)
+5. **On-chain redemption**: A relay apex auto-redeems claims on-chain once a per-channel threshold is crossed (see [Multi-Chain Settlement](#identity--multi-chain-settlement) for the EVM/Solana/Mina specifics and the Mina credit-at-close deferral)
 
 ### Using a Separate EVM Key (Advanced)
 
@@ -304,10 +304,9 @@ See [examples/client-example/](../../examples/client-example/) for standalone cl
 ## Related Packages
 
 - **[@toon-protocol/core](../core/)** — Core protocol (peer discovery, bootstrap, `buildBlobStorageRequest`)
-- **[@toon-protocol/relay](../relay/)** — Nostr relay with ILP payment gating (`encodeEventToToon` / `decodeEventFromToon`)
-- **[@toon-protocol/sdk](../sdk/)** — Higher-level helpers including `streamSwap()` for multi-chain swaps via a **mill**
+- **[@toon-protocol/relay](../relay/)** — Operator product running the apex connector plus town/swap/store nodes; also exports `encodeEventToToon` / `decodeEventFromToon` for event encoding
+- **[@toon-protocol/sdk](../sdk/)** — Higher-level helpers including `streamSwap()` for multi-chain swaps via a **swap**
 - **[@toon-protocol/bls](../bls/)** — Business Logic Server (pricing, validation, storage)
-- **[@toon-protocol/townhouse](../townhouse/)** — The operator product that runs the apex + town/mill/dvm nodes you pay
 
 ---
 

package/dist/index.d.ts

@@ -172,7 +172,7 @@ interface ToonClientConfig {
      * preferred tokens, EVM TokenNetwork addresses, and the Solana/Mina channel
      * params (programId / zkApp) — from the shared core presets
      * (`resolveClientNetwork`), so the caller no longer hand-wires every address.
-     * This is the client-side mirror of the townhouse node's `network` selector;
+     * This is the client-side mirror of the relay node's `network` selector;
      * both resolve the SAME deployed contracts.
      *
      * Precedence: any explicit per-chain field (`supportedChains`,
@@ -1013,7 +1013,7 @@ declare class ToonClient {
     }): Promise<RequestBlobStorageResult>;
     /**
      * Per-chain settlement readiness for the configured `network` tier, mirroring
-     * the townhouse node's status. Returns `undefined` when no named `network` is
+     * the relay node's status. Returns `undefined` when no named `network` is
      * set (or `network: 'custom'`), since there is no preset tier to report on.
      */
     getNetworkStatus(): NetworkFamilyStatus | undefined;
@@ -1099,7 +1099,7 @@ declare class ToonClient {
      */
     h402Fetch(url: string, opts?: H402FetchOptions): Promise<Response>;
     /**
-     * Sends a raw swap ILP packet (Story 12.5) to a Mill peer with an attached
+     * Sends a raw swap ILP packet (Story 12.5) to a swap peer with an attached
      * balance-proof claim. This is a lower-level surface than `publishEvent`:
      * it forwards the raw `IlpSendResult` so the sender (`streamSwap()`) can
      * decode FULFILL metadata itself.
@@ -1864,7 +1864,7 @@ declare class EvmSigner {
  * is what makes a client-issued Solana payment-channel claim (paying the apex
  * to write) acceptable on connector 3.9.0.
  *
- * NOTE: this is a DIFFERENT message from the Mill ↔ sender swap-claim wire
+ * NOTE: this is a DIFFERENT message from the swap peer ↔ sender swap-claim wire
  * contract (`balanceProofHashSolana`, SDK `verifyEd25519Signature`). The client
  * here is paying a payment-channel claim to the apex, not issuing a swap claim,
  * so it must sign the connector's on-chain payment-channel message. `channelId`
@@ -1934,7 +1934,7 @@ interface MinaSignerOptions {
  * off-chain `verifyBalanceProof` accepts EITHER, so off-chain store/FULFILL works
  * in both cases — only on-chain settle requires the participant form.
  *
- * NOTE: this is a DIFFERENT message + format from the Mill ↔ sender swap-claim
+ * NOTE: this is a DIFFERENT message + format from the swap peer ↔ sender swap-claim
  * wire contract (`balanceProofFieldsMina` in `@toon-protocol/core`, verified by
  * the SDK's `verifyMinaSignature`). The client here pays a payment-channel claim
  * to the apex, so it signs the connector's on-chain payment-channel scheme; the
@@ -2406,7 +2406,7 @@ declare function buildStoreWriteEnvelope(event: NostrEvent, requestTarget?: stri
  * dependency-free helper that returns the status code + raw body string, which
  * is all the publish/upload paths need.
  *
- * DEFENSIVE: not every FULFILL is HTTP-enveloped (e.g. Mill-swap raw-TOON
+ * DEFENSIVE: not every FULFILL is HTTP-enveloped (e.g. swap peer raw-TOON
  * FULFILLs go through `sendSwapPacket`, not these paths). If the decoded data
  * does not begin with an `HTTP/<v>` status line, `isHttp` is `false` and the
  * caller should fall back to its prior (non-HTTP) interpretation rather than
@@ -2467,7 +2467,7 @@ interface ClientSettlementInfo {
 declare function applyNetworkPresets(config: ToonClientConfig): ToonClientConfig;
 /**
  * Returns per-chain settlement readiness for the configured `network` tier,
- * mirroring the townhouse node's status. Returns `undefined` when `network` is
+ * mirroring the relay node's status. Returns `undefined` when `network` is
  * unset or `'custom'` (no preset tier to report on).
  */
 declare function getNetworkStatus(config: ToonClientConfig): NetworkFamilyStatus | undefined;
@@ -2977,9 +2977,24 @@ interface FundWalletResult {
 interface FundWalletOptions {
     /** Custom fetch implementation (for testing / custom transports). */
     fetchImpl?: typeof fetch;
-    /** Request timeout in milliseconds (default: 30000). */
+    /**
+     * Request timeout in milliseconds. Defaults to {@link defaultFaucetTimeout}
+     * for the chain (fast 30s for evm/solana, a longer 120s for the slow-settling
+     * mina faucet).
+     */
     timeout?: number;
 }
+/**
+ * Default faucet request timeout (ms) for a chain.
+ *
+ * EVM and Solana faucets respond in a few seconds, so 30s is plenty. The Mina
+ * faucet sends native MINA *and* mints USDC on a chain that settles much more
+ * slowly: the drip routinely succeeds server-side (the faucet logs
+ * `✅ Mina faucet request completed`) but takes well over 30s to answer the
+ * HTTP request, so a flat 30s budget makes the client give up on a request that
+ * actually worked. Give mina a much longer budget.
+ */
+declare function defaultFaucetTimeout(chain: FaucetChain): number;
 /**
  * Drip test funds to `address` on `chain` from the devnet `faucetUrl`.
  *
@@ -3271,7 +3286,7 @@ declare function isPrfSupported(): boolean;
 /**
  * Node-only encrypted mnemonic keystore for @toon-protocol/client.
  *
- * Mirrors the Townhouse node wallet crypto (`packages/townhouse/src/wallet/
+ * Mirrors the relay node wallet crypto (`packages/relay/src/wallet/
  * crypto.ts`): a BIP-39 mnemonic is encrypted at rest with scrypt (KDF) +
  * AES-256-GCM (authenticated encryption), serialized as JSON, and written to
  * disk with mode 0o600. Decryption requires the operator password; a wrong
@@ -3286,7 +3301,7 @@ declare function isPrfSupported(): boolean;
  */
 /**
  * Encrypted keystore file format (JSON, all binary fields base64-encoded).
- * Wire-compatible with Townhouse's `EncryptedWallet`.
+ * Wire-compatible with the relay node's `EncryptedWallet`.
  */
 interface EncryptedKeystore {
     /** scrypt salt (base64). */
@@ -3337,8 +3352,8 @@ declare function importKeystore(path: string, mnemonic: string, password: string
 declare function loadKeystore(path: string, password: string): string;
 /**
  * Serialize and write an encrypted keystore to disk with mode 0o600
- * (owner read/write only), mirroring the Townhouse wallet file permissions.
+ * (owner read/write only), mirroring the relay node wallet file permissions.
  */
 declare function writeKeystoreFile(path: string, keystore: EncryptedKeystore): void;
 
-export { type BackupPayload, type BalanceProofParams, BtpRuntimeClient, type BtpRuntimeClientConfig, type ChainMetadata, type ChainSigner, ChannelManager, type ClaimMessage, type ClaimResolver, ConnectorError, type DiscoveredIlpPeer, type EVMClaimMessage, type EncryptedKeystore, EvmSigner, type FaucetChain, type FundWalletOptions, type FundWalletResult, type H402FetchOptions, Http402Client, type Http402ClientConfig, HttpConnectorAdmin, type HttpConnectorAdminConfig, HttpIlpClient, type HttpIlpClientConfig, type HttpIlpClientFactory, HttpRuntimeClient, type HttpRuntimeClientConfig, ILP_CLAIM_HEADER, ILP_CLAIM_WRAPPED_HEADER, ILP_PEER_ID_HEADER, type IlpTransportChoice, type InteractionResultContent, KeyManager, type KeyManagerConfig, type MinaClaimMessage, type MinaDepositReader, MinaSigner, type MinaSignerOptions, NetworkError, OnChainChannelClient, type OnChainChannelClientConfig, type ParsedFulfillHttp, type ParsedX402Challenge, type PasskeyInfo, type PetDvmProvider, type PetInteractionEventData, type PetInteractionRequestParams, type PetInteractionResultData, type PetListing, type PetListingFilterOptions, type PetListingParams, type PetPurchaseRequestParams, type ProofStatus, type PublishEventResult, type RequestBlobStorageParams, type RequestBlobStorageResult, type RetryOptions, type SelectIlpTransportOptions, type SignedBalanceProof, type SolanaChannelClientOptions, type SolanaClaimMessage, SolanaSigner, type StatValues, type ToonChannelAccept, ToonClient, type ToonClientConfig, ToonClientError, type ToonIdentity, type ToonSigners, type ToonStartResult, type UnsignedNostrEvent, ValidationError, type VaultData, applyDefaults, applyNetworkPresets, buildBackupEvent, buildBackupFilter, buildPetInteractionRequest, buildPetListingEvent, buildPetPurchaseRequest, buildSettlementInfo, buildStoreWriteEnvelope, decryptMnemonic, deriveFromNsec, deriveFullIdentity, deriveNostrKeyFromMnemonic, encryptMnemonic, filterPetDvmProviders, filterPetListings, fundWallet, generateKeystore, generateMnemonic, generateRandomIdentity, getNetworkStatus, httpEndpointToBtpUrl, importKeystore, isPrfSupported, loadKeystore, parseBackupPayload, parseFulfillHttp, parseFulfillHttpBytes, parseHttpResponse, parsePetInteractionEvent, parsePetInteractionResult, parsePetListing, parseX402Body, parseX402Challenge, proxyIlpEndpoint, readDiscoveredIlpPeer, readMinaDepositTotal, requestBlobStorage, selectIlpTransport, serializeHttpRequest, validateConfig, validateMnemonic, withRetry, writeKeystoreFile };
+export { type BackupPayload, type BalanceProofParams, BtpRuntimeClient, type BtpRuntimeClientConfig, type ChainMetadata, type ChainSigner, ChannelManager, type ClaimMessage, type ClaimResolver, ConnectorError, type DiscoveredIlpPeer, type EVMClaimMessage, type EncryptedKeystore, EvmSigner, type FaucetChain, type FundWalletOptions, type FundWalletResult, type H402FetchOptions, Http402Client, type Http402ClientConfig, HttpConnectorAdmin, type HttpConnectorAdminConfig, HttpIlpClient, type HttpIlpClientConfig, type HttpIlpClientFactory, HttpRuntimeClient, type HttpRuntimeClientConfig, ILP_CLAIM_HEADER, ILP_CLAIM_WRAPPED_HEADER, ILP_PEER_ID_HEADER, type IlpTransportChoice, type InteractionResultContent, KeyManager, type KeyManagerConfig, type MinaClaimMessage, type MinaDepositReader, MinaSigner, type MinaSignerOptions, NetworkError, OnChainChannelClient, type OnChainChannelClientConfig, type ParsedFulfillHttp, type ParsedX402Challenge, type PasskeyInfo, type PetDvmProvider, type PetInteractionEventData, type PetInteractionRequestParams, type PetInteractionResultData, type PetListing, type PetListingFilterOptions, type PetListingParams, type PetPurchaseRequestParams, type ProofStatus, type PublishEventResult, type RequestBlobStorageParams, type RequestBlobStorageResult, type RetryOptions, type SelectIlpTransportOptions, type SignedBalanceProof, type SolanaChannelClientOptions, type SolanaClaimMessage, SolanaSigner, type StatValues, type ToonChannelAccept, ToonClient, type ToonClientConfig, ToonClientError, type ToonIdentity, type ToonSigners, type ToonStartResult, type UnsignedNostrEvent, ValidationError, type VaultData, applyDefaults, applyNetworkPresets, buildBackupEvent, buildBackupFilter, buildPetInteractionRequest, buildPetListingEvent, buildPetPurchaseRequest, buildSettlementInfo, buildStoreWriteEnvelope, decryptMnemonic, defaultFaucetTimeout, deriveFromNsec, deriveFullIdentity, deriveNostrKeyFromMnemonic, encryptMnemonic, filterPetDvmProviders, filterPetListings, fundWallet, generateKeystore, generateMnemonic, generateRandomIdentity, getNetworkStatus, httpEndpointToBtpUrl, importKeystore, isPrfSupported, loadKeystore, parseBackupPayload, parseFulfillHttp, parseFulfillHttpBytes, parseHttpResponse, parsePetInteractionEvent, parsePetInteractionResult, parsePetListing, parseX402Body, parseX402Challenge, proxyIlpEndpoint, readDiscoveredIlpPeer, readMinaDepositTotal, requestBlobStorage, selectIlpTransport, serializeHttpRequest, validateConfig, validateMnemonic, withRetry, writeKeystoreFile };

package/dist/index.js

@@ -3987,7 +3987,7 @@ var ToonClient = class {
   }
   /**
    * Per-chain settlement readiness for the configured `network` tier, mirroring
-   * the townhouse node's status. Returns `undefined` when no named `network` is
+   * the relay node's status. Returns `undefined` when no named `network` is
    * set (or `network: 'custom'`), since there is no preset tier to report on.
    */
   getNetworkStatus() {
@@ -4305,7 +4305,7 @@ var ToonClient = class {
     return client.fetch(url, opts);
   }
   /**
-   * Sends a raw swap ILP packet (Story 12.5) to a Mill peer with an attached
+   * Sends a raw swap ILP packet (Story 12.5) to a swap peer with an attached
    * balance-proof claim. This is a lower-level surface than `publishEvent`:
    * it forwards the raw `IlpSendResult` so the sender (`streamSwap()`) can
    * decode FULFILL metadata itself.
@@ -5414,6 +5414,9 @@ function buildPetPurchaseRequest(params) {
 }
 
 // src/faucet.ts
+function defaultFaucetTimeout(chain) {
+  return chain === "mina" ? 12e4 : 3e4;
+}
 function faucetPath(chain) {
   switch (chain) {
     case "evm":
@@ -5434,7 +5437,7 @@ async function fundWallet(faucetUrl, address, chain, options = {}) {
   const base = faucetUrl.replace(/\/+$/, "");
   const url = `${base}${faucetPath(chain)}`;
   const fetchImpl = options.fetchImpl ?? fetch;
-  const timeout = options.timeout ?? 3e4;
+  const timeout = options.timeout ?? defaultFaucetTimeout(chain);
   const controller = new AbortController();
   const timeoutId = setTimeout(() => controller.abort(), timeout);
   let response;
@@ -6557,6 +6560,7 @@ export {
   buildUiCoordinate,
   classifyIntent,
   decryptMnemonic2 as decryptMnemonic,
+  defaultFaucetTimeout,
   deriveFromNsec,
   deriveFullIdentity,
   deriveNostrKeyFromMnemonic,