tag:github.com,2008:https://github.com/vipnode/vipnode/releases 2020-06-11T17:31:01Z tag:github.com,2008:Repository/137096355/v2.4 2020-06-11T17:34:07Z <p>v2.4</p> <p>No new features. Dependencies updated, primarily to fix Badger disk <br />usage and crash.</p> <p>Moved the vipnode Go module to the appropriate <br />`github.com/vipnode/vipnode/v2` namespace.</p> shazow tag:github.com,2008:Repository/137096355/v2.4-alpha.2 2019-12-06T20:37:41Z shazow tag:github.com,2008:Repository/137096355/v2.4-alpha.1 2019-12-06T19:30:37Z shazow tag:github.com,2008:Repository/137096355/v2.3.3 2019-12-06T19:51:07Z <p>v2.3.3</p> <p>Bug fix release for agents running with Parity v2.5 or newer.</p> <p>- `agent`: Fix incorrect compatibility check for Parity.</p> <p>Built using Go v1.13.4. Full list of changes here: <a class="commit-link" href="https://github.com/vipnode/vipnode/compare/v2.3.2...v2.3.3"><tt>v2.3.2...v2.3.3</tt></a></p> shazow tag:github.com,2008:Repository/137096355/v2.3.2 2019-12-05T19:59:57Z <p>v2.3.3</p> <p>Bug fix release for agents running with Parity v2.5 or newer.</p> <p>- `agent`: Fix "Missing RPC method" with Parity nodes, see <a class="issue-link js-issue-link" href="https://github.com/vipnode/vipnode/issues/88">#88</a>.</p> shazow tag:github.com,2008:Repository/137096355/v2.3.1 2019-11-15T17:43:41Z <p>v2.3.1</p> <p>Bug fix release for agents.</p> <p>- `vipnode agent --strict-peers` no longer uses the port for strict equality comparison of hosts. See <a class="issue-link js-issue-link" href="https://github.com/vipnode/vipnode/pull/84">#84</a> for details. <br />- Added more verbose logging details when peers are disconnected due to strict peer inequality.</p> shazow tag:github.com,2008:Repository/137096355/v2.3 2019-10-07T03:01:04Z <p>v2.3</p> <p>Minor feature release that prepares for some compatibility breaking.</p> <p>- Added `vipnode agent --strict-peers` which will disconnect any peers <br /> that were not provided by the pool, or if there is a routing mismatch. <br /> Useful for completely overriding the discovery mechanism of nodes. <br /> Recommended to also run geth with `--nodiscover` and `--netrestrict` <br />- Changed pool API: `UpdateResponse.ActivePeers` now returns <br /> "enode://..." strings instead of just NodeIDs. This is <br /> backwards-compatible to how agents were implemented in the past, which <br /> ignored the actual value but used the count. <br />- Updated agent implementations to parse `UpdateResponse` values <br /> defensively, works with NodeIDs or "enode://..." strings.</p> shazow tag:github.com,2008:Repository/137096355/v2.3-alpha.2 2019-10-04T01:19:17Z shazow tag:github.com,2008:Repository/137096355/v2.3-alpha 2019-10-01T01:36:37Z <p>Merge pull request <a class="issue-link js-issue-link" href="https://github.com/vipnode/vipnode/pull/73">#73</a> from vipnode/strict-peers</p> <p>agent: Add StrictPeers mode</p> shazow tag:github.com,2008:Repository/137096355/v2.2.2 2019-09-30T00:57:28Z <p>Bug fix release:</p> <p>- pool: Fix peers being incorrectly marked as inactive, causing agents <br /> to disconnect all pool peers periodically, reconnect, and enter a <br /> thrashing loop.</p> <p>Full list of changes here: <a class="commit-link" href="https://github.com/vipnode/vipnode/compare/v2.2...v2.2.2"><tt>v2.2...v2.2.2</tt></a></p> shazow