Alberto Sonnino

Allows to change the committee at any point, even if it is not the end of an epoch. This is useful if we wants to change the committee to only...

### Description Do we really need to return the new committee after a reconfiguration to `executor::Core`? (We will know once we integrated Narwhal with Sui.)

Cleanup Network

1

### Description Most of our networks (PrimaryToWorkerNetwork, PrimaryNetwork, WorkerNetwork) have a HashMap of address -> clients. When the committee changes and the network addresses change, the networks will simply expand...

Consensus crash-recovery

5

### Description To ensure crash-recovery of consensus, it is not enough to have the `CertificatesWaiter` to send to consensus every certificate for which their ancestors are in the storage. After...

Support reconfiguration when only the network addresses change (and nothing else). In this case, we shouldn't cleanup internal state like we do upon epoch change.

The networking stack currently doesn't understand the notion of reconfiguration. Swapping the committee under its feet is enough for many use-cases but a problem for reliable/quorum broadcast. We may want...

Limit empty-headers

2

See section "(F) Validity": https://www.notion.so/mystenlabs/Narwhal-Progress-d954e29f6e0d4f7ebfa3c1dd6bbcfe48

Reliable worker-primary connection

3

Now that we want to be able to crash-recover and rotate network addresses, we should re-think the connection between primary and its workers. Currently the workers assume the primary is...

See Section "(C) Sequencing.": https://www.notion.so/mystenlabs/Narwhal-Progress-d954e29f6e0d4f7ebfa3c1dd6bbcfe48

Support large transaction sizes

1

It is unclear whether Narwhal can support large transaction sizes (MBs). We should try and make a test.