#dusk $DUSK @Dusk A building can welcome everyone without leaving the server room unlocked. Obvious in real life. But when we say “permissionless,” that boundary is easy to miss.
I noticed it while digging through Dusk’s node setup. Provisioners need 9000/udp for Kadcast and consensus, but the HTTP API on 8080/tcp doesn’t need to be public. Archive Nodes even bind the API to 127.0.0.1 by default.
Hold up. A permissionless L1 whose own operational guidance explicitly tells you what not to expose.
That isn’t a contradiction. Consensus needs open participation; the machine doesn’t need open exposure. Making both public wouldn’t make Dusk more decentralized it would only increase the attack surface.
What I like is that Dusk doesn’t confuse openness with exposure. One is a property of the protocol; the other is a security decision at the operational layer. They can move in opposite directions while serving the same system.
Decentralization removes unnecessary permission. Security removes unnecessary access. The hard part is knowing exactly where to draw the line.
$TUT $ENA
I noticed it while digging through Dusk’s node setup. Provisioners need 9000/udp for Kadcast and consensus, but the HTTP API on 8080/tcp doesn’t need to be public. Archive Nodes even bind the API to 127.0.0.1 by default.
Hold up. A permissionless L1 whose own operational guidance explicitly tells you what not to expose.
That isn’t a contradiction. Consensus needs open participation; the machine doesn’t need open exposure. Making both public wouldn’t make Dusk more decentralized it would only increase the attack surface.
What I like is that Dusk doesn’t confuse openness with exposure. One is a property of the protocol; the other is a security decision at the operational layer. They can move in opposite directions while serving the same system.
Decentralization removes unnecessary permission. Security removes unnecessary access. The hard part is knowing exactly where to draw the line.
$TUT $ENA