Skip to main content
Tavchain Testnet is an unaudited network. Understand its validator control, availability and application risks before using it.

Consensus and finality

The validator set uses CometBFT-family consensus. A block is committed after valid precommits representing more than two-thirds of the current validator voting power. The threshold uses voting power, not the number of nodes. Under the consensus assumptions, including less than one-third faulty voting power, committed blocks have deterministic finality. Quorum loss can halt new blocks. Waiting for extra confirmations does not remove shared-administration risk, and Tavchain does not wait for settlement on Ethereum. A full node verifies the chain, while applications commonly rely on RPC responses and transaction receipts. A successful receipt records execution in a block. It does not audit a contract, establish a token’s value or guarantee the correctness of an explorer index.

Validator control and availability

The current testnet has four validators under shared administration. They are not four independent operators. Several validators share one hosting failure domain; an outage affecting that group can halt consensus, and compromise of a quorum can compromise the network. Public RPC and explorer users rely on those services to report chain state. Running a full node provides a separate local verification path, but does not change the validator control model.

Accounts and contracts

Keep wallet seeds, private keys and passwords private. Neither the faucet nor support needs them. Use dedicated test accounts and do not deposit real assets. Test TAV has no monetary value, and demonstration contracts are not audited financial products.

Report a vulnerability

Email support@safeney.com with the subject Tavchain security report. Describe the affected component, impact and safe reproduction steps. Do not publish sensitive exploitation details or include credentials. See reporting guidance. Network reference · Governance and upgrades