About this release

This is a maintenance release. It:

• Fine tunes the severity of the log message in case of invalid request on the user HTTP API - from warning to info.

• Details the Sophia compiler error reason, returned in the HTTP response body of path /debug/contracts/code/compile. This is a backward compatible enhancement of the user HTTP API.

• Fine tunes the validation of user API requests. The request body must be smaller than approx. 5 MB (was 8 MB) and must be received within 10 s (was 15 s).

• Fine tunes the severity of the log message in case of unexpected validation result of user HTTP API request - from error to warning.

• Adds network_id to /status endpoint. This is a backward compatible enhancement of the user HTTP API.

• Disables mining autostart by default, and makes beneficiary optional when mining is not enabled.

• Re-designs how the node interacts with the miner. Passing the nonce as a separate option.

• Introduces the repeats option to mining to allow the miner to make several attempts in one context.

• Adds support for multiple mining workers inside the node. Also adds the configuration instances: N to allow for multi (GPU) mining.

• Ships Linux CUDA GPU miners (cuda29, lcuda29) in the Ubuntu release package.

This release is backward compatible with v1.0.*.

Please join the Roma network by following the instructions below, and let us know if you have any problems by opening a ticket. Troubleshooting of common issues is documented in the wiki.

The instructions below describe:

• How to retrieve the released software for running a node;

• How to install a node;

• How to join the roma network.

• How to join the testnet.

Retrieve the software for running a node

You can run a node by either:

• Installing the published release binary corresponding to your platform; or
• Running the published Docker image aeternity/epoch; or
• Building a release binary from source.

The user configuration is documented in the wiki. For specifying configuration using the Docker image, please refer to its documentation.

The node user API is documented:

• HTTP API endpoints are specified online in swagger.yaml;

  • A JSON version of the same specification is located in the node at path lib/aehttp-0.1.0/priv/swagger.json.

  • The JSON version can be obtained from a running node using the endpoint /api.

  • An interactive visualization of the same specification is available online.
• WebSocket API endpoints are specified online;
• The intended usage of the user API (HTTP and WebSocket) is documented online.

Install node

The instructions for installing a node using a release binary are in the dedicated separate document.

For installation of a node using the Docker image, please refer to its documentation online.

Join Roma network

Roma network seed nodes

The release package comes preconfigured with seed nodes. Here is example subset of the seed nodes:

• aenode://pp_5mmzrsoPh9owYMfKhZSkUihufDTB6TuayD173Ng464ukVm9xU@35.178.61.73:3015

• aenode://pp_2KWhoNRdythXAmgCbM6QxFo95WM4XXGq2pjcbKitXFpUHnPQc3@35.177.192.219:3015

• aenode://pp_2L8A5vSjnkLtfFNpJNgP9HbmGLD7ZAGFxoof47N8L4yyLAyyMi@18.136.37.63:3015

• aenode://pp_2gPZjuPnJnTVEbrB9Qgv7f4MdhM4Jh6PD22mB2iBA1g7FRvHTk@52.220.198.72:3015

• aenode://pp_frAKABjDnM3QZCUygbkaFvbd8yhv6xdufazDFLgJRc4fnGy3s@52.56.252.75:3015

• aenode://[email protected]:3015

• aenode://pp_2mwr9ikcyUDUWTeTQqdu8WJeQs845nYPPqjafjcGcRWUx4p85P@3.17.30.101:3015

• aenode://pp_FLpSUrKwgBAu5uVRnB2iWKtwGAHZckxvtCbjVPeeCA3j33t3J@52.56.66.124:3015

• aenode://pp_2CAJwwmM2ZVBHYFB6na1M17roQNuRi98k6WPFcoBMfUXvsezVU@13.58.177.66:3015

Inspect Roma network

Here are example nodes that can be used to inspect current top block and see information about e.g. height or target:

• http://35.178.61.73:3013/v2/blocks/top

• http://35.177.192.219:3013/v2/blocks/top

• http://18.136.37.63:3013/v2/blocks/top

• http://52.220.198.72:3013/v2/blocks/top

Join the testnet

This section describes how to run a node as part of the testnet - the public test network of nodes - by using the release binary.

For running a node as part of the testnet by using the Docker image, please consult its documentation in addition to this section.

Testnet seed nodes

In order to join testnet reconfigure seed nodes in the release package:

• aenode://pp_QU9CvhAQH56a2kA15tCnWPRJ2srMJW8ZmfbbFTAy7eG4o16Bf@52.10.46.160:3015

• aenode://pp_27xmgQ4N1E3QwHyoutLtZsHW5DSW4zneQJ3CxT5JbUejxtFuAu@13.250.162.250:3015

• aenode://pp_nt5N7fwae3DW8Mqk4kxkGAnbykRDpEZq9dzzianiMMPo4fJV7@18.130.148.7:3015

Inspect the testnet

The core nodes of the public test network are accessible from the Internet.

Information, e.g. height, of the top block of the longest chain as seen by these core nodes of the testnet can be obtained by opening in the browser any of the following URLs:

• http://52.10.46.160:3013/v2/blocks/top

• http://13.250.162.250:3013/v2/blocks/top

• http://18.130.148.7:3013/v2/blocks/top

Setup your node

Setting up your node consists of:

• Configuring your node - see instructions in the dedicated separate document;
• Starting your node and verifying it works as expected - see instructions in the dedicated separate document.