arkpool.orgMining setup guide →

PRIVACY · SECURITY · BITCOIN MINING

Bitcoin mining privacy:
Tor, Stratum V2 and ArkPool.

Your miner needs work to hash and a way to submit shares. It does not need to advertise your home IP address to the pool. ArkPool combines a home gateway, Tor and authenticated Stratum V2 to protect the connection—while keeping the limits clear.

By ArkPool · Published November 16, 2026

Start with the path your work takes

Miner → home gateway → authenticated V2 over Tor → ArkPool.

The gateway runs on your home server or another compatible host. Your ASIC does the hashing; the gateway handles the remote connection. Miner-to-gateway compatibility is a separate question: a miner speaking V1 needs a gateway release that explicitly supports V1-to-V2 translation. Native V2 passthrough requires compatible miner firmware. Changing a port does not convert protocols.

ArkPool accepts native V2 connections today. The new gateway connects to ArkPool using V2 only. Pool-side V1 remains available for existing installations during migration. Check the exact gateway release and its LAN settings before switching; start with one miner and confirm accepted shares and credited work.

Tor reduces exposure of your home IP

The remote mining connection reaches ArkPool through an onion service. The pool does not receive your home public IP as the connection’s source address. The gateway must keep remote name resolution and traffic on Tor, with no direct clearnet fallback when Tor is unavailable.

That is useful privacy, not a guarantee of anonymity. Your network provider may observe Tor use and traffic timing or volume. A compromised gateway, miner or wallet can reveal information before encryption helps. Strong observers may also correlate traffic. Reusing an Ark address links mining activity to the same payout identity.

The public HTTPS website is a separate path. Cloudflare delivers and protects it and can process visitor IP addresses, request metadata and security events. Mining traffic is not routed through that website. Individual miner lookups use the separate Tor dashboard.

V2 adds authenticated, encrypted mining transport

On the gateway-to-pool connection, Stratum V2’s authenticated encryption protects mining protocol messages and verifies the server against its configured authority key. Keep authority verification enabled and obtain the public key from the documented pool connection settings. Do not accept an unexpected key change just to make a connection succeed.

Tor and V2 serve complementary purposes: Tor protects the network path and source-address exposure; V2 authenticates and encrypts the mining protocol connection. Neither protects a compromised endpoint. The new gateway must not silently downgrade to V1 after an authentication failure.

Transport security also does not make a pool trustless or guarantee fair accounting. Accepted submissions, independently verified work, credited earnings and a payment received in your wallet are separate milestones. V2 does not itself change ArkPool’s pay rates, Boost rules or payout schedule, and this rollout is not a claim of miner-selected block templates.

Read the V2 migration guide and public endpoint and authority-key settings.

Who developed Stratum V2?

Stratum V2 grew from work by Braiins founders Pavel Moravec and Jan Čapek, in collaboration with Bitcoin developer Matt Corallo and other contributors. The protocol is an open industry effort. The Stratum Reference Implementation (SRI) community develops open-source software for it; ArkPool builds on that work rather than claiming to have invented V2.

Read the protocol specification and author credits, Braiins’ protocol history, and the Stratum V2 project.

Who can see what?

The public pool website shows aggregate statistics, without a public miner directory. However, anyone who knows a miner’s Ark address can look up its read-only information through the Tor dashboard. Keep that address and identifying screenshots private if you want to limit linkage.

Resilience helps, but does not remove latency

The gateway’s documented dual-Tor design provides alternate ready paths for new connections. A failed active path still requires a reconnect. Both paths share your gateway and internet connection, so they cannot protect against every power, ISP or pool outage. Verify these capabilities in the release you install.

Your ASIC hashes locally. Tor carries jobs and submitted shares, not every hash calculation. Variable delay can postpone new work or increase stale shares. Redundancy does not remove that delay, and we do not promise a fixed performance penalty or earnings improvement.

Keep the setup private in practice

Ready to connect? Follow the mining setup guide. Agents can use ArkPool’s setup instructions. Report suspected vulnerabilities through our private security reporting process.