lazy-adr: erasure coded block propagation #163
Conversation
|
ref: #85 |
| LoadBlockCommit(height int64) *types.Commit | ||
| LoadSeenCommit(height int64) *types.Commit | ||
| } | ||
| ``` |
There was a problem hiding this comment.
Makes sense to me. The Store interface for light clients is not an option because it expects a canonical commit with each header?
There was a problem hiding this comment.
Currently, in tendermint, light clients request data from full nodes. In our case they only need to connect to a full node to get DAheaders and header. Otherwise, all requests will go through IPFS, correct?
There was a problem hiding this comment.
Yes, that is correct. Implementation wise, we should prob. do this in (at least) two steps: add requesting block data from IPFS while having the store and the reactors work as before, then step by step replace everything by ipfs apis.
There was a problem hiding this comment.
Thanks a lot @marbar3778! 👍🏼
Do you mind opening a few issues that can be implemented as an outcome of this ADR?
I think, we should merge this, start implementing different portions, and keep the ADR in sync with the implementation.
I released tm-load-test v1.3.0 earlier (see https://github.com/informalsystems/tm-load-test/releases/tag/v1.3.0) to remove its dependency on Tendermint Core. cc @lasarojc --- #### PR checklist - [x] Tests written/updated, or no tests needed - [x] `CHANGELOG_PENDING.md` updated, or no changelog entry needed - [x] Updated relevant documentation (`docs/`) and code comments, or no documentation updates needed
Description
This adr outlines changes required to have erasure coded block propagation/pulling
Closes: #XXX