Comment on page
Testnet
AWS:
m5a.large
or any equivalent instance type
Bare Metal:
- 16GB RAM
- 4 vCPUs
- At least 200 GB of storage - make sure it's extendable
For running a Testnet node, the steps are almost the same as above. The only difference is that we should download a different genesis file this time
wget https://download.fantom.network/testnet-6226-no-mpt.g
We recommend using the following startup command:
opera --genesis /path/to/genesis/testnet-6226-no-mpt.g --syncmode snap --datadir /path/to/datadir --http --http.addr 0.0.0.0 --http.vhosts=* --http.corsdomain=* --ws --ws.addr 0.0.0.0 --ws.origins=* --datadir.minfreedisk=8096 --http.api="ftm,eth,abft,dag,rpc,web3,net,debug" --ws.api="ftm,eth,abft,dag,rpc,web3,net,debug"
Same sync checks can be applied here aswell. If the result of the
eth_syncing
call is false
, it means your node is fully synced.The result of the
eth_blockNumber
call should be a hex number (i.e 0x10c5815
). If you convert it to a decimal number, you can compare it to the latest block listed on the Fantom Testnet explorer: https://testnet.ftmscan.com/The Fantom node exports both RPC on port
18545
and WS on port 18546
.In order to test the WS endpoint, we will need to install a package called
node-ws
.An example WS call would look like this:
wscat --connect ws://localhost:18546
> {"id":1, "jsonrpc":"2.0", "method": "eth_blockNumber","params": []}
In order to maintain a healthy node that passes the Integrity Protocol's checks, you should have a monitoring system in place. Blockchain nodes usually offer metrics regarding the node's behaviour and health - a popular way to offer these metrics is Prometheus-like metrics. The most popular monitoring stack, which is also open source, consists of:
- Prometheus - scrapes and stores metrics as time series data (blockchain nodes cand send the metrics to it);
- Grafana - allows querying, visualization and alerting based on metrics (can use Prometheus as a data source);