🧑🏿‍🤝‍🧑🏼 👆🏾 📒 Analysis of an attack on an I2P user 🍒 🎅🏽 😯

The history of the I2P network dates back to 2003, and therefore has been overgrown with rumors, speculation and articles about vulnerabilities, some of which are no longer relevant. Before starting the main story, let's outline the solved problems, the mention of which you can still meet today. Don't let them confuse you.

Common misconceptions

Bike number one : I2P does not scale well and with a large increase in nodes, the network will be paralyzed, because reference nodes - floodfiles - will not cope with the flow of information. They say I2P works only while it is not popular, but as soon as the total load grows, the network will fall.

In fact, the number of floodfiles grows along with the network, and all floodfiles are not required to access a certain hidden service. Each hidden service publishes its full address (called a lisset) on the two nearest DHT floods. In turn, DHT coordinates change every day almost randomly.

, , . , , . : . I2P, - . , , .