---
name: mineracks-bitcoin-infrastructure
description: Use the public Bitcoin infrastructure mineracks runs (explorers, Electrum, silent payments, VSS, DLC oracle, Spark testbed, faucet, nodes, mining, payments). Read before connecting a wallet, node, miner or SDK to a *.mineracks.com service.
---

# mineracks public Bitcoin infrastructure

Operator: mineracks Pty Ltd, Brisbane, Australia · contact info@mineracks.com · generated 2026-09-21.
Machine-readable list: https://bitcoin.mineracks.com/services.json · live status: https://bitcoin.mineracks.com/status.json (fields: slug → ok|down|unknown, checked, source).

Rules for agents: everything is free and public; respect the per-IP limits on each service; signet/testnet4 services carry no value; mainnet services move real money — never send funds to a card's connect string, they are endpoints, not addresses. Paid higher quotas will use L402 (HTTP 402 + Lightning invoice, no account) on the price API, VSS and the oracle; look for `WWW-Authenticate: L402` before assuming a 402 is an error.


## Explore — See the chain and the numbers behind it.


- page: https://mempool.mineracks.com

- page: https://signet.mineracks.com

- page: https://testnet4.mineracks.com

- page: https://liquid.mineracks.com

### MutinyNet node (mutinynet, Explorers)
- connect: `https://mutinynet.mineracks.com/api/`
- what: Explorer and Esplora API on MutinyNet, the custom signet with 30-second blocks.
- status: degraded — Explorer and Esplora API on MutinyNet, the custom signet with 30-second blocks.
- how: Explorer at /explorer/, Esplora API under /api/ (same paths as mempool.mineracks.com). Coin from faucet.mutinynet.com.
- trust: A follower node: we validate against MutinyNet's published signet challenge and serve what their miner produces. If their chain stalls, so does this view.
- probe: `https://mutinynet.mineracks.com/api/blocks/tip/height`
- page: https://bitcoin.mineracks.com/mutinynet/

- page: https://prices.mineracks.com

## Connect — Point your wallet at a server you can name.


### Electrum · Fulcrum (mainnet, Electrum servers)
- connect: `ssl://electrum.mineracks.com:50002`
- aliases: `fulcrum.mineracks.com`, `knots.mineracks.com`
- what: Fulcrum 2.1.1 over TLS. Sparrow, Electrum, BlueWallet, Nunchuk.
- how: Fulcrum indexing our mainnet Bitcoin Core (unpruned, txindex) in Brisbane.
- how: 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: 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.
- trust: No account, no rate limit today. Abuse gets an IP block, not a login wall.
- probe: `tcp://electrum.mineracks.com:50002`
- page: https://bitcoin.mineracks.com/electrum-fulcrum/

