celestia-app icon indicating copy to clipboard operation
celestia-app copied to clipboard

PoS application for the consensus portion of the Celestia network. Built using celestia-core (fork of CometBFT) and the cosmos-sdk

Results 269 celestia-app issues
Sort by recently updated
recently updated
newest added

Currently, in the QGB branch, we are confusing the names of the following: - `evmAddress` and `ethereumAddress` - `valset` and `valSet` - `validatorAddress` should be changed to `orchestratorAddr` in the...

good first issue
C: QGB
low priority

The QGB integration to the app includes two new transactions that validators will have to create and submit on a routine basis. These need to be well documented along with...

C: QGB

## Summary of Bug Currently, in the QGB module, we're using the following name to refer to the orchestrator: https://github.com/celestiaorg/celestia-app/blob/eaed5dbf403395ed58bf74029b1abc650fb44e26/proto/qgb/msgs.proto#L73 This needs to be updated in order to avoid confusion....

good first issue
C: QGB
low priority

Ideally, we should be able to use the cli to quickly query current state of the qgb contracts just like we can with state on celestia.

good first issue
C: QGB
low priority

This issue will track the remaining tasks required to finish the QGB MVP, ie a simple minimal version that only does the following: - Deploy the bridge smart contract -...

C: QGB
Tracking

The specification makes some changes to the staking logic used internally in the cosmos-sdk: - https://github.com/lazyledger/lazyledger-specs/blob/master/specs/consensus.md - https://github.com/cosmos/cosmos-sdk/tree/master/x/staking Some of these changes are absolutely required for fraud proofs others are...

As a default, starport chains have the ability to use IBC. We should be able to start a relayer and connect to another chain.

Currently we're using a version cosmos-sdk that only supports an iavl, in the future we will want to use a sparse merkle tree instead, as it is more conducive to...

C: Celestia app
apphash breaking

As done in https://github.com/celestiaorg/celestia-app/issues/468#issuecomment-1156887715, we can go for replacing `ValsetConfirm`s and `DataCommitmentConfirm`s with an `AttestationConfirm` interface which would simplify the implementation and remove unnecessary redundant code.

enhancement
C: QGB

When starting E2E network, the scripts used to boot up the orchestrator, relayer and nodes can fail for various reasons. These failures are sometimes due to an orchestrator/relayer starting before...

enhancement
C: QGB
testing