Additional Resources

Overview

This section provides quick reference materials for node operators, including commonly used commands, file locations, network parameters, and support resources.

Useful Commands Reference

# Node status
evmd status --node http://localhost:26657

# Validator info
evmd query staking validator $(evmd keys show validator --bech val -a --keyring-backend file --home $HOME/.evmd)

# Account balance
evmd query bank balances $(evmd keys show validator -a --keyring-backend file --home $HOME/.evmd)

# Network validators
evmd query staking validators --node http://localhost:26657

# Blockchain sync info
curl -s http://localhost:26657/status | jq '.result.sync_info'

# Node peers
curl -s http://localhost:26657/net_info | jq '.result.peers'

# Latest block
curl -s http://localhost:26657/block | jq '.result.block.header'

Configuration File Locations

Directory Structure

$HOME/.evmd/
├── config/
│   ├── app.toml              # Application configuration (APIs, EVM, telemetry)
│   ├── config.toml           # Tendermint consensus and networking
│   ├── genesis.json          # Chain genesis state
│   ├── node_key.json         # P2P node identity (backup securely)
│   └── priv_validator_key.json  # Validator signing key (CRITICAL - backup encrypted)
├── data/
│   ├── application.db/       # Application state database
│   ├── blockstore.db/        # Block storage
│   ├── cs.wal/              # Consensus write-ahead log
│   ├── evidence.db/         # Evidence storage
│   ├── snapshots/           # State sync snapshots
│   ├── state.db/            # Consensus state
│   └── tx_index.db/         # Transaction index
└── keyring-file/            # Encrypted keyring (or keyring-os/ for OS keyring)
    └── *.address, *.info    # Encrypted account keys

Key File Descriptions

• Directory Structure:

  • Node home: $HOME/.evmd/

  • Config directory: $HOME/.evmd/config/

  • Data directory: $HOME/.evmd/data/

  • Keyring: $HOME/.evmd/keyring-file/ (or keyring-os/ based on backend)

  • Logs: sudo journalctl -u evmd

• Key File Descriptions:

  • config.toml - Consensus timeouts, P2P settings, RPC configuration, state sync, mempool limits

  • app.toml - Gas prices, API/gRPC/JSON-RPC endpoints, EVM settings, telemetry, pruning

  • genesis.json - Initial chain state, module parameters, validator set (must match network)

  • priv_validator_key.json - Your validator's consensus signing key (NEVER share, backup encrypted)

  • node_key.json - P2P network identity (can be regenerated, but changes peer ID)

Network Information

Mainnet:

• Chain ID: 9001 - Unique identifier for the Bitplanet network. Used to prevent transaction replay attacks across different networks.

• Base Denomination: bplcoin - The smallest unit of the native BPL token. All amounts are expressed in bplcoin (1 BPL = 10^18 bplcoin).

• Block Time: How often new blocks are produced. Fast finality means transactions are confirmed quickly.

• Unbonding Period: 21 days (default, configurable via governance) - How long staked tokens remain locked after initiating withdrawal. This security measure prevents validators from quickly unstaking after misbehavior. The actual period can be adjusted through governance proposals.

Key Ports:

• 26656 - P2P networking: Node-to-node communication for block and transaction propagation. Must be publicly accessible for validators.

• 26657 - Cosmos RPC: Query blockchain state, submit transactions via Cosmos-native endpoints.

• 1317 - REST API: HTTP REST endpoints for querying blockchain state. Used by web applications and light clients.

• 9090 - gRPC: High-performance RPC protocol for efficient client-server communication.

• 9091 - gRPC-Web: Browser-compatible version of gRPC for web applications.

• 8545 - Ethereum JSON-RPC: Ethereum-compatible API for EVM interactions, MetaMask, and Web3 applications.

• 8546 - Ethereum WebSocket: Real-time event streaming for smart contract events and block updates.

• 6060 - Prometheus metrics: Performance monitoring and observability data for node operators.

For Production Deployment: Contact the Bitplanet team or check the official documentation for the latest network information before joining mainnet.

Support & Community

Official Resources

• GitHub Repository: https://github.com/Bitplanet-L1/Bitplanet-CosmosEVM

• Issue Tracker: https://github.com/Bitplanet-L1/Bitplanet-CosmosEVM/issues

Useful Scripts

The repository includes helpful scripts:

• local_node.sh - Start a local testnet for development

• join_validator.sh - Automated validator setup and joining

• Makefile - Build commands (make install, make sh-testnet)

Next Steps

• Review hardware requirements in Hardware Requirements

• Check setup procedures in Setup & Configuration

• Learn about daily operations in Operations

• Follow step-by-step procedures in Runbooks