looked up [chaum 79] on mixnets https://chaum.com/wp-content/uploads/2022/09/UNTRACEABLE-ELECTRONIC-MAIL-RETURN-ADDRESSES-AND-DIGITAL-PSEUDONYMS-tech-report.pdf and hell yeah motherfucker they even mention ddos resistance by a different name:
Incrimination of a particular mix that failed to properly process an item also remains possible.
ratcheting keys (and ratcheting identifiers) is how i would address the issue with reusing addresses. i would also make logical addresses possible to delegate. i would also obv segment messages into fixed-size datagrams to be reconstituted by the recipient, and instead of recipient-driven replay attacks like TCP requires, the network would pass along confirmation of each datagram as it arrives at each intermediate destination
@hipsterelectron How would this work? The confirmation is itself a datagram, so… would there be confirmation of each confirmation?
@wizzwizz4 confirmations constitute a control message (other control messages include setting up a virtual circuit in the first place as a double ratchet chain). the term "datagram" is used to refer to an independently routable chunk of user data from source to sink. the protocol is not recursive in the sense that datagrams (user data) are at this point distinguished from control messages.
@wizzwizz4 the assumptions here are that ("like tor") we want to make user communications indifferentiable to a global passive adversary. this is accomplished in three main ways:
(1) source routing i.e. sending datagrams through a sequence of pre-negotiated channels (this essentially does onion routing)
(2) splitting messages into a sequence of datagrams to reconstitute at the destination (this can be thought of as like bittorrent)
(3) message mixing between nodes that achieves a constant bandwidth/bit rate between each pair of neighbors at all times (the mixing behavior batches messages between neighbors and encrypts each batch in a ratcheting channel--this may be double ratchet, but it may be another racheting cryptosystem since double ratchet is meant to be asynchronous and makes other assumptions we don't need for this)
this is doable with a double ratchet message chain at each phase. each batch message dispatched between nodes would be encrypted separately, and padded to mitigate traffic analysis (possibly not padded at end depending upon susceptibility to length extension, or perhaps the padding would be randomized instead of fixed)
Install bonfire.cafe
Get the full app experience
