Skip to main content
Tavchain is an independent EVM Layer 1. Its node application combines a Cosmos SDK application, CometBFT-family consensus and EVM execution, derived from Cronos 1.8.1.

Protocol and application access

Validators agree on blocks and execute the chain’s state transitions. A non-validator full node follows and verifies the same history without participating in consensus voting. Wallets and applications use Ethereum JSON-RPC to read state, estimate execution and submit signed transactions. Native node tools use the chain’s native RPC and identifiers. The two interfaces serve different audiences.

Supporting services

  • RPC provides application access to chain data and transaction submission.
  • Explorer indexes blocks, transactions, contracts and token activity.
  • Faucet distributes Test TAV for development.
These services do not hold a user’s wallet signing key. Explorer indexing and service availability are distinct from consensus and can lag or fail independently.

Trust boundaries

Tavchain does not settle to Ethereum and does not inherit Base or Celo’s rollup security. The initial testnet validators are administered together. Multiple validators share a hosting failure domain, so validator count alone does not imply independent operation. Read Consensus, finality and security for the control and availability assumptions. Node roles · Network settings · Protocol overview