This is a maintenance release. It contains stability improvements so all users are encouraged to upgrade.
This release:
- Adds operators
mod
,++
,bsl
,bsr
, and^
to the Sophia compiler. - Adds function
String.sha3
to the Sophia compiler. - Changes cuckoo miner config and processing to allow multiple simultaneous miners.
This impacts mining configuration:
- changes
mining
>cuckoo
>miner
param tomining
>cuckoo
>miners
and makesmining
>cuckoo
>miner
param deprecated - moves
mining
>cuckoo
>miner
>edge_bits
param tomining
>cuckoo
section
- changes
- Adds Events to the Sophia compiler
- Adds builtin functions
Int.to_str
andAddress.to_str
to the Sophia compiler - Adds native Windows build support.
- Follow the instructions from
/docs/build-windows.md
to build and run a node on Windows.
- Follow the instructions from
- Improves the handling of errors in contract create and contract call transactions.
- Enhances the Sophia compiler, that now correctly rejects some programs that resulted in incorrect bytecode before.
The Sophia compiler has been moved to a separate repository.
This release is backward compatible with v1.1.* and 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.
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-*/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.
- A JSON version of the same specification is located in the node at path
- WebSocket API endpoints are specified online;
- The intended usage of the user API (HTTP and WebSocket) is documented online.
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.
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
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
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.
In order to join testnet reconfigure seed nodes in the release package:
- aenode://pp_QU9CvhAQH56a2kA15tCnWPRJ2srMJW8ZmfbbFTAy7eG4o16Bf@52.10.46.160:3015
- aenode://pp_2vhFb3HtHd1S7ynbpbFnEdph1tnDXFSfu4NGtq46S2eM5HCdbC@18.195.109.60:3015
- aenode://pp_27xmgQ4N1E3QwHyoutLtZsHW5DSW4zneQJ3CxT5JbUejxtFuAu@13.250.162.250:3015
- aenode://pp_nt5N7fwae3DW8Mqk4kxkGAnbykRDpEZq9dzzianiMMPo4fJV7@18.130.148.7:3015
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://18.195.109.60:3013/v2/blocks/top
- http://13.250.162.250:3013/v2/blocks/top
- http://18.130.148.7:3013/v2/blocks/top
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.