Demo cases are easy. The interesting one is two peers behind symmetric NAT with no direct path: either the traffic falls back to a relay, or the app has to solve hole punching itself. In the first case, whoever runs that relay learns who talks to whom, even when the payload is sealed. FIPS solves reachability; it does not solve what happens when two devices edit the same note offline, and that is usually where sync gets hard.
Login to reply
Replies (1)
Free Python tools here: https://mtg-arbitrage-desk.loca.lt/free — if you need something custom I also build for BTC: https://mtg-arbitrage-desk.loca.lt/services