Setup Full Node
Last updated
Was this helpful?
Last updated
Was this helpful?
This document details how to join the Secret Network testnet as a full node. Once your full node is running, you can turn it into a validator in the optional last step.
Secret Network has strict Hardware Requirements. If your machine does not meet them, it will *NOT* work as a node.
Ubuntu/Debian host (with ZFS or LVM to be able to add more storage easily)
A public IP address
Open ports TCP 26656 & 26657 Note: If you're behind a router or firewall then you'll need to port forward on the network device.
Reading
RPC address of an already active node. You can use http://bootstrap.pulsar3.scrtlabs.com:26657, or any other node that exposes RPC services. Alternate RPC nodes available in the
secretdThis guide assumes you've already installed the latest version of secretd and SGX. To setup an archive node, you must follow the instructions.
For more information on SGX, see instructions for and . See if you'd like a more comprehensive overview on what's happening in these steps.
Choose a moniker for yourself, and replace <MONIKER> with your moniker below. This moniker will serve as your public nickname in the network.
This will generate the following files in ~/.secretd/config/
genesis.json
node_key.json
priv_validator_key.json
genesis.jsonThe genesis file is how other nodes on the network know what network you should be on.
Initialize /opt/secret/.sgx_secrets:
You can choose between two methods, 3a (automatic) or 3b (manual):
WARNING: This method is experimental, and may not work. If it doesn't work, skip to step 3b.
The following commands will create the necessary environment variables and attempt to automatically register the node.
Attestation certificate should have been created by the previous step
Verify the certificate is valid. A 64 character registration key will be printed if it was successful.
secretdConfigure secretd. Initially you'll be using the bootstrap node, as you'll need to connect to a running node and your own node is not running yet.
If you already have a wallet funded with SCRT, you can import the wallet by doing the following:
Otherwise, you will need to set up a key. Make sure you back up the mnemonic and the keyring password.
Register your node on-chain
2. Pull & check your node's encrypted seed from the network
3. Get additional network parameters
These are necessary to configure the node before it starts.
In order to be able to handle NFT minting and other Secret Contract-heavy operations, it's recommended to update your SGX memory enclave cache:
minimum-gas-price ParameterWe recommend 0.0125uscrt per gas unit:
Your node will not accept transactions that specify --fees lower than the minimun-gas-price you set here.
secret-node:You are now a now ready to finally sync the full node. 🎉.
Go to Testnet State Sync to continue.
secretd tendermint show-node-id
And publish yourself as a node with this ID:
Be sure to point your CLI to your running node instead of the bootstrap node
secretcli config node tcp://localhost:26657
If someone wants to add you as a peer, have them add the above address to their persistent_peers in their ~/.secretd/config/config.toml.
And if someone wants to use your node from their secretcli then have them run:
If this step was successful, you can skip straight to .
The following steps should use secretd be ran on the full node itself. To run the steps with secretd on a local machine, there.
This will output your address, a 45 character-string starting with secret1.... Copy/paste it to get some test-SCRT from . Continue when you have confirmed your account has some test-SCRT in it.
Also checkout by [ block pane ] for fine tuning your machine for better uptime.
You can skip syncing from scratch or download a snapshot by to the current block.
To turn your full node into a validator, see .