### Electrum · mempool-electrs (mainnet, Electrum servers)
- connect: `ssl://electrs.mineracks.com:50002`
- what: electrs with the same data as the explorer.
- how: mempool-electrs (the explorer's backend) exposed on the Electrum protocol, TLS at our edge.
- trust: Same visibility caveat as any Electrum server: the operator sees the addresses you ask about.
- probe: `tcp://electrs.mineracks.com:50002`
- page: https://bitcoin.mineracks.com/electrum-electrs/

### signet Electrum (signet, Electrum servers)
- connect: `ssl://signet-electrum.mineracks.com:50002`
- what: Fulcrum on signet for wallet development.
- how: Fulcrum on our signet node. Point Sparrow or BDK at it to develop against a chain with no value.
- probe: `tcp://signet-electrum.mineracks.com:50002`
- page: https://bitcoin.mineracks.com/signet-electrum/

### testnet4 Electrum (testnet4, Electrum servers)
- connect: `ssl://testnet4-electrum.mineracks.com:50002`
- what: mempool-electrs on testnet4, the chain wallets are moving their test suites to.
- how: Same TLS edge as our other Electrum hosts (SNI-routed). Sparrow: Server → Electrum → testnet4-electrum.mineracks.com:50002. Coin from the testnet4 faucet below.
- note: testnet3 is deliberately not offered: it is deprecated upstream and its coin is traded, which defeats the purpose of a test network.
- probe: `tcp://testnet4-electrum.mineracks.com:50002`
- page: https://bitcoin.mineracks.com/testnet4-electrum/

### MutinyNet Electrum (mutinynet, Electrum servers)
- connect: `ssl://mutinynet-electrum.mineracks.com:50002`
- what: mempool-electrs on MutinyNet, the 30-second-block signet Lightning tooling tests on.
- status: degraded — mempool-electrs on MutinyNet, the 30-second-block signet Lightning tooling tests on.
- how: Point a signet-capable wallet at it (MutinyNet is a signet with different chain parameters: Sparrow, BDK and LDK builds that support custom signets work; stock Bitcoin Core does not).
- probe: `tcp://mutinynet-electrum.mineracks.com:50002`
- page: https://bitcoin.mineracks.com/mutinynet-electrum/

### Liquid Electrum (liquid, Electrum servers)
- connect: `ssl://liquid-electrum.mineracks.com:50002`
- what: electrs-esplora for Green and other Liquid wallets.
- how: electrs-liquid over our Elements node; TLS at our edge.
- probe: `tcp://liquid-electrum.mineracks.com:50002`
- page: https://bitcoin.mineracks.com/liquid-electrum/

- page: https://silentpay.mineracks.com

- page: https://silentpay.mineracks.com

- page: https://nostr.mineracks.com

- page: https://mineracks.com/.well-known/nostr.json?name=mineracks

- page: https://github.com/mineracks/mineracks-signer/releases

### Monero remote node (monero, Nostr and adjacent)
- connect: `http://xmr.mineracks.com:18089`
- what: Restricted RPC remote node, clearnet and Tor.
- how: Restricted RPC (no wallet functions) for any Monero wallet. Also as a v3 onion for Feather, Cake and Monerujo.
- trust: Plain HTTP on 18089 by design of the protocol; the remote node sees your IP and the outputs you fetch.
- probe: `tcp://xmr.mineracks.com:18089`
- page: https://bitcoin.mineracks.com/monero/

### Place search · Photon (none, Maps without logs)
- connect: `https://geocode.mineracks.com/api?q=`
- what: Type an address, get coordinates. OpenStreetMap data on our box, no access log, the query is never written down.
- how: GET /api?q=<text>&limit=5 returns GeoJSON (Photon's format). Queries under four characters are refused (a keystroke is not a search); 5 requests per second per client, 4 connections.
- how: Coverage today: Australia (the OSM extract loaded 2026-09-20). Other regions are a data download away; ask.
- trust: OpenStreetMap data under ODbL; results are as good as the map is. We see an address and a query in flight and keep neither.
- probe: `https://geocode.mineracks.com/healthz`
- page: https://bitcoin.mineracks.com/geocode/

### Map tiles · Protomaps (none, Maps without logs)
- connect: `https://tiles.mineracks.com/planet.pmtiles`
- what: The whole world's vector map as one file, read by range requests, served with no access log.
- how: Range requests only: a whole-file GET is refused with 416. Six connections and 2 MB/s per client. /build says which Protomaps build is loaded; /healthz says it is up.
- how: Style: any Protomaps basemap style works (they are open); the app ships its own.
- trust: Protomaps builds from OpenStreetMap (ODbL). We see byte ranges in flight and keep nothing. The file is re-downloadable, so it is not backed up.
- probe: `https://tiles.mineracks.com/healthz`
- page: https://bitcoin.mineracks.com/tiles/

## Build — Test against real infrastructure on chains with no value.


### VSS · versioned storage (mainnet, Storage and oracles)
- connect: `https://vss.mineracks.com/vss`
- what: An encrypted, versioned store for the small state a wallet must get back with its keys. Lightning channel state, and now labels, notes and files.
- how: Upstream lightningdevkit/vss-server, unmodified, over PostgreSQL. Clients encrypt before upload, so we hold ciphertext.
- how: Signature auth, as ldk-node sends it by default: a secp256k1 keypair is the account. 4 MiB per request, 25 requests a second per address.
- how: Durability: continuous encrypted write-ahead archiving to an on-site backup host, an encrypted off-site copy at a second provider, and nightly machine snapshots. The restore is drilled, not assumed — on 21 September 2026 the latest backup and a point-in-time restore were each rebuilt on an isolated machine and matched this database exactly, and the off-site copy passes a full checksum verification.
- trust: Registration is open by design: any keypair is a tenant, which is what makes it usable without an account, and also means the rate limit and the body cap are the only brakes. Store what you can afford to have rate-limited.
- trust: We cannot read an object, and nothing in a store ties it to a wallet, an address or a transaction. What we can see is that a store exists, how large its objects are and when they were written.
- probe: `https://vss.mineracks.com/healthz`
- page: https://bitcoin.mineracks.com/vss/

- page: https://oracle.mineracks.com

- page: https://spark.mineracks.com

- page: https://testnet4-faucet.mineracks.com

### Inquisition signet (signet, Test networks)
- connect: `https://inqsignet.mineracks.com/v1/tx`
- what: A Bitcoin Inquisition node that validates and relays covenant proposals on the default signet.
- how: POST the raw hex of a CTV / APO / OP_CAT / CSFS spend to /v1/tx: it runs testmempoolaccept on the Inquisition node first and relays it only if that passes, so a refused transaction comes back with the node's reason (HTTP 422), not silence.
- how: GET /v1/info lists the active deployments; POST /v1/rpc takes a small fixed set of read-only methods (see /info).
- trust: Vanilla signet nodes (ours at signet.mineracks.com included) see these transactions as non-standard or invalid; only Inquisition peers relay them. Confirmation depends on the signet miners running Inquisition, which they do.
- note: 5 requests per second per IP, 256 KB body cap, no account. Signet coin from a public signet faucet.
- probe: `https://inqsignet.mineracks.com/v1/tip`
- page: https://bitcoin.mineracks.com/inqsignet/

### regtest-in-a-box (regtest, Test networks)
- connect: `https://bitcoin.mineracks.com/downloads/regtest-in-a-box.tar.gz`
- what: Our drill environment as a download — bitcoind, Esplora, Electrum and a mempool explorer in one compose file.
- how: Unpack, `docker compose up -d`, `./mine.sh 101`. Explorer on localhost:8080, Esplora API on :3000, Electrum on :50001, RPC on :18443 (user and password `regtest`).
- how: `./fund.sh <bcrt1…> 0.5` pays from the miner wallet and mines a confirming block; `./mine.sh` mines on demand.
- note: Regtest is private by nature, so this is the one entry here that is not a hosted endpoint. Everything binds to localhost; the credentials are deliberately trivial. Nothing here phones home.
- page: https://bitcoin.mineracks.com/regtest-in-a-box/

- page: https://ark.mineracks.com

- page: https://ark.mineracks.com

- page: https://walletplayground.com

- page: https://anytwokeys.com

- page: https://multisighsm.com

## Run — Peer with our nodes, mine to our pool, take payments on our stack.


### Bitcoin Core P2P (mainnet, Nodes and peers)
- connect: `addnode=112.213.33.201:8333`
- what: Unpruned, txindex, accepting inbound peers.
- how: Bitcoin Core on our mempool VM, advertised on the public IP. Add it as a peer or just let the network find it.
- probe: `tcp://112.213.33.201:8333`
- page: https://bitcoin.mineracks.com/bitcoin-p2p/

### Elements P2P (liquid, Nodes and peers)
- connect: `addnode=elementscore.mineracks.com:18332`
- what: elementsd accepting inbound peers.
- how: Our Liquid node, advertised on the public IP.
- probe: `tcp://elementscore.mineracks.com:18332`
- page: https://bitcoin.mineracks.com/elements-p2p/

- page: https://ln.mineracks.com

- page: https://node.mineracks.com

### Watchtower (mainnet, Nodes and peers)
- connect: `0281f4affcd16ad56a6a5be055d19e24a17f9932d057f61c5403fc0809ebc696aa@tower.mineracks.com:9911`
- aliases: `0281f4affcd16ad56a6a5be055d19e24a17f9932d057f61c5403fc0809ebc696aa@troevjbliziveefvjyw3rmvynii33r5zrlax6vxs5xp3scv2gwhopdqd.onion:9911`
- what: Altruistic lnd watchtower, clearnet and Tor.
- how: A second lnd in watchtower-only mode with no funds. It watches for old channel states and broadcasts the justice transaction you handed it in advance; sweeps pay to your address.
- trust: Altruistic: no fee. We see your encrypted state blobs and nothing else until a breach.
- probe: `tcp://tower.mineracks.com:9911`
- page: https://bitcoin.mineracks.com/watchtower/

- page: https://public-pool.mineracks.com

- page: https://ausolo.ckpool.org

- page: https://btcpay.mineracks.com

- page: https://lnbits.mineracks.com

### Lightning address (mainnet, Payments)
- connect: `pay@mineracks.com`
- what: LNURL-pay with LUD-21 verify. Names on request.
- how: Any Lightning wallet can pay pay@mineracks.com. We can host addresses on your domain: CNAME it at our well-known service.
- probe: `https://mineracks.com/.well-known/lnurlp/pay`
- page: https://bitcoin.mineracks.com/lightning-address/

### BIP-353 pay codes (mainnet, Payments)
- connect: `piers.user._bitcoin-payment.pay.mineracks.com`
- what: DNSSEC-signed payment instructions carrying sp= and lno=.
- how: Resolve the TXT record over DoH with the AD bit set; wallets that speak BIP-353 do this for you.
- page: https://bitcoin.mineracks.com/bip353/

- page: https://mint.mineracks.com