Docs Open Console

Blockchain Nodes

How U.CASH watches chains: your own nodes first, then a provider cascade, with a credit-metered last resort - payments are never lost to a single dead source.

Detection architecture#

Every payment check walks a priority chain:

  1. Your own node (BTC, ETH, Solana, Lightning) if configured
  2. Your custom explorer if configured (see Custom Explorers)
  3. Provider cascade - multiple independent public sources per coin, tried in order until one answers
  4. CryptoAPIs - the credit-metered last resort, used only when the free cascade came up empty

For EVM chains, 19 networks carry ordered default public RPC endpoints (official-first), and token chains fall back to direct keyless RPC after the cascade. A failing source never blocks a payment - the next source takes over.

Running your own nodes#

Under Settings → Nodes & Testnet (requires the wallets permission) you can connect:

NodeSettingsWhat it unlocks
BitcoinNode URL, optional headers, xpubAddress generation from your xpub, sweeping transfers, and on-chain refunds
EthereumNode URL, headers, network (mainnet/Sepolia)Address generation, transfers, instant conversion, refunds
SolanaNode URLDetection and transfers on Solana
Lightning (LND)REST URL, macaroonLightning invoices and instant settlement - see Lightning Network

Node URLs must be HTTPS with valid certificates; extra headers are supported for proxies and authentication. Wallet-affecting settings require the wallets permission.

Provider keys (bring your own)#

Detection uses several data providers. You can plug in your own API keys for any of them under the blockchain settings - Blockdaemon, Tatum, Etherscan, Ethplorer, and CryptoAPIs - and your keys are used ahead of platform capacity. Keys are stored encrypted.

Operating notes#

  • Scans run continuously: pending transactions are re-checked every 2 minutes; payments up to 48 hours old stay in the scan window
  • Non-custodial either way: nodes you run only add capabilities (xpub generation, sweeps, refunds) - without any node, payments still detect and settle to your addresses
  • Rate limits: your own nodes and explorer keys take the load off shared providers, which matters at volume
  • Monero: detection uses Monero-specific sources; incoming payments are matched by amount and payment id