mineracksbitcoin.mineracks.com/Connect/Electrum servers Price and FX APIElectrum · mempool-electrs The directory
Connect · Electrum servers
mainnet

Electrum · Fulcrum

Fulcrum 2.1.1 over TLS. Sparrow, Electrum, BlueWallet, Nunchuk.

Connect
ssl://electrum.mineracks.com:50002
Also fulcrum.mineracks.com, knots.mineracks.com

What it is

The Electrum protocol is how most Bitcoin wallets talk to a full node without running one. A wallet sends the script hashes of its addresses; the server answers with balances, history and unspent outputs, and pushes a notification when something new arrives. Fulcrum is a fast, C++ implementation of that server on top of our own Bitcoin Core node.

Why it matters: a wallet that uses someone else's Electrum server hands that server the complete list of its addresses. Using a server run by a party you know, or your own, is the difference between private and surveilled. Ours is here so you have a named, accountable option rather than a random public server.

What people use it for

Wallet by wallet

Sparrow
Preferences → Server → Private Electrum: electrum.mineracks.com, port 50002, SSL on.
Electrum desktop
Network → uncheck auto-connect → server electrum.mineracks.com:50002:s.
BlueWallet
Settings → Network → Electrum server: host electrum.mineracks.com, SSL port 50002.
Nunchuk
Settings → Network → Electrum: ssl://electrum.mineracks.com:50002.

How we run it

Fulcrum indexing our mainnet Bitcoin Core (unpruned, txindex) in Brisbane.
TLS is terminated on our own edge host and routed by server name to the indexer over the private network. No third-party proxy in the path.

Trust, stated plainly

We can see which addresses you query, as any Electrum server can. Use Tor, or step up to the Bitcoin Core P2P card and run your own node.
No account, no rate limit today. Abuse gets an IP block, not a login wall.

Learn more