search

consensus-shipyard / consensuslab

The go-to place for scalable decentralised consensus research
66 stars 3 forks source link

🎯 | B3.2-M2: Lifecycle of a subnet implemented #128

Closed jsoares closed 2 years ago

jsoares commented 2 years ago

For work tracking purposes.

Refer to the parent project issue for high-level discussion and resources.

jsoares commented 2 years ago 
- Deliverable: 
    - __Spawn Subnet__: Need to understand whether it should be run as a separate process, or the same. How should the child subnet see its parent chain state (both ledger and finality)? How should it send a checkpoint, who does it via what API? Parent and child both need to subscribe to the gossip-sub topic. Where do we track existing subnets so they can be resumed after a restart?
    - __Demo Subnet__: Demonstrate that a subnet can be started with _Delegated Consensus_, which the parent and the subnet would both use. The parent and the child would _not_ talk to each other in this demo; that would require M3 features.
- Date: 10th September
- Demo: N/A