celestia-app
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
After we finish celestiaorg/celestia-app#329, we should be able to have a working QBG to begin playing with. To help test the mvp, we should deploy the qgb and bridge a...
Currently, the QGB is unable to query for the genesis params to get the data commitment window. This is necessary to know when to sign the data commitments and for...
For the QGB, we only care about the state of the current unbonding period. That is due to the following: - If no signatures are posted during this period, then...
Move the QGB module constants to a specific consts package as discussed in https://github.com/celestiaorg/celestia-app/pull/257#discussion_r838303008
Currently, when using the `--broadcast-mode block` flag, the block times on a live network are too long, resulting the cli almost always timing out. We need to communicate this to...
in the current [cli integration tes](https://github.com/celestiaorg/celestia-app/blob/master/x/payment/client/testutil/integration_test.go)t, we are checking to see that emitted events contain a multiple of the share size instead of checking for a direct size. We should...
With the introduction of ABCI++ #231, we are adding checks to proposal blocks. The current integration tests are only testing for basic functionality, when they should be testing to ensure...
Currently, we use the [`KeyringSigner`](https://github.com/celestiaorg/celestia-app/blob/b4c8ebdf35db200a9b99d295a13de01110802af4/x/payment/types/builder.go#L18-L28) to programmatically sign malleated transactions. This is because the standard cosmos-sdk `tx.Factory` does not support creating multiple malleated transactions and then signing over those as...
Namespaces are now kept in the actual message to ensure that they are recoverable, see [the spec PR](https://github.com/lazyledger/lazyledger-specs/pull/146/files). This should also be accounted for in the app, specifically `SHARE_SIZE -...
Currently, the `MaxSquareSize` constant has to be in celestia-core, but ideally, it should be a parameter in the app. This way, it doesn't require a hardfork to change, we only...