v2.4

No new features. Dependencies updated, primarily to fix Badger disk usage and crash.

Moved the vipnode Go module to the appropriate github.com/vipnode/vipnode/v2 namespace.

v2.3.3

Bug fix release for agents running with Parity v2.5 or newer.

• agent: Fix incorrect compatibility check for Parity.

Built using Go v1.13.4. Full list of changes here: v2.3.2...v2.3.3

v2.4-alpha.2

Experimental pre-release that adds a feature to the vipnode pool to be used in case the Istanbul fork has issues with buggy clients:

• pool: Add --invalid-node=REGEXP flag

Example usage:

vipnode pool --invalid-node="^Parity-Ethereum/v2.5.10"

Connecting agents will be instructed to disconnect from any peers that match the regular expression, check happens once per update cycle (60 seconds).

No binaries will be built for this release, but a Docker image is provisioned. https://hub.docker.com/repository/docker/shazow/vipnode/tags

v2.3.2

Bug fix release for agents running with Parity v2.5 or newer.

• agent: Fix "Missing RPC method" with Parity nodes, see #88.

Built using Go v1.13.4. Full list of changes here: v2.3.1...v2.3.2

v2.3.1

Bug fix release for agents.

• vipnode agent --strict-peers no longer uses the port for strict equality comparison of hosts. See #84 for details.
• Added more verbose logging details when peers are disconnected due to strict peer inequality.

Built using Go v1.13.3. Full list of changes here: v2.3...v2.3.1

v2.3

Minor feature release that prepares for some compatibility breaking.

• Added vipnode agent --strict-peers which will disconnect any peers that were not provided by the pool, or if there is a routing mismatch. Useful for completely overriding the discovery mechanism of nodes. Recommended to also run geth with --nodiscover and --netrestrict
• Changed pool API: UpdateResponse.ActivePeers now returns "enode://..." strings instead of just NodeIDs. This is backwards-compatible to how agents were implemented in the past, which ignored the actual value but used the count.
• Updated agent implementations to parse UpdateResponse values defensively, works with NodeIDs or "enode://..." strings.

Full list of changes here: v2.2.2...v2.3

v2.2.2

Bug fix release:

• pool: Fix peers being incorrectly marked as inactive, causing agents to disconnect all pool peers periodically, reconnect, and enter a thrashing loop.

Full list of changes here: v2.2...v2.2.2

v2.2.1

Bug fix release:

• ethnode: geth changed so enode IDs must be prefixed with enode://
• ethnode: geth changed the layout of PeerInfo, IDs are now ID hashes,
  old IDs are encoded under EnodeID.
• agent: Fixed agents aborting after the pool was unable to find more peers.

Full list of changes here: v2.2...v2.2.1

v2.2

This is a compatible release, it fixes a few bugs in v2.1 and adds a
few minor features:

• Added vipnode agent --enode.host flag to override the host component
  of the advertised enode URI, used for overriding network routing.
• Added vipnode --pprof flag to start a pprof server for debugging.
• Fixed vipnode agent not requesting peers on connect.
• Fixed vipnode pool not registering the new vipnode_peer RPC.
• Fixed vipnode pool returning peers that were already known to be
  connected.
• Fixed vipnode pool not saving some peer metrics (num_peers,
  block_number)

Lots of tests and cleanup, too.

Full list of changes here: v2.1...v2.2

Notes:

• Having trouble building a Windows binary right now. Will upload one once I get it working.
• Recent geth releases don't work with vipnode (admin_* compatibility breakage), next release will fix this. Update: See v2.1.1

v2.1

This is a forward-compatible release towards some big changes slated for
Vipnode 3.0 Infrastructure Edition.

Major changes:

• Replaced the "host"/"client" dichotomy with a single "agent" type. The vipnode agent runs along your node, regardless of which kind of node it is. Node protocol capability is used to determine matchmaking.
• Deprecated RPCs: vipnode_client, vipnode_host (will be removed in v3.0)
• New RPCs: vipnode_connect
• Pantheon node support (full nodes only, no light nodes)
• Agents send more metadata with updates now, including protocol capability and versions for everything.
• Added support for peering between full nodes, can used for peering internal infrastructure.

Command-line flag changes:

• Added pool --restrict-network for restricting the pool to a single network.
• Added pool --max-request-hosts for limiting the number of hosts a node is allowed to request.
• Merged host and client sub-commands into agent.
• Added agent --update-interval for controlling the update frequency.
• Added agent --min-peers for maintaining a minimum number of peers from the pool.
• Changed pool --contract.welcome to be default disabled.

Full list of changes here: v2.0.1...v2.1