-
The current public facing API:
Should we:
- add methods to the extended data square…
-
## Summary of Bug
After using command `celestia-appd export`, our app is panicking due to UnmarshalJSON error
## Version
d255f0ce461e8cc72f48282593a876cca9cb6c91
## Steps to Repro…
-
## Summary
Current RetrieveBlockData implementation spawns a goroutine per each share in ExtendedDataSquare. In the worst case with the max block 128X128 that is 16384 goroutines. This causes the rac…
-
## Summary
A lot was discussed and said about block propagation (during consensus and in other cases) already. We should capture the decision on how to move forward with the implementation in an AD…
-
## Summary
In Tendermint, the [BlockID](https://github.com/tendermint/tendermint/blob/884d4d525299e4d43ab881ac19062501c1e09ddf/types/block.go#L1172-L1176) is comprised of the `Header` [hash](https:…
-
## Summary
To be able to evict the mempool depending on the data that was written into the block.
## Problem Definition
Currently, tendermint evicts the mempool using the Mempool.Update metho…
-
After defining `WirePayForMessage` and connecting it the rest of the application, the draft implementation for PreprocessTxs needs to:
1. cleanly separate share messages from other transactions
2. p…
-
Use [this plugin](https://github.com/lazyledger/lazyledger-core/pull/144) when tackling #4 and #5.
An alternative to explicitly use the plugin, could be to actually spin up a lazyledger-app node an…
-
Tendermint currently uses ed25519, and the SDK uses secp for accounts/signing tx. The LL spec currently proposes to use secp for everything instead.
Additionally, we want to be able to recover the…
-
We need to define the messages that are exchanged by nodes during consensus.
IMO, most of the messages defined by tendermint can be used and do not require any changes. The main change would be re…