Skip to content
You are reading Palm development version documentation and some displayed features may not be available in the stable release. You can switch to stable version using the version box at screen bottom.

Updated on July 8, 2021

Run a transaction node

Transaction nodes are used to read transaction history or send transactions on the Palm network without performing validator duties.


In IBFT 2.0 networks, validators validate transactions and blocks. Validators take turns to create the next block. Before inserting the block onto the chain, a super-majority (greater than 66%) of validators must first sign the block.

To ensure that your node can successfully join the Palm network, you must specify the correct bootnodes for the environment you are targeting. This allows your node to find existing nodes on the network. Connecting to existing nodes is important as it allows your node to download the chain history and send transactions to validator nodes.

The instructions in this section allow you to run a Palm transaction node locally for the target network environment. Available network environments are:

Network Description
Palm Mainnet Palm’s production environment. Contracts and accounts hold real value. You can use the Palm Mainnet bridge to transfer assets between Palm Mainnet and Ethereum Mainnet.
Palm Testnet A persistent environment that will not be reset. This is useful as a staging environment and for long-term testing. You can use the Palm Testnet bridge to transfer assets between Palm Testnet and the Ethereum Rinkeby testnet.


1. Create the node directory

Create the directory in which to store the required files and data directory:

mkdir palm-node

Change into the palm-node directory:

cd palm-node


If deploying your node on a cloud service like AWS, we recommend you use a second large data volume for the data directory. In the event of host failure, the data volume can be quickly moved to another host to re-establish connectivity with minimal downtime.

2. Download the genesis file

The genesis file specifies the network-wide settings and defines the first block in the chain. Each Palm environment uses a different genesis file.

The following curl commands download the genesis file for the required environment.

curl -O
curl -O

3. Create the Besu configuration file

The configuration file is a TOML file used to specify the Besu options. Alternatively, specify the options directly when starting Besu.

The following configuration file examples include the bootnode addresses for the required environments. Create a TOML file named config.toml with the following options:


For the data-pathoption, replace <PATH> with the location of the node directory created in step 1.

# Palm Mainnet genesis file

# Network bootnodes

# Data directory

#Enable the JSON-RPCs
# Palm Testnet genesis file

# Network bootnodes

# Data directory

#Enable the JSON-RPCs


If running multiple Besu clients, ensure you configure the rpc-http-port option to avoid port conflicts.

4. Start Besu

Start Besu and specify the configuration file:

besu --config-file=/home/myuser/palm_node/config.toml

The node attempts to connect to the bootnodes and other transaction nodes, and begins synchronization once enough peers are found.

5. Confirm the network is running

Once the network is synchronized, start another terminal and use curl to call the JSON-RPC API net_peerCount method to check for connected peers:

curl -X POST --data '{"jsonrpc":"2.0","method":"net_peerCount","params":[], "id":1}' localhost:8545

The result displays the validators on the Palm network:

  "jsonrpc" : "2.0",
  "id" : 1,
  "result" : [ "0x5" ]
Questions or feedback? You can discuss and obtain community support on Palm Discord.
For additional support, contact Palm on Palm website.