-
Ref https://github.com/lazyledger/rsmt2d/pull/44#issuecomment-819134397
-
We need to define the public API and the protocol to interact with a _storage node_.
This also plays into data availability (which might be started being spec'ed out in #2) as consensus participant…
-
We should add architecture diagrams that clarifies at least the following relations:
1) LazyLedger layer-1 (including block producers/validators)
2) application specific sidechain dealing with state…
-
To avoid future messes, we should define a mechanism to deploy upgrades (i.e. hard forks, and potentially also soft forks).
https://github.com/cosmos/cosmos-sdk/blob/b4820fe491e91cd95340f2f7b606ada…
-
Use https://github.com/lazyledger/smt/ instead of https://github.com/cosmos/iavl which is the default state tree in the cosmos sdk.
Ideally, this would be done in a way that makes upstreaming this …
-
Currently the only evidence type is double-signing. There should be additional types for anything slashable, i.e. anything that would trigger a fraud proof.
Upcoming new Tendermint evidence types: …
-
As a result of the conclusions reached in cosmos/cosmos-sdk#7100, the Cosmos-SDK is undergoing a switch away from the [IAVL](https://github.com/cosmos/iavl) library which is going to impact the long t…
-
#47 cleaned up a number of issues around Merkle tree specs. Additional proof formats still need to be defined
* [ ] Merkle multiproofs
* [ ] Exclusion proof for Sparse Merkle tree (rather, inclusi…
-
Define the process and parameters (number of samples) for doing Data Availability Sampling (DAS).
-
One thing we haven't really thought about yet: LazyLedger (app) messages could potentially become quite large. I'm not sure if the tendermint mempool in its current form will able to cope with these. …