github celestiaorg/celestia-node v0.2.0

latest releases: v0.20.1-rc1, v0.18.0-not-final-experiment-v3.3, v0.18.0-not-final-experiment-v3.2...
2 years ago

v0.2.0 | 2022-02-23

The second minor release focuses on the stability and robustness of existing features via refactorings, mainly for
headers synchronization and storing, while fixing the DA network segregation by providing bootstrap peers, allowing you to
run a Light Node with zero effort. The release also includes a few breaking changes.

Highlights

Hardcoded bootstrap peers

Bootstrappers are necessary for peers to connect to when they come online in order to be part of the DA p2p network.
Additionally, they serve block headers and shares for everyone, so any other node joining the network can use them to
synchronize headers and perform Data Availability Sampling. Now it's unnecessary to maintain your own Bridge(previously
Full) Node to run a Light Node, as now it will rely on bootstrappers by default.

Zero effort Light Node

Now becoming a valuable node that contributes to the security of the of Celestia network is only two commands away. Simply run celestia light init followed by celestia light start, and you are good to go. Still, you can keep running your own Bridge Node as the trusted peer.

Test Swamp

The release comes with a new internal testing library for Celestia Node called Test Swamp, aimed to provide an
ergonomic framework for integration tests for celestia-node. It allows simulating a network on which we can test various
high-level scenarios.

Header Synchronization

It was almost rewritten from scratch with a better design which:

  • Tolerates network disconnections
  • Tolerates primary network interface changes
    • both above are useful for Light Node running on laptops or mobile phones
  • Optimizes bandwidth and IO usage, subsequently speeding up the synchronization time for ~20%
  • Eliminates long-standing issue with header duplicates flooding the network
  • Fixes the most common issue community has faced - constant logging of invalid headers error.

Renamed Full Node

Full Node is now called Bridge Node to emphasize its purpose of bridging the core consensus and the halo DA networks, both
powering the Celestia project.

Spoiler: Next release will come with a reincarnation of the Full Node type, which operates only over the DA celestia-node network

Full node operators after the update should now migrate to Bridge Node. This migration is trivial:

  • Rename .celestia-full to .celestia-bridge
  • Change scripts from celestia full to celestia bridge

Trusted Peers

  • trusted-peer is now trusted-peers as the flag now allows passing multiple trusted peers.
  • Config.Services.TrustedPeer is now Config.Services.TrustedPeers

BREAKING CHANGES

FEATURES

IMPROVEMENTS

BUG FIXES

MISCELLANEOUS

Don't miss a new celestia-node release

NewReleases is sending notifications on new releases.