I kept running the DUSK nodes for over a week, watching the traffic charts every day. The data on the outbound side was a bit abnormally low. I even thought, for the first couple of days, that the client was just being lazy, and I restarted it several times.
I spent half a day digging through the documentation to figure out what “Kadcast” is. It lives in the network layer, built on the same structured addressing model as Kademlia DHT. Messages get forwarded along a tree-shaped path—one to ten, ten to a hundred—while each node only handles a small set of neighbors. Compared with Gossip’s all-network broadcast, where every message has to shout through all connections (and the bandwidth bills just keep piling up), Kadcast shuts that loophole tight. The denser the nodes, the more it saves on cost. This algorithm is basically born with the whole network in mind. $ETH
Phoenix handles the accounting ledger, Piecrust handles execution, and Kadcast handles the network. When I add it up, this DUSK chain is building privacy like it’s three stories high. The network layer is the easiest for non-experts to overlook—but it’s actually the foundation. If messages can’t be transmitted properly, then no matter how fancy the stuff upstairs is, it’s still pointless. Their network layer is made to “eat grass” and “squeeze out milk.”
I tested it on my own node: routed the broadcast through the Kadcast path, captured packets, and looked for a long time. Other than the expected neighbor communications, there was nothing else I could read. That kind of cleanliness was the first time I’d run into it—and it also cured my suspicions from those first two days. #dusk $DUSK @Dusk
I spent half a day digging through the documentation to figure out what “Kadcast” is. It lives in the network layer, built on the same structured addressing model as Kademlia DHT. Messages get forwarded along a tree-shaped path—one to ten, ten to a hundred—while each node only handles a small set of neighbors. Compared with Gossip’s all-network broadcast, where every message has to shout through all connections (and the bandwidth bills just keep piling up), Kadcast shuts that loophole tight. The denser the nodes, the more it saves on cost. This algorithm is basically born with the whole network in mind. $ETH
Phoenix handles the accounting ledger, Piecrust handles execution, and Kadcast handles the network. When I add it up, this DUSK chain is building privacy like it’s three stories high. The network layer is the easiest for non-experts to overlook—but it’s actually the foundation. If messages can’t be transmitted properly, then no matter how fancy the stuff upstairs is, it’s still pointless. Their network layer is made to “eat grass” and “squeeze out milk.”
I tested it on my own node: routed the broadcast through the Kadcast path, captured packets, and looked for a long time. Other than the expected neighbor communications, there was nothing else I could read. That kind of cleanliness was the first time I’d run into it—and it also cured my suspicions from those first two days. #dusk $DUSK @Dusk