Awesome Berachain validators

Collection of Berachain validators resources

Contents

Monitoring
Proof of Liquidity
Data
Snapshots
FAQ

Monitoring

• Berachain Validator Monitoring - Public Dashboard
• Tenderduty - Comprehensive monitoring tool for Tendermint chains. Its primary function is to alert a validator if they are missing blocks, and more.
• cosmos-validator-watcher - Real-time Cosmos-based chains monitoring. Berachain setup explained in Discord.
• Execution blocks monitoring - Public Dashboard
• Cosmostation: Cosmos Validator Monitoring Service (CVMS) - Public Dashboard
• Synergy Nodes: Performance Metrics - Public Dashboard
• Hyeongjun Yu: Grafana dashboard

PoL

• BGT Station - list of vaults, and validators - Can sort the lists to see which validators and vaults have the highest APY.
• Synergynode cutting board tool - Simple UI to manage your Berachef cutting board.
• Kodiak cutting board tool - Simple UI to manage your Berachef cutting board.

Data

• BGTscan - BGT rewards dashboard
• Nodes map - Berachain v2 nodes map
• B-Harvest dashboard - Validators data by B-Harvest
• Flipside: State of the Berachain Testnet - Overall metrics for total number of users, transactions, etc.

Snapshots

Provider	Database
A41	pebbledb
Allnodes	goleveldb
Berachain (Asia)	pebbledb
Berachain (Europe)	pebbledb
Berachain (North America)	pebbledb
Blacknodes	pebbledb
Blockhunters	goleveldb
Brightlystake	pebbledb
Contribution DAO	pebbledb
Imperator	goleveldb
L0vd services	pebbledb
Staketab	pebbledb
Synergy Nodes	pebbledb
TTT VN	pebbledb

FAQ

• What are some useful commands for troubleshooting?
  • See here for a list of useful commands.
• How do I address missed blocks on my validator?
  • Check disk I/O metrics, make sure your node can keep up.
  • NVMe storage is highly recomended over SSDs for better performance.
  • The CPU is another possible bottleneck. Some users have reported that overclocking has helped dissipate the problem.
  • For validators on AWS,i4i.2xlarge is a good example of machine spec which has been reported to work without issues.
  • For more context, please see this relevant discussion.
• My BGT rewards are delayed or missing!
  • Please review your cutting board, ensure that the weights are setup exactly the way you expect them.
  • You can use any of these tools to make the job easy.
  • Currently the rewards distribution is less centralized and (very rarely) likely to be disrupted. The berachain team will continue to monitor and fix any problems, but expect more decentralization (and more resileince) in the future.
  • If you updated your cutting board and are worried about the status of the update, you can check the current status through a contract call. Please see discussion here.
• I have questions on snapshots?
  • More information here.
• I'm unable to update the cutting board - returns an error
  • Please see above for tools that you can use to update your cutting board. You can also run trasanctions from the command-line (ex. cast)
  • Check the transaction details on the explorer - what does it say? For example, this transaction returned an error because the operator address was not registered.
  • To set the operator address, run: cast send 0xfb81E39E3970076ab2693fA5C45A07Cc724C93c2 "setOperator(address)" 0xYOUROPERATORADDRESS --rpc-url ETH_RPC_URL --private-key YOURPRIVATEKEYWITHOUT0x
  • Please make sure to read the instructions very carefully - addresses, amounts, etc.
  • Vault addresses can be found on BGT Station, labeled as “reward vault”, or on Bartio Explorer as “contract address”.
  • Ensure you have set an execution block number sufficiently far in the future from the current execution block. (use the Bartio Explorer to see the current block number)
  • To update cutting board, run:
    cast send 0xfb81E39E3970076ab2693fA5C45A07Cc724C93c2 \ # Berachef address "queueNewCuttingBoard(address,uint64,(address,uint96)[])" \ $VALIDATOR_ADDRESS \ # Your execution-side validator address (suggested-fee-recipient) $FUTURE_BLOCK_NUMBER \ # The future block number you want to queue this cutting board to begin at '[(0xe5519D97eA854291c35a494b28929fA7abEf12e8,5000),(0x175e2429bCb92643255abCbCDF47Fff63F7990CC,5000)]' # The array of reward vault addresses + their % of BGT emissions from your cutting board
• How do I check for peering issues?
  • Poor peering can result in your node falling behind and potentially missing out on rewards.
  • Keep an eye on your logs if your suspect any peering problems - these will usually show up as a "connection refused" message, "could not resolve host" etc.
  • Check for established connections to your node. ex. on linux netstat -plant|grep ESTABLISHED, which gives you the source addresses to verify peering.
  • See the number of peers: curl -sS localhost:26657/net_info| jq .result.n_peers
  • Check the list of who is peering with you: curl -sS http://localhost:26657/net_info | jq -r '.result.peers[] | "\(.node_info.id)@\(.remote_ip):\(.node_info.listen_addr)"' | awk -F ':' '{print $1":"$(NF)}'
  • Get a JSON output that is useful for debugging curl -sS localhost:26657/status | jq .
  • Check your geographic region for the availability of nearby peers; consider relocating to a different region.
  • Change your execution client - remember that peering can affect both the execution and consensus layers. Reth appears to have substantially more peers than geth.
  • Make sure that you have alerting set up on both layers to catch any problems proactively. More information was provided during the monitoring office hours.

Contributing

Your contributions are welcome! Please feel free to submit a Pull Request.

Changelog

• 2024-11-05: Additional info added by Max from H2O Nodes.
• 2024-08-02: Initial release