Skip to content

Latest commit

 

History

History
42 lines (31 loc) · 1.63 KB

launch-validator.md

File metadata and controls

42 lines (31 loc) · 1.63 KB
Raw

Run Opera validator

1. Setup an AWS node

  • Ubuntu Server 20.04 LTS 64-bit
  • We would recommend the following (or better):
m5.xlarge (4 CPUs and 16GB), 500GB SSD
  • Open up port 22 for SSH, and port 5050 for both TCP and UDP traffic

2. Launch a read-only Opera node

  • Follow instructions in launching go-opera readonly node with limitations:
    • Use only --syncmode full option.
    • Use only --db.preset ldb-1 or --db.preset legacy-ldb options.

Wait for your node to sync up. You may add --exitwhensynced.age 10s flag to automatically stop the node when synced.

3. Run Opera validator

  • Stop read-only node
killall opera

  • Wait until the read-only node has stopped

  • Then run your validator node:

nohup opera --syncmode full --cache $CACHE --validator.id ID --validator.pubkey 0xPubkey --validator.password /path/to/password &
  • ID is your validator ID (e.g. 25)
  • 0xPubkey is your validator public key. You've generated your key with opera validator new.
  • /path/to/password is a path to a file which contains the password to decrypt the validator key (optional). If you omitted the --validator.password flag, then you will be prompted for the password in terminal.
  • $CACHE is amount of memory allocated for go-opera. Substitute half of server RAM capacity in MB.
  • Use only --syncmode full option.

Warning: it's highly recommended to not store password in a file. Instead, avoid using --validator.password and type password manually after each restart or remove it with shred -vu after every restart.

It's complete. Your node is running!