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
1.1 KiB
| entry | tags | terms | summary | |||
|---|---|---|---|---|---|---|
| Destination |
|
|
A in-net address that serves as a final endpoint (either local or remote) |
{% include untranslated.html %}
The Basics
A @destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or Monero node). This can also include a local destination of which other peers need to connect to in order to make contact for communication (similar to how, in @clearnet, your IP address is given to a website when you connect so it knows where to send the information back to).
In-depth Information
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-addresses or a .i2p hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys:
256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation
Note: certificates are not used now but, if they were, the keys would be longer.