search

consensus-shipyard / consensuslab

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

🎯 | B3.2-M3: Cross-net messages #129

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 
- Deliverables:
    - __Sign Checkpoint__: The child subnet participants should collect signatures and produce a checkpoint, ready to be sent to the parent chain. Should it be stored on the child chain at all? What is a good checkpointing scheme with _Delegated Consensus_? Need to check what the Subnet Actor supports.
    - __Cross Message Pool__: Prescribed by the spec as a staging area for cross messages included in the ledger, to be resolved by CID, and included in an upcoming block. Also cleared out when included by other validators.
    - __Cross Message Resolution__: Mechanism to resolve CID to content using libp2p gossip-sub. 
    - __Cross Message execution__
    - __Demo: exchange of cross-messages__
- Date: 1st October
- Demo: 6th October