paritytech / mixnet Goto Github PK

Node key is currently set at construction and can't be changed without destroying the Mixnet object. Even though this implementation does not enforce a specific topology, it should be possible to set a new key for the existing session. This will allow the keys to be short lived for better forward secrecy.

Documentation should enable anyone to write an alternative implementation of the protocol. It should include

• Sphinx packet format.
• Wire protocol, fragment handling.
• Peer expectations w.r.t packet delays, cover traffic generation, route selection, etc.

Hi all! Thank you for the great work in this repo.

I would like to ask if this mixnet implementation is based on libp2p, as written in the repo description. It seems that the repo doesn't use libp2p as a dependency and implements its own interfaces. If so, can I ask about the future integration plan with libp2p?

Calculate basic traffic rate based on configuration and disconnect peers that go over this rate by too much.

Track loop cover packets and use their return times to gauge the health of the mixnet. We expect all loop cover packets to return, but we also expect them to return at a certain time (based on the deterministic forwarding delays).