Skip to content

Adding a full node to the Bakerloo testnet

The Bakerloo testnet is public, and anyone can submit transactions, and add nodes.


In production systems, adding full nodes — and thereby obtaining a complete copy of the system state, the blockchain data — will be allowed by the protocol to stakeholders of the DCN

Stakeholders will be able to manage their own list of nodes on such systems

Operating AGC in light client mode will not require any process for adding a node to the system; rather, it will be based entirely on bilateral agreements between any full node operator, and the light client user. Similarly, full node operators are free to make their node RPC endpoints available to anyone

Light client support is roadmapped for AGC, and will be described in the Bakerloo testnet context as soon as it is available

The steps below describe how to add a node to the testnet. In the future, adding full nodes will become a decentralised operation. Currently, however, nodes must be added by Clearmatics.

Find your node's eNode string

Follow the instructions in the final section of installing your node to attach to it with the Autonity Node.JS Console.

Then, to get the eNode string, run the following in the Node.JS Console:

const nodeinfo = await web3.admin.nodeInfo()
The output eNode string will resemble the following:



This will work on any node added to the testnet according to the instructions provided here. However, the node endpoints publicly provided by Clearmatics (rpc3 and rpc4) do not offer the web3.admin namespace

Create a participant account address

To send transactions on the Bakerloo testnet, you must own AUT, Autonity's native protocol coin (intrinsic account balance) that is used to pay gas for transactions.

This requires an account, such as those you would use in a wallet application, to have those funds transferred to. This works just like elsewhere in Ethereum-type systems.

The user guide section explains how to create a Participant account address that you will be using to sign transactions and interact with the Bakerloo testnet.


Autonity DCNs are built on the principle that node addresses are used by nodes for their participation in the distributed virtual machine and consensus computation, and Participant account addresses are used before submitting fully-formed transactions to a node, to sign them. Therefore nodes do not store or contain the cryptographic keys that participants would use to sign transactions or transfer value

Add your full node to the Bakerloo testnet

In the future, adding full nodes will become a decentralised operation. Currently, however, nodes must be added by Clearmatics. To request the addition of a node, submit its eNode string using this form:

If there are any problems connecting your node, we will contact you. If you need help, please ask.


Our team currently operates only during normal London (UK) business hours. We will reply to requests as quickly as possible, but please be aware that during busy times it can take up to two hours for your node to be added

Sync the blockchain

If you have provided your email address, you will receive confirmation once your node has been added.

As soon as that is done, your node will begin to download and verify the blockchain data. You can check this by using the Node.JS Console to attach to your node and query await web3.eth.getBlockNumber(), or on your node host, by Docker attaching to the AGC's standard output.


Depending on your node's connection speed and the height of the blockchain, this process can take several hours


If you need help, you can: