Parallax v2.1.0 brings native Tor support and fixes the Go module path for library consumers.
Tor
The node can now run over Tor with Bitcoin Core's semantics: dial through a SOCKS5 proxy, maintain its own v3 onion service, gossip and store onion addresses (BIP155), and operate onion-only. The default configuration is zero-flag: install a Tor daemon and the node finds it over the control port, creates the onion service, and routes onion dials through it. For explicit control there are --proxy, --onion, --onlynet, --proxyrandomize, --listenonion, --torcontrol, and --torpassword, following Core's flag semantics.
Documentation:
- Running over Tor — operator setup and verification
- Tor Integration — protocol behavior
Go module path
The module moved to github.com/ParallaxProtocol/parallax/v2. Go requires the /vN suffix at major version 2, so the plain-path v2.0.0 tag was unresolvable with go get; from this release, go get github.com/ParallaxProtocol/parallax/v2@v2.1.0 works. Library consumers should update their imports and depend on v2.1.0 or later.
Fixes
validation: a cold snap sync could wedge one block short of the target; head markers ahead of an imported block are now kept.build: release Docker tags and archive inclusion were pinned to the v1 series; both now derive from the actual major version.cmd: leftover Geth branding in user-facing output replaced.- The documentation site is now versioned per minor series, so each release keeps the docs it shipped with.
Upgrading
No operator action required: without a Tor daemon nothing changes. Your onion identity lives at <datadir>/onion_v3_private_key; back it up if you want a stable onion address.
Full Changelog: v2.0.0...v2.1.0