CHAMI Rachid
CHAMI Rachid
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, the QGB orchestrator queries the state for attestations, confirms and unbonding periods. After [ADR-005](https://github.com/celestiaorg/celestia-app/blob/22a48e47721acb57030b5c520994ef9d0bd4d82a/docs/architecture/adr-005-qgb-reduce-state-usage.md) which reduces the QGB state usage, the confirms are no longer part of the state....
We should use the existing https://github.com/celestiaorg/celestia-app/blob/e18de882c3de4ee92e4632af21d4007c1b642adb/testutil/test_app.go#L71 for the QGB tests instead of: ```golang func SetupTestChain(t *testing.T, weights []uint64) (TestInput, sdk.Context) { ``` _Originally posted by @evan-forbes in https://github.com/celestiaorg/celestia-app/pull/742#discussion_r975808339_
Implementation of the https://github.com/celestiaorg/celestia-app/pull/657
If a validator edits their orchestrator/ethereum address, the state machine must react to that. Currently: - if they change their orchestrator address, then it's alright, nothing will change - If...
[not blocking] this error message seems a bit confusing b/c now it's possible for the "last" block to be higher than the current chain height. "last" can be exactly one...
As discussed in https://github.com/celestiaorg/celestia-core/pull/878#discussion_r1060145980 and https://github.com/celestiaorg/celestia-core/pull/878#discussion_r1040780793, we could add support for light nodes generating the data root inclusion proofs since they have access to the headers and thus have all...