Biscuit Wallet
Biscuit Wallet
Docs › Ethereum, USDT and USDC
Biscuit doesn’t download the Ethereum blockchain. It asks public Ethereum nodes for your balances, fees and nonce, and sends your transactions through them. The list of your past transactions comes from Blockscout, an open source explorer.
To give your balance, a node has to know your address, as an Electrum server does for Bitcoin. Biscuit asks one node at a time and moves to the next if it doesn’t answer. Blockscout only ever shows the history: your balance, the fees and what you send never depend on it.
Biscuit uses these public nodes: PublicNode, dRPC, MEV Blocker and Flashbots, and eth.blockscout.com for the history.
In Settings › Network › Ethereum, set the address of your own node (Geth, Nethermind, Erigon… on Umbrel, Start9 or a machine of yours, usually port 8545), and Biscuit reads and sends through it only. You can set your own Blockscout for the history too. Addresses start with https://; http:// is accepted for an .onion address or a machine on your local network.
In Tor mode, nodes and Blockscout are reached through Tor. With onion services only, Ethereum works only with .onion addresses in the settings, the history included: none of the built-in ones is one.