About this release

This is a maintenance release. It:

  • Improves scheduling of Ping:s - make sure we keep/restart pinging after synchronization is done.

  • Adds support for responding of ping messages in State Channels' WebSocket protocol. Because of browser compatibility issues, the keep alive functionality is being built on data frames instead of using the control frames.

  • Enhances the HTTP endpoint for channel creation transaction to accept an optional list of delegates.

  • Introduces State Channel fsm-assisted solo-close and slash, and continuous chain monitoring.

    • The state channel chain watcher now watches the chain continuously.

    • The state channel FSM stays open during the closing phase.

    • Client WS API for solo-closing, slash and settle.

    • SC FSM automatically detects when a slash is needed.

    • SC FSM reports to client any time the on-chain channel state changes.

    • The SC watcher is now fork-aware.

This release is backward compatible with the previous v3.0.1 release.

Please join the mainnet 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:

Retrieve the software for running a node

You can run a node by either:

The instructions for configuring the node using the Docker image are in the dedicated separate document.

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-*/priv/swagger.json (you will need to amend the wildcard * placeholder in the path with the version).

    • 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 the mainnet

Mainnet seed nodes

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

  • aenode://pp_2L8A5vSjnkLtfFNpJNgP9HbmGLD7ZAGFxoof47N8L4yyLAyyMi@18.136.37.63:3015

  • aenode://pp_2gPZjuPnJnTVEbrB9Qgv7f4MdhM4Jh6PD22mB2iBA1g7FRvHTk@52.220.198.72:3015

  • aenode://[email protected]:3015

  • aenode://pp_2mwr9ikcyUDUWTeTQqdu8WJeQs845nYPPqjafjcGcRWUx4p85P@3.17.30.101:3015

  • aenode://pp_2CAJwwmM2ZVBHYFB6na1M17roQNuRi98k6WPFcoBMfUXvsezVU@13.58.177.66:3015

  • aenode://pp_7N7dkCbg39MYzQv3vCrmjVNfy6QkoVmJe3VtiZ3HRncvTWAAX@13.53.114.199:3015

  • aenode://pp_22FndjTkMMXZ5gunCTUyeMPbgoL53smqpM4m1Jz5fVuJmPXm24@13.53.149.181:3015

  • aenode://pp_Xgsqi4hYAjXn9BmrU4DXWT7jURy2GoBPmrHfiCoDVd3UPQYcU@13.53.164.121:3015

  • aenode://[email protected]:3015

Inspect the mainnet

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

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

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

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

  • http://13.53.149.181: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_DMLqy7Zuhoxe2FzpydyQTgwCJ52wouzxtHWsPGo51XDcxc5c8@13.53.161.215: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://13.53.161.215:3013/v2/blocks/top

Setup your node

Setting up your node consists of:

Last updated