Sealminer A4 Ultra Hydro
Bitcoin & Bitcoin Cash ASIC Miner
886TH
HASHRATE
9.45W/TH
EFFICIENCY
8373W
POWER
£903.43
EST. MONTHLY
NO PAYBACK
EST. ROI
This guide explains Bitcoin Core I2P support in plain English. It focuses on what the subject is, why it matters and what a beginner should remember.
TL;DR
- What it is: Bitcoin Core 22.0 added native support for connecting to I2P services and, when configured, accepting inbound I2P connections. Core communicates with an I2P router through its SAM interface and uses transient or persistent destinations according to configuration.
- Why it matters: Core 22 made I2P a first-class Bitcoin transport, but operators still need to secure the SAM boundary, decide identity lifetime and verify that routing and fallback behaviour match the intended privacy model.
- Current position: Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Bitcoin Core I2P support in simple English
Bitcoin Core I2P support: Native I2P support arrived in Core 22.0. It still requires a separately installed and running I2P router exposing a compatible SAM endpoint.
Simple example
A node operator is checking Bitcoin Core I2P support. For inbound reachability, preserve the private key only when stable identity is intentional. Test router unavailable, SAM authentication, session restart, inbound and outbound paths, onlynet policy, mixed Tor and clearnet configuration, key loss, monitoring and rollback.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Version and dependency
Native I2P support arrived in Core 22.0. It still requires a separately installed and running I2P router exposing a compatible SAM endpoint.
SAM connection
Configure the I2P SAM proxy explicitly and restrict it to the local host or a protected network. Failure to reach SAM should not silently reroute intended I2P-only traffic over clearnet.
Outbound sessions
Core can use transient I2P destinations for outbound activity. A destination is a network identity, so assess whether rotation or persistence best fits the operator threat model.
Inbound service
For inbound reachability, preserve the private key only when stable identity is intentional. Protect file permissions and test publication and connectivity from an independent I2P client.
Address relay
BIP 155 carries I2P endpoints in addrv2. Receiving or relaying an address does not authenticate a peer, prove reachability or reveal whether the local node used that transport.
Privacy boundary
I2P hides IP-layer paths from peers but local logs, timing, wallet activity, mixed transports, DNS, monitoring and administrator access can still correlate the node.
Operations
Test router unavailable, SAM authentication, session restart, inbound and outbound paths, onlynet policy, mixed Tor and clearnet configuration, key loss, monitoring and rollback. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness. Record source commit, binary hash, network, chain identity, configuration and dependencies.
Frequently asked questions
What is the main point of Bitcoin Core I2P support?
Bitcoin Core I2P support: Native I2P support arrived in Core 22.0. It still requires a separately installed and running I2P router exposing a compatible SAM endpoint.
For Bitcoin Core I2P support, what should a beginner know about version and dependency?
Native I2P support arrived in Core 22.0. It still requires a separately installed and running I2P router exposing a compatible SAM endpoint.
For Bitcoin Core I2P support, what should a beginner know about sam connection?
Configure the I2P SAM proxy explicitly and restrict it to the local host or a protected network.
For Bitcoin Core I2P support, what should a beginner know about outbound sessions?
Core can use transient I2P destinations for outbound activity. A destination is a network identity, so assess whether rotation or persistence best fits the operator threat model.
Conclusion
Core 22 made I2P a first-class Bitcoin transport, but operators still need to secure the SAM boundary, decide identity lifetime and verify that routing and fallback behaviour match the intended privacy model.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.