Haven Protocol
  • Haven Protocol
  • 💻GUI
    • Overview
      • Restore Account
      • Create Account
      • Login
      • Transfer
      • Receive
      • Offshore Exchange
      • Onshore Exchange
      • Nodes
      • Settings
      • Troubleshooting
      • Signature
      • Smart Mining
  • CLI
    • Overview
      • Installation
      • Create Account
      • Restore Account
      • Login
      • Transfer
      • Receive
      • Offshore Exchange
      • Onshore Exchange
      • Nodes
      • Troubleshooting
      • Settings
  • RPC
    • Overview
      • Transfer
      • Transfer Split
      • Offshore
      • Onshore
      • Offshore Transfer
      • Offshore Sweep All
      • Get Offshore Balance
      • Get Transfers
  • FAQ
    • Project Timeline
    • The Protocol
      • What is Haven?
        • What can Haven be used for?
        • How does it work?
          • Transactions
            • What are the transaction fees?
            • How do the transactions work?
          • Haven Assets
            • Can I see the supply of xAssets?
            • What is the supply of XHV and xAssets?
            • How many xAssets will there be?
      • Whats an Oracle?
      • Is Haven private?
        • Why does Haven need privacy?
  • Glossary
  • Overview
    • Airgap
    • Address
    • Address Book
    • Account
    • Atomic Units
    • Block
    • Blockchain
    • Bootstrap Node
    • Bulletproofs
    • Canonically Unique Host
    • Change
    • Clearnet
    • Coinbase
    • Consensus
    • Cryptocurrency
    • Daemon
    • Denomination
    • Destination
    • Encryption
    • Fluffy Blocks
    • Fungibility
    • Kovri
    • Locally Unique Host
    • Mining
    • Mnemonic Seed
    • Node
    • Open Alias
    • Paper Wallet
    • Payment ID's
    • Pedersen Commitments
    • Pruning
    • Random X
    • Remote Node
    • Ring Size
    • RingCT
    • Ring Signatures
    • Scalability
    • Spend Key
    • Stealth Addresses
    • Tail Emission
    • Transactions
    • Unlock Time
    • View Key
    • Wallet
Powered by GitBook
On this page

Was this helpful?

  1. Overview

Destination

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 Haven 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.

PreviousDenominationNextEncryption

Last updated 4 years ago

Was this helpful?