Context
|
github.com/celestiaorg/celestia-app/v8 v8.0.0-20260319203113-2ec59a0a61e4 |
Problem
The main branch of celestia-node isn't compatible with the main branch of celestia-app. IMO the main branch in celestia-node should use the latest official release of celestia-app, likely v8.0.1-mocha for now or v8.0.1 when that is released.
We don't need Fibre support in celestia-node until v10 so we also don't need go-square v4 on celestia-node main for a while.
Tangent: This is why Rachid is unlinking Fibre from celestia-app because we plan on creating a celestia-app v9 release which doesn't use Fibre. celestia-node main should likely target compatibility with celestia-app v9.
Proposal
Context
celestia-node/go.mod
Line 13 in bd4fd29
Problem
The
mainbranch of celestia-node isn't compatible with themainbranch of celestia-app. IMO themainbranch in celestia-node should use the latest official release of celestia-app, likelyv8.0.1-mochafor now orv8.0.1when that is released.We don't need Fibre support in celestia-node until v10 so we also don't need go-square v4 on celestia-node
mainfor a while.Tangent: This is why Rachid is unlinking Fibre from celestia-app because we plan on creating a celestia-app v9 release which doesn't use Fibre. celestia-node
mainshould likely target compatibility with celestia-app v9.Proposal
mainto usev8.0.1-mocha. This may involve removing Fibre features from celestia-node or placing them behind a build flag like feat!: unlink the fibre module by default and allow adding it using a build tag celestia-app#6957