Enhancing Node Communication, Developing Monitoring Tools and Deprecating the “Epoch” Name

Release 1.3.0 is coming later this week. Here is a sneak-peak of its main features.

After completing release 1.2.0 on the 10th of January, we immediately began working on our next sprint. This sprint will be finished by the end of this week and is scheduled to produce a 1.3.0 release. The focus of release 1.3.0 will be limited to adding support for NAT-PMP/UPNP, introducing the monitoring of transactions on the Roma network and renaming epoch node to “aeternity:

  • NAT-PMP/UPNP: in order to have nodes connected in a dense network, nodes must be able to communicate with each other. At the minimum, users that use the default configuration must open the default port 3015 in their network. When setting up an aeternity node, some users may have difficulties opening those ports. We plan to introduce support for NAT-PNP and UPNP protocols in order to have port-forwarding working “out of the box” if a router supports one of those protocols. This should make the process of deploying a node with open ports much easier and, therefore, significantly improve the stability and responsiveness of the overall network.
  • Transactions monitoring: to be able to monitor the flow of transactions on the Roma network in real-time, we will introduce infrastructure for transaction monitoring that will post a new transaction every minute onto the network and check if the transaction is included in one of the following blocks.
  • To make the naming of aeternity components more consistent, we will start deprecating the epoch name and start referring to our node as aeternity node. In this respect, the following actions are planned:
  1. aeternity/epoch repository will be renamed to aeternity/aeternity: since GitHub will keep forwarding all HTTP requests and git commands referencing epoch to aeternity, impact of this change will be minimal
  2. all references to epoch in code will be replaced by aeternity or node
  3. binary bin/epoch will be renamed to bin/aeternity, however, for backward compatibility a symlink bin/epoch pointing at bin/aeternity will be created
  4. backward compatibility will be kept until the next scheduled hard fork (The 2.x.x. release called Minerva) of the æternity network
  5. names of binary packages will be updated to aeternity-X.X.X-…
  6. changes to the documentation, user configuration schema epoch_config_schema.json will take place in release 1.4.0.
  7. names of log files containing epoch will be renamed:
epoch.log -> aeternity.log
epoch_sync.log -> aeternity_sync.log
epoch_mining.log -> aeternity_mining.log
epoch_pow_cuckoo.log -> aeternity_pow_cuckoo.log
epoch_metrics.log -> aeternity_metrics.log

In addition, a lot of progress has been made on improving usability of state channels and building æternity’s implementation of Stratum/pool. However, this is still work in progress and will not be included in release 1.3.0.

If you have any questions, please let us know by using GitHub or starting a topic in the Forum.

Interested in æternity? Get in touch:

GitHub | Forum | Reddit | Twitter | YouTube| LinkedIn

Leave a Reply

Your email address will not be published. Required fields are marked *