-
## Dev-net
After our MVP we want to be able to deploy a basic dev-net.
### Goals
The main goal of the dev-net is to test DAS in a much more realistic setting and at the same time test the de…
-
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 i…
-
Ref https://github.com/lazyledger/rsmt2d/pull/50#discussion_r615941444
-
Full nodes should be able to:
- generate fraud proofs and
- gossip those to other nodes (we still need to decide if gossiping should be done by the app or in lazyledger-core)
Additionally, th…
-
LazyLedger DA client must be finished - currently it builds `PayForMessage` and tries to submit it do lazyledger-app.
It should also implement DA checks and retrieval as described in #61 and #62.
…
-
## Summary
I think some parts spec still deviate from existing implementations in the Cosmos-SDK. In some cases this might inevitable (e.g. changes to the staking logic to make it efficiently fraud…
-
The latest release isn't usable as it still uses `lazyledger` in the module name.
-
## Description
I wanted to bring up everyone's favorite topic again. Namely serialization.
First, I want to note that the way we [arrange data](https://github.com/lazyledger/lazyledger-specs/blob/ma…
-
## Goal
The Celestia Node controls Celestia Core in the embedded(default) case and should also control the creation of genesis block, genesis transaction, and/or genesis document which would dictate …
-