consensus: create new config for each authority

[bmwill]

Create a new Narwhal configuration for each authority we want to start
in order to avoid binding to the exact same ports. Eventaully we'll want
this config to be a part of a larger ValidatorConfig.

[asonnino]

Create a new Narwhal configuration for each authority we want to start
in order to avoid binding to the exact same ports. Eventaully we'll want
this config to be a part of a larger ValidatorConfig.

The consensus parameters do not contain port information at all (those are found in the committee config). The parameters only contains things like block size, max block delays, etc and it is important (for performance) that every node has the same.

[bmwill]

@asonnino while they may not contain network information for the primary/worker and transaction interfaces, they most certainly do contain network information for the interface @arun-koshy recently added.

https://github.com/MystenLabs/narwhal/blob/main/config/src/lib.rs#L110-L111

https://github.com/MystenLabs/narwhal/blob/main/config/src/lib.rs#L118-L119

[asonnino]

@asonnino while they may not contain network information for the primary/worker and transaction interfaces, they most certainly do contain network information for the interface @arun-koshy recently added.

https://github.com/MystenLabs/narwhal/blob/main/config/src/lib.rs#L110-L111

https://github.com/MystenLabs/narwhal/blob/main/config/src/lib.rs#L118-L119

Ha I see

[bmwill]

yeah, whether that was intended or not could be up for debate. I'm currently working on overhauling sui's configs. so i'm finding little quirks like this everywhere :)