Why Dusk Uses Kadcast to Move Consensus Messages Around the Network
I was looking at Dusk’s consensus today and got stuck on a pretty simple question
Once a block is created how does all the information needed for consensus actually move through the network
At first I thought this was just a normal networking detail
Then I looked a little deeper and came across Kadcast
Dusk uses Kadcast as part of its peer-to-peer network to propagate blocks transactions and consensus-related messages between nodes
What caught my attention is that Kadcast doesn't rely only on unstructured gossip It uses a more structured way of connecting nodes to help propagate messages through the network
And that made the bigger picture clearer to me
Consensus isn't only about deciding which block everyone should accept
The network also has to move that block and the messages around it between the participants involved in reaching that decision
So there are really two different questions:
What should the network agree on
And How does the information needed for that agreement reach the network
That's why I found Kadcast interesting
It's not the flashy part of Dusk that usually gets attention but it's one of those underlying pieces that makes me appreciate how much engineering sits beneath the consensus layer
Consensus decides what Dusk agrees on
Kadcast helps carry the information needed to get there
#dusk $DUSK @Dusk
I was looking at Dusk’s consensus today and got stuck on a pretty simple question
Once a block is created how does all the information needed for consensus actually move through the network
At first I thought this was just a normal networking detail
Then I looked a little deeper and came across Kadcast
Dusk uses Kadcast as part of its peer-to-peer network to propagate blocks transactions and consensus-related messages between nodes
What caught my attention is that Kadcast doesn't rely only on unstructured gossip It uses a more structured way of connecting nodes to help propagate messages through the network
And that made the bigger picture clearer to me
Consensus isn't only about deciding which block everyone should accept
The network also has to move that block and the messages around it between the participants involved in reaching that decision
So there are really two different questions:
What should the network agree on
And How does the information needed for that agreement reach the network
That's why I found Kadcast interesting
It's not the flashy part of Dusk that usually gets attention but it's one of those underlying pieces that makes me appreciate how much engineering sits beneath the consensus layer
Consensus decides what Dusk agrees on
Kadcast helps carry the information needed to get there
#dusk $DUSK @Dusk
