So i totally understand $DUSK uses something called Kadcast as its main protocol for spreading blocks, transactions, and consensus votes across the network. It's not something built from zero it actually takes a lot of inspiration from Kademlia distributed hash table setup, especially the whole XOR distance concept. Basically, instead of just dumping messages onto every single neighbor like old-school gossip protocols do, it's smarter about it — it sends data through specific, structured paths using selected peers.
Breaking it down a bit:
Every node has its own identifier, and the XOR distance between nodes decides how peers get organized around each other.
Peers aren't just randomly connected they're grouped into what's called routing buckets, based on how far apart they are from a node.
When a message needs to spread, it doesn't go to everyone at once it's passed along through a chosen set of peers instead of flooding the whole network.
Since each bucket holds more than one peer, there's a safety net if one peer drops out or fails, there are other paths ready to carry the message forward.
There's also a security layer built in messages get signed, and before anything gets forwarded further, that signature is checked. This helps stop bad actors from messing with how data spreads.
And in terms of actual performance, @Dusk_Foundation has reported that this setup cuts bandwidth usage by around 25–50% compared to regular gossip-style protocols. That said, it's worth keeping in mind this number comes from Dusk's own testing and design claims it's not some fixed guarantee that'll hold true in every single setup or condition out there. #dusk
Breaking it down a bit:
Every node has its own identifier, and the XOR distance between nodes decides how peers get organized around each other.
Peers aren't just randomly connected they're grouped into what's called routing buckets, based on how far apart they are from a node.
When a message needs to spread, it doesn't go to everyone at once it's passed along through a chosen set of peers instead of flooding the whole network.
Since each bucket holds more than one peer, there's a safety net if one peer drops out or fails, there are other paths ready to carry the message forward.
There's also a security layer built in messages get signed, and before anything gets forwarded further, that signature is checked. This helps stop bad actors from messing with how data spreads.
And in terms of actual performance, @Dusk_Foundation has reported that this setup cuts bandwidth usage by around 25–50% compared to regular gossip-style protocols. That said, it's worth keeping in mind this number comes from Dusk's own testing and design claims it's not some fixed guarantee that'll hold true in every single setup or condition out there. #dusk