mirror of
https://github.com/monero-project/monero-site.git
synced 2024-12-15 04:46:35 +02:00
841f7c1efb
- Resolved TODO's for Base32/64-address, Destination, Transports Referencing: - monero-project/kovri#256 - monero-project/monero-site#155
20 lines
828 B
Markdown
20 lines
828 B
Markdown
---
|
|
layout: moneropedia
|
|
entry: "Destination"
|
|
tags: ["kovri"]
|
|
terms: ["Destination", "Destinations"]
|
|
summary: "A in-net address that serves as a final endpoint"
|
|
---
|
|
|
|
### 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).
|
|
|
|
### In-depth Information
|
|
|
|
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-address 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.
|