Skip to content
This repository has been archived by the owner on Aug 23, 2020. It is now read-only.

v1.8.0-RELEASE
Compare
Choose a tag to compare
@GalRogozinski GalRogozinski released this 10 Jul 13:20
v1.8.0-RELEASE
6e0f635

Upgrade instructions

Please leave some time for your neighbors to upgrade as well. Connection will only be established with neighbors who have upgraded to >= 1.8.0. If you are not receiving traffic from your neighbors within a day, restart your node. Your neighbors may have upgraded after a longer period of time and restarting your node should allow the node to re-establish the connection.

Changes

  • Support for UDP connections has been removed. Please re-add your neighbors through the TCP protocol instead.

Configuration changes

The following configuration parameters have been removed:

  • UDP_RECEIVER_PORT
  • TCP_RECEIVER_PORT
  • MAX_PEERS
  • DNS_REFRESHER_ENABLED
  • DNS_RESOLUTION_ENABLED

The following configuration parameters have been added:

  • NEIGHBORING_SOCKET_ADDRESS - defines the socket address to bind the TCP socket to.
  • NEIGHBORING_SOCKET_PORT - defines the port of the TCP socket to use.
  • RECONNECT_ATTEMPT_INTERVAL_SECONDS - defines the interval at which to try to reconnect/disconnect wanted neighbors.
  • AUTO_TETHERING_ENABLED - controls auto-tethering, this was previously controlled via TESTNET true, default is false (also in testnet mode).
  • MAX_NEIGHBORS - rename of MAX_PEERS, defines the max number of connected neighbor. Default 5.

Other changes

  • It is now possible to connect to multiple neighbors originating from the same IP address, as the identity of a node is its IP address + server socket port
  • BCTCurl is used within the transaction processing pipeline which batches up to 64 transactions to hash them at the same time.
  • Neighbors are now only added after their domain name could be resolved. Reconnects are done in the RECONNECT_ATTEMPT_INTERVAL_SECONDS defined interval. Neighbors to which the connection was closed, are put into "reconnect pool" until they are explicitly removed by removeNeighbors.
  • Gossiping transaction messages are now dynamic and take 341–1650 bytes of data.
  • The requested transaction hash of a transaction gossip packet is now fixed to 49 bytes, no matter in what mode the node runs in.
  • The getNeighbors API call now also returns the domain with which the neighbor was added and whether the neighbor is actually connected.
  • A neighbor communicates his used coordinator address in the initial handshake packet, which if it doesn't match the node's own used coordinator address, will drop the connection. This prevents cross-pollination of nodes running in different networks. The Nodes will also communicate their used minimum weight magnitude, which in case they don't match, will also drop the connection.
  • Fix: set arrival time in millis (not seconds) (#766)
  • #1376
  • #1377
  • #1380
  • #1381
  • #1383
  • #1379
  • #1388
Assets 5
Loading