mirror of
https://github.com/monero-project/monero-site.git
synced 2024-12-25 21:19:49 +00:00
4c1e8dd858
+ correction on Italian Account + Removed leftover miners.md (replaced by mining.md) + Removed Dust and update Copyright + Code improvement to avoid reading the config file and to use the builtin jekyll config variable passed in the content + Ammount.md:25/26 glitch "\@transaction-privacy" corrected. PL to be checked twice. + Italian ammount.md moneropedia links corrected (terms added to destination entries, unnecessary markdown links removed) + Polish corrections + extend ruby \word-boundary in regex to match `-based` `-like` `-form` + Updated readme according to the new way to add or translate a moneropedia entry + fix mining with CryptoNight variant + rebased to include AR + chery picked #820 to avoid conflicts
28 lines
1.4 KiB
Markdown
28 lines
1.4 KiB
Markdown
---
|
|
entry: "I2NP"
|
|
tags: ["kovri"]
|
|
terms: ["I2NP"]
|
|
summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network"
|
|
---
|
|
|
|
{% include untranslated.html %}
|
|
### The Basics
|
|
|
|
From @Java-I2P:
|
|
|
|
>
|
|
@I2NP manages the routing and mixing of messages between routers, as well as the selection of what transports to use when communicating with a peer for which there are multiple common transports supported
|
|
|
|
### In-depth information
|
|
|
|
From @Java-I2P:
|
|
|
|
>
|
|
@I2NP (@I2P Network Protocol) @messages can be used for one-hop, router-to-router, point-to-point @messages. By @encrypting and wrapping @messages in other @messages, they can be sent in a secure way through multiple hops to the ultimate @destination. @I2NP does not specify nor require any particular @transport layer but does require at least one @transport in use.
|
|
|
|
>
|
|
Whenever a @destination wants to send a message to to another @destination, it provides its local router with both the @destination structure and the raw bytes of the message to be sent. The router then determines where to send it, delivers it through outbound @tunnels, instructing the end point to pass it along to the appropriate inbound @tunnel, where it is passed along again to that @tunnel's end point and made available to the target for reception.
|
|
|
|
### Notes
|
|
|
|
Read more about the @I2NP [protocol](https://geti2p.net/en/docs/protocol/i2np) and [specification](https://geti2p.net/spec/i2np).
|