monero-site/_i18n/pt-br/resources/moneropedia/destination.md
erciccione 7575e6d8e1
Adopt versioning system used in the User Guides to keep track of the translation status of the Moneropedia entries
- Removed the 'untranslated.html' snippet (_includes/untranslated.html). Since now we are using 'disclaimer.html' everywhere
- Replaced the old snippet with the new disclaimer (introduced with #966) in all Moneropedia entries
- Add snippet where it was missing
- Updated instructions in the README
2020-10-04 15:00:43 +02:00

1.1 KiB

tags terms summary
kovri
Destination
Destinations
A in-net address that serves as a final endpoint (either local or remote)

{% include disclaimer.html translated="no" translationOutdated="no" %}

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.