By default, CometBFT uses the
syndtr/goleveldb package for its in-process
key-value database. If you want maximal performance, it may be best to install
the real C-implementation of LevelDB and compile CometBFT to use that using
make build COMETBFT_BUILD_OPTIONS=cleveldb. See the install
instructions for details.
CometBFT keeps multiple distinct databases in the
blockstore.db: Keeps the entire blockchain - stores blocks, block commits, and block meta data, each indexed by height. Used to sync new peers.
evidence.db: Stores all verified evidence of misbehavior.
state.db: Stores the current blockchain state (ie. height, validators, consensus params). Only grows if consensus params or validators change. Also used to temporarily store intermediate results during block processing.
tx_index.db: Indexes txs (and their results) by tx hash and by DeliverTx result events.
By default, CometBFT will only index txs by their hash and height, not by their DeliverTx result events. See indexing transactions for details.
Applications can expose block pruning strategies to the node operator. Please read the documentation of your application to find out more details.
Applications can use state sync to help nodes bootstrap quickly.
Default logging level (
log_level = "main:info,state:info,statesync:info,*:error") should suffice for
normal operation mode. Read this
for details on how to configure
log_level config variable. Some of the
modules can be found here. If
you’re trying to debug CometBFT or asked to provide logs with debug
logging level, you can do so by running CometBFT with
CometBFT uses write ahead logs for the consensus (
cs.wal) and the mempool
mempool.wal). Both WALs have a max size of 1GB and are automatically rotated.
consensus.wal is used to ensure we can recover from a crash at any point
in the consensus state machine.
It writes all consensus messages (timeouts, proposals, block part, or vote)
to a single file, flushing to disk before processing messages from its own
validator. Since CometBFT validators are expected to never sign a conflicting vote, the
WAL ensures we can always recover deterministically to the latest state of the consensus without
using the network or re-signing any consensus messages.
consensus.wal is corrupted, see below.
mempool.wal logs all incoming txs before running CheckTx, but is
otherwise not used in any programmatic way. It’s just a kind of manual
safe guard. Note the mempool provides no durability guarantees - a tx sent to one or many nodes
may never make it into the blockchain if those nodes crash before being able to
propose it. Clients must monitor their txs by subscribing over websockets,
polling for them, or using
/broadcast_tx_commit. In the worst case, txs can be
resent from the mempool WAL manually.
For the above reasons, the
mempool.wal is disabled by default. To enable, set
mempool.wal_dir to where you want the WAL to be located (e.g.
Validators are supposed to setup Sentry Node Architecture to prevent Denial-of-Service attacks.
The core of the CometBFT peer-to-peer system is
MaxPacketMsgPayloadSize, which is the maximum packet
size and bounded send & receive queues. One can impose restrictions on
send & receive rate per connection (
The number of open P2P connections can become quite large, and hit the operating system’s open
file limit (since TCP connections are considered files on UNIX-based systems). Nodes should be
given a sizable open file limit, e.g. 8192, via
ulimit -n 8192 or other deployment-specific
It is generally not recommended for RPC endpoints to be exposed publicly, and especially so if the node in question is a validator, as the CometBFT RPC does not currently provide advanced security features. Public exposure of RPC endpoints without appropriate protection can make the associated node vulnerable to a variety of attacks.
It is entirely up to operators to ensure, if nodes’ RPC endpoints have to be exposed publicly, that appropriate measures have been taken to mitigate against attacks. Some examples of mitigation measures include, but are not limited to:
If no expertise is available to the operator to assist with securing nodes’ RPC endpoints, it is strongly recommended to never expose those endpoints publicly.
Under no condition should any of the unsafe RPC endpoints ever be exposed publicly.
Endpoints returning multiple entries are limited by default to return 30 elements (100 max). See the RPC Documentation for more information.
If you ever have to debug CometBFT, the first thing you should probably do is check out the logs. See How to read logs, where we explain what certain log statements mean.
If, after skimming through the logs, things are not clear still, the next thing
to try is querying the
/status RPC endpoint. It provides the necessary info:
whenever the node is syncing or not, what height it is on, etc.
/dump_consensus_state will give you a detailed overview of the consensus
state (proposer, latest validators, peers states). From it, you should be able
to figure out why, for example, the network had halted.
There is a reduced version of this endpoint -
/consensus_state, which returns
just the votes seen at the current height.
If, after consulting with the logs and above endpoints, you still have no idea
what’s happening, consider using
cometbft debug kill sub-command. This
command will scrap all the available info and kill the process. See
Debugging for the exact format.
You can inspect the resulting archive yourself or create an issue on Github. Before opening an issue however, be sure to check if there’s no existing issue already.
Each CometBFT instance has a standard
/health RPC endpoint, which responds
with 200 (OK) if everything is fine and 500 (or no response) - if something is
Other useful endpoints include mentioned earlier
CometBFT also can report and serve Prometheus metrics. See Metrics.
cometbft debug dump sub-command can be used to periodically dump useful
information into an archive. See Debugging for more
You are supposed to run CometBFT under a process supervisor (like systemd or runit). It will ensure CometBFT is always running (despite possible errors).
Getting back to the original question, if your application dies, CometBFT will panic. After a process supervisor restarts your application, CometBFT should be able to reconnect successfully. The order of restart does not matter for it.
We catch SIGINT and SIGTERM and try to clean up nicely. For other signals we use the default behavior in Go: Default behavior of signals in Go programs.
NOTE: Make sure you have a backup of the CometBFT data directory.
Remember that most corruption is caused by hardware issues:
Other causes can be:
If consensus WAL is corrupted at the latest height and you are trying to start CometBFT, replay will fail with panic.
Recovering from data corruption can be hard and time-consuming. Here are two approaches you can take:
1) Create a backup of the corrupted WAL file:
```sh cp "$CMTHOME/data/cs.wal/wal" > /tmp/corrupted_wal_backup ```
./scripts/wal2json to create a human-readable version:
```sh ./scripts/wal2json/wal2json "$CMTHOME/data/cs.wal/wal" > /tmp/corrupted_wal ```
3) Search for a “CORRUPTED MESSAGE” line. 4) By looking at the previous message and the message after the corrupted one and looking at the logs, try to rebuild the message. If the consequent messages are marked as corrupted too (this may happen if length header got corrupted or some writes did not make it to the WAL ~ truncation), then remove all the lines starting from the corrupted one and restart CometBFT.
```sh $EDITOR /tmp/corrupted_wal ```
5) After editing, convert this file back into binary form by running:
```sh ./scripts/json2wal/json2wal /tmp/corrupted_wal $CMTHOME/data/cs.wal/wal ```
While actual specs vary depending on the load and validators count, minimal requirements are:
SSD disks are preferable for applications with high transaction throughput.
While for now, CometBFT stores all the history and it may require significant disk space over time, we are planning to implement state syncing (See this issue). So, storing all the past blocks will not be necessary.
secp256k1 implementations require constant time
uint64 multiplication. Non-constant time crypto can (and has) leaked
private keys on both
secp256k1. This doesn’t exist in hardware
on 32 bit x86 platforms (source), and it
depends on the compiler to enforce that it is constant time. It’s unclear at
this point whenever the Golang compiler does this correctly for all
We do not support nor recommend running a validator on 32 bit architectures OR the “VIA Nano 2000 Series”, and the architectures in the ARM section rated “S-“.
CometBFT can be compiled for a wide range of operating systems thanks to Go language (the list of $OS/$ARCH pairs can be found here).
While we do not favor any operation system, more secure and stable Linux server distributions (like CentOS) should be preferred over desktop operation systems (like Mac OS).
NOTE: if you are going to use CometBFT in a public domain, make sure you read hardware recommendations for a validator in the Cosmos network.
If you are going to use CometBFT in a private domain and you have a private high-speed network among your peers, it makes sense to lower flush throttle timeout and increase other params.
[p2p] send_rate=20000000 # 2MB/s recv_rate=20000000 # 2MB/s flush_throttle_timeout=10 max_packet_msg_payload_size=10240 # 10KB
After every block, CometBFT rechecks every transaction left in the
mempool to see if transactions committed in that block affected the
application state, so some of the transactions left may become invalid.
If that does not apply to your application, you can disable it by
Setting this to false will stop the mempool from relaying transactions to other peers until they are included in a block. It means only the peer you send the tx to will see it until it is included in a block.
skip_timeout_commit=false when there is economics on the line
because proposers should wait to hear for more votes. But if you don’t
care about that and want the fastest consensus, you can skip it. It will
be kept false by default for public deployments (e.g. Cosmos
Hub) while for enterprise
applications, setting it to true is not a problem.
You can try to reduce the time your node sleeps before checking if theres something to send its peers.
You can also try lowering
timeout_commit (time we sleep before
proposing the next block).
By default, CometBFT checks whenever a peer’s address is routable before saving it to the address book. The address is considered as routable if the IP is valid and within allowed ranges.
This may not be the case for private or local networks, where your IP range is usually
strictly limited and private. If that case, you need to set
false (turn it off).
By default, the number of simultaneous connections is limited because most OS give you limited number of file descriptors.
If you want to accept greater number of connections, you will need to increase these limits.
Sysctls to tune the system to be able to open more connections
The process file limits must also be increased, e.g. via
ulimit -n 8192.
…for N connections, such as 50k:
kern.maxfiles=10000+2*N # BSD kern.maxfilesperproc=100+2*N # BSD kern.ipc.maxsockets=10000+2*N # BSD fs.file-max=10000+2*N # Linux net.ipv4.tcp_max_orphans=N # Linux # For load-generating clients. net.ipv4.ip_local_port_range="10000 65535" # Linux. net.inet.ip.portrange.first=10000 # BSD/Mac. net.inet.ip.portrange.last=65535 # (Enough for N < 55535) net.ipv4.tcp_tw_reuse=1 # Linux net.inet.tcp.maxtcptw=2*N # BSD # If using netfilter on Linux: net.netfilter.nf_conntrack_max=N echo $((N/8)) > /sys/module/nf_conntrack/parameters/hashsize
The similar option exists for limiting the number of gRPC connections -