celestia-core is a fork of cometbft/cometbft, an implementation of the Tendermint protocol, with the following changes:
PrepareProposal and ProcessProposal because they haven't yet landed in a CometBFT release.DataHash in the block header is determined. In CometBFT, DataHash is based on the transactions included in a block. In Celestia, block data (including transactions) are erasure coded into a data square to enable data availability sampling. In order for the header to contain a commitment to this data square, DataHash was modified to be the Merkle root of the row and column roots of the erasure coded data square. See ADR 008 for the motivation or celestia-app/pkg/da/data_availability_header.go for the implementation. Note on the implementation: celestia-app computes the hash in prepare_proposal and returns it to CometBFT via blockData.Hash so a modification to celestia-core isn't strictly necessary but comments were added.BlockAPIBlobstreamAPISee ./docs/celestia-architecture for architecture decision records (ADRs) on Celestia modifications.
^ +-------------------------------+ ^
| | | |
| | State-machine = Application | |
| | | | celestia-app (built with Cosmos SDK)
| | ^ + | |
| +----------- | ABCI | ----------+ v
Celestia | | + v | ^
validator or | | | |
full consensus | | Consensus | |
node | | | |
| +-------------------------------+ | celestia-core (fork of CometBFT)
| | | |
| | Networking | |
| | | |
v +-------------------------------+ v
See https://github.com/celestiaorg/celestia-app#install
See https://github.com/celestiaorg/celestia-app#usage
This repo intends on preserving the minimal possible diff with cometbft/cometbft to make fetching upstream changes easy. If the proposed contribution is
# Build a new CometBFT binary and output to build/comet
make build
# Install CometBFT binary
make install
# Run tests
make test
# If you modified any protobuf definitions in a `*.proto` file then
# you may need to lint, format, and generate updated `*.pb.go` files
make proto-lint
make proto-format
make proto-gen
main is the canonical branch for development. Most PRs should target main and optionally be backported to a release branch.
| Branch | Based on CometBFT | Release format | Used by celestia-app |
|---|---|---|---|
v0.42.x | v0.38.x | v0.42.0 | v10.x |
v0.40.x | v0.38.x | v0.40.0 | v9.x |
v0.39.x-celestia | v0.38.x | v0.39.0 | v6.x through v8.x |
v0.38.x-celestia | v0.38.x | v1.54.1-tm-v0.38.17 | v4.x and v5.x |
v0.34.x-celestia | v0.34.x | v1.52.1-tm-v0.34.35 | v1.x through v3.x |
Branches cut from main after v0.39.x-celestia have no -celestia suffix. Newer celestia-app versions still depend on v0.34.x-celestia to multiplex ABCI v1 requests, via a github.com/tendermint/tendermint replace directive.
The replace directives in celestia-app's go.mod are the source of truth for which celestia-core version a given celestia-app branch consumes.
Previous releases were formatted: v<CELESTIA_CORE_VERSION>-tm-v<COMETBFT_VERSION>.
For example: v1.4.0-tm-v0.34.20 is celestia-core version 1.4.0 based on CometBFT 0.34.20. CELESTIA_CORE_VERSION strives to adhere to Semantic Versioning.
Recent releases after v0.39.0 do not include the CometBFT version.
Overall
Maintained
Code review
Go module
Latest release
Releases this year
194 followers · starred Jan 2024
7,782 followers · starred Jun 2022
454 followers · starred Jul 2026
222 followers · starred Feb 2022
celestia-core is a fork of cometbft/cometbft, an implementation of the Tendermint protocol, with the following changes:
PrepareProposal and ProcessProposal because they haven't yet landed in a CometBFT release.DataHash in the block header is determined. In CometBFT, DataHash is based on the transactions included in a block. In Celestia, block data (including transactions) are erasure coded into a data square to enable data availability sampling. In order for the header to contain a commitment to this data square, DataHash was modified to be the Merkle root of the row and column roots of the erasure coded data square. See ADR 008 for the motivation or celestia-app/pkg/da/data_availability_header.go for the implementation. Note on the implementation: celestia-app computes the hash in prepare_proposal and returns it to CometBFT via blockData.Hash so a modification to celestia-core isn't strictly necessary but comments were added.BlockAPIBlobstreamAPISee ./docs/celestia-architecture for architecture decision records (ADRs) on Celestia modifications.
^ +-------------------------------+ ^
| | | |
| | State-machine = Application | |
| | | | celestia-app (built with Cosmos SDK)
| | ^ + | |
| +----------- | ABCI | ----------+ v
Celestia | | + v | ^
validator or | | | |
full consensus | | Consensus | |
node | | | |
| +-------------------------------+ | celestia-core (fork of CometBFT)
| | | |
| | Networking | |
| | | |
v +-------------------------------+ v
See https://github.com/celestiaorg/celestia-app#install
See https://github.com/celestiaorg/celestia-app#usage
This repo intends on preserving the minimal possible diff with cometbft/cometbft to make fetching upstream changes easy. If the proposed contribution is
# Build a new CometBFT binary and output to build/comet
make build
# Install CometBFT binary
make install
# Run tests
make test
# If you modified any protobuf definitions in a `*.proto` file then
# you may need to lint, format, and generate updated `*.pb.go` files
make proto-lint
make proto-format
make proto-gen
main is the canonical branch for development. Most PRs should target main and optionally be backported to a release branch.
| Branch | Based on CometBFT | Release format | Used by celestia-app |
|---|---|---|---|
v0.42.x | v0.38.x | v0.42.0 | v10.x |
v0.40.x | v0.38.x | v0.40.0 | v9.x |
v0.39.x-celestia | v0.38.x | v0.39.0 | v6.x through v8.x |
v0.38.x-celestia | v0.38.x | v1.54.1-tm-v0.38.17 | v4.x and v5.x |
v0.34.x-celestia | v0.34.x | v1.52.1-tm-v0.34.35 | v1.x through v3.x |
Branches cut from main after v0.39.x-celestia have no -celestia suffix. Newer celestia-app versions still depend on v0.34.x-celestia to multiplex ABCI v1 requests, via a github.com/tendermint/tendermint replace directive.
The replace directives in celestia-app's go.mod are the source of truth for which celestia-core version a given celestia-app branch consumes.
Previous releases were formatted: v<CELESTIA_CORE_VERSION>-tm-v<COMETBFT_VERSION>.
For example: v1.4.0-tm-v0.34.20 is celestia-core version 1.4.0 based on CometBFT 0.34.20. CELESTIA_CORE_VERSION strives to adhere to Semantic Versioning.
Recent releases after v0.39.0 do not include the CometBFT version.
Overall
Maintained
Code review
Go module
Latest release
Releases this year
194 followers · starred Jan 2024
7,782 followers · starred Jun 2022
454 followers · starred Jul 2026
222 followers · starred Feb 2022