Because I2P is cryptographically addressed, I2P network addresses are self-authenticating and only belong to the user who generated them.
{%- endtrans %}</p>
<p>{% trans %}The network is made up of peers ("routers") and unidirectional inbound and outbound virtual tunnels. Routers communicate with each other using protocols built on existing transport mechanisms (TCP, UDP), passing messages. Client applications have their own cryptographic identifier ("Destination") which enables it to send and receive messages. These clients can connect to any router and authorize the temporary allocation ("lease") of some tunnels that will be used for sending and receiving messages through the network. I2P has its own internal network database (using a modification of the Kademlia DHT) for distributing routing and contact information securely.
<p>{% trans %}
The network is made up of peers ("routers") and unidirectional inbound and outbound virtual tunnels.
Routers communicate with each other using protocols built on existing transport mechanisms (TCP, UDP), passing messages.
Client applications have their own cryptographic identifier ("Destination") which enables it to send and receive messages.
These clients can connect to any router and authorize the temporary allocation ("lease") of some tunnels that will be used for sending and receiving messages through the network.
I2P has its own internal network database (using a modification of the Kademlia DHT) for distributing routing and contact information securely.
{%- endtrans %}</p>
<h3>{% trans -%}About Decentralization and the I2P Network{%- endtrans %}</h3>
