Hi, check this comment. It seems like it will be able to work without the concerns that Mullvad has had. I suppose in theory the bad actors can use a synchronized scheme like this as well - if they realize that, ProtonVPN may still end up with the same amount of problems and need to shut it down.

The main issue with I have with how the current i2p implementation works is that it essentially creates a walled garden in the torrent network, as i2p users can't seed out to non-i2p users, they can only leech from them. I feel like that would needlessly split the network, which relies on having as many people as possible seeding. Frankly I don't know if its even possible to work around that, but I'll need to see how it plays out. Also, there needs to be at least one person with a port forwarded on any given torrent. utp only peers cannot seed independently, from my understanding.

I think i2p or something similar where people can run a router and provide bandwidth to the network and help hide what other users are downloading (which is how i2p works but its not super fast sadly)

Hi, I looked into this and from what I can gather, ProtonVPN gives out temporary ports for port forwarding. I'm not 100% how long these ports are leased for, but as long as you run a script like this to move your torrent client's port around to match ProtonVPN's, I can see how this would work. It's not perfect, but it's workable. I wonder if Mullvad will implement something like this to achieve parity.