Skip to main content
Version: v5.0.0

Frequently Asked Questions

How to find the external IP address?​

  1. Open the terminal

  2. Run the command

    Copy, paste and execute the following command:

    curl ifconfig.me

  3. Note your public IP address

    Note your public IP address from the output

What are the requirements for an IP address to run a HOPRd node?​

If you are planning to run HOPRd node(s) under NAT (Network Address Translation), such as running node(s) on Dappnode, Avado devices, or home/office computers/servers. Please follow bellow the guide to determine if your IP address meets the requirements to run a HOPRd node.

Your node's IP address is crucial for its performance. If it is misconfigured or does not meet the necessary requirements, your node will not be reachable by most peers, including Cover Traffic nodes, and you may not receive rewards.

  1. Check if your external IP is a public IP

    For HOPRd nodes to communicate with each other on the HOPR network, every node must have a public IP address. The only reliable way to check this is to contact your Internet Service Provider (ISP) and ask directly.

  2. Check if your public IP is static or dynamic

    Why is this important?

    • If your public IP is dynamic, it changes over time, causing your node to become unreachable.
    • If your IP changes, you must manually update your node's configuration with the new public IP.
    • A static IP is recommended to avoid frequent maintenance issues.

    How to check if your public IP is static or dynamic:

    • The only reliable way to check this is to contact your Internet Service Provider (ISP) and ask directly. If it is dynamic, ask if they offer a static IP option.

    • Alternative method (Less Reliable):

      • Find your external IP by going to https://whatismyipaddress.com and note the IPv4 address displayed.
      • Turn off your router/modem for 5-10 minutes. Then turn it back on and reconnect.
      • Return to https://whatismyipaddress.com and check the IPv4 address again.
        • If the IP address has changed, your IP is dynamic.
        • If the IP address remains the same, your IP might be static (although some ISPs assign "sticky" dynamic IPs that rarely change).

  3. Actions based on your external IP type

    Select your external IP type:

    If your external IP address is not public, other nodes may not be able to connect to your node, and it may not earn rewards. HOPRd v5.0.0 no longer has the HOPRD_NAT setting from earlier versions, so we recommend running your node with a public IP address.

    One option is to rent a low-cost cloud VPS. More info here.

How to use dynamic DNS?​

To run the HOPRd node, you need a static or public IP so other peers can reach you on the network. However, many ISPs only provide dynamic IPs. In this case, you can use Dynamic DNS (DDNS), which continually checks for IP changes and automatically updates the hostname with the latest IP. This allows you to use a hostname instead of an IP address. Here's how to set it up:

Most router brands support dynamic DNS. You can use the router brand's credentials or third-party services like No-IP.

Brands supporting Dynamic DNS:

After setting up DDNS, you'll have a hostname (e.g., hostname.hopto.org) to use with a port on the HOPR package instead of an IP address.

Example: hostname.hopto.org:9091

How do I create a secure password for the secret token and database password?​

There are no specific requirements for creating a database password or secret token, but both should be treated like passwords. We recommend using the Bitwarden Password Generator to create a strong token.

note

To evaluate the strength of your password, you can use the Bitwarden Password Strength Testing Tool.

Do I need a minimum stake to run a node?​

No. On the Piz Palu network, your stake doesn't affect your rewards. Your node needs:

  • A Safe and node module, created with hopli as described in the setup guide for your platform, for example Docker.
  • At least 1 wxHOPR in your Safe, which pays the fee for announcing your node on the network.
  • At least 0.01 xDai on your node address.
  • At least 5 open outgoing payment channels with at least 100 wxHOPR each to be eligible for Cover Traffic. Your node funds them from your Safe, so keep at least 750 wxHOPR in your Safe, plus extra for top-ups. You also need to change your channel funding values, as described in Fund your channels for Cover Traffic.

You can find where to get wxHOPR and xDai here.

What is Cover Traffic, and what is its purpose?​

Cover Traffic is traffic that HOPR sends through the network to pay node runners and to keep the network busy, which protects the privacy of real users. Cover Traffic nodes send short bursts of traffic through every eligible node, and each node earns tickets for the packets it relays, the same as for real traffic, for example from Gnosis VPN.

For background, see Cover Traffic on HOPR Piz Palü.

How many Cover Traffic nodes are there?​

There are five Cover Traffic nodes on Piz Palu:

0x51624c828c175cc81d6a7dd22a9a30d68c6a1ae0
0xa64109ed980c902ac554662b9d569a6a3f71e7a7
0x02d7d9ca7788e674676f809ac984cbf59e4b6099
0x50eac8e328847e5389aabb267398386db7225644
0x991a376c646274d74adb3b25ccc292a775f352f1

When is my node eligible for Cover Traffic, and where are the rewards sent?​

Your node is eligible when:

  1. A Cover Traffic node can reach it. Check this with How to check if my node is working correctly?
  2. It has at least 5 open outgoing payment channels with at least 100 wxHOPR each. Your stake, Safe balance and location don't count.

Your node earns a ticket for every packet it relays. When a ticket wins, your node redeems it automatically and the reward goes to your Safe. If your node has an open outgoing payment channel to one of the Cover Traffic nodes, the reward goes to that channel's balance instead, and moves to your Safe when you close the channel. To check that your node relays traffic and earns tickets, see How can I verify if Cover Traffic is being relayed through my node(s)?

How often does Cover Traffic reach my node?​

Each eligible node gets a burst of about 10 seconds roughly every 20 minutes, averaged across the five Cover Traffic nodes. If your node can't be reached when its turn comes, it's skipped for that round.

How much can I earn?​

There is no APR and no fixed reward. Your node earns tickets for the packets it actually relays, from both Cover Traffic and real users. Whether a ticket wins depends on the ticket winning probability, and its value depends on the ticket price; both are still being tuned. A reachable node with good hardware, a fast connection and funded channels relays more traffic and earns more.

Is there a lock-up period for my wxHOPR?​

No. You can withdraw wxHOPR from your Safe at any time, as described in Withdraw wxHOPR from your Safe. wxHOPR in your payment channels returns to your Safe when the channels close. If your channels drop below 5 open channels with 100 wxHOPR each, your node stops being eligible for Cover Traffic.

How to check your Safe allowance and increase it?​

Your node funds its payment channels with wxHOPR from your Safe, but only up to the amount your Safe has approved for the HOPR channels contract. This approved amount is your Safe allowance. hopli set it when you created your Safe, with the --allowance value from the setup guide (15,000 wxHOPR in the Docker guide).

Each time your node opens or tops up a channel, the allowance goes down by that amount. wxHOPR that returns to your Safe when a channel closes doesn't raise it again. When the allowance runs out, your node can't open or top up channels, even if your Safe still holds wxHOPR, and it can stop being eligible for Cover Traffic.

Check your allowance​

  1. Open the Swagger UI and authorize

    Follow steps 1 to 3 of How to check if my node is working correctly?

  2. Read your allowance

    Run GET …/account/balances and look at safeHoprAllowance. For example:

    "safeHoprAllowance": "15000 wxHOPR"

    safeHopr in the same response is the wxHOPR in your Safe. Your node needs both: wxHOPR in your Safe, and an allowance that covers the wxHOPR it still has to put into channels. If the allowance is lower than that, increase it.

Increase your allowance​

You change the allowance with a transaction from your Safe that calls approve on the wxHOPR token contract. The value you enter replaces your current allowance; it isn't added to it. Enter the total allowance you want.

You need these values:

WhatValue
wxHOPR token contract0xD4fdec44DB9D44B8f2b6d529620f9C0C7066A2c1 (see HOPR tokens on different chains)
Spender: the HOPR channels contract on Piz Palu0x75Ce59332721E3aE3064cb9652BCE35FFCE3f8E6
New allowance, in weiThe wxHOPR amount followed by 18 zeros. We recommend 100,000 wxHOPR: 100000000000000000000000
caution

Check the spender address carefully. approve lets the spender take wxHOPR from your Safe, up to the allowance.

  1. Open your Safe

    Open your Safe in Safe{Wallet} with a wallet that is a signer of your Safe, as described in Open your Safe.

  2. Open Transaction Builder

    Click New transaction, then Transaction Builder. If Safe{Wallet} shows a disclaimer about third-party apps, read it, select the checkbox to agree, then click Continue.

  3. Enter the wxHOPR token contract

    In Enter Address or ENS Name, paste the wxHOPR token contract address. Transaction Builder loads the contract's functions.

  4. Fill in the approve call

    • In Contract Method Selector, select approve.
    • In spender (address), paste the HOPR channels contract address.
    • In value (uint256), enter the new allowance in wei, for example 100000000000000000000000.

  5. Create the batch

    Click Add new transaction, then Create Batch.

  6. Send the batch

    Check the transaction, click Send Batch, and sign and execute it with your wallet. If your Safe needs more than one confirmation, the other signers confirm the transaction in Safe{Wallet} before it can be executed.

  7. Check the new allowance

    When the transaction is confirmed, run GET …/account/balances again. safeHoprAllowance shows the new value, for example 100000 wxHOPR.

Can I earn rewards without operating a node?​

No. Rewards come only from relaying traffic, so you need a running node with funded payment channels.

From a cost/efficiency perspective, which option should I choose: running a node on physical hardware or using a VPS?​

Both work. What matters most is that your node can handle Cover Traffic bursts: a node that can't keep up drops packets and loses the tickets for them.

The minimum for a relay node is 4 CPU cores, 4 GB of RAM and 5 GB of disk, with an uplink that handles 10 Mbit/s in both directions. Give your node some headroom above this.

Physical hardware​

Pros: cost-effective over time, with no monthly fees, and usually faster CPU cores than a VPS.

Cons: you have to monitor it for internet and power outages yourself.

VPS​

Pros: high uptime; most providers offer 99.9% uptime and handle power and network issues for you.

Cons: monthly costs, and VPS cores are usually slower than your own hardware, so choose a plan with headroom.

Can I run multiple nodes?​

Yes. Each node needs its own identity, folder and ports, and must be added to your Safe. Each node also needs its own 5 funded outgoing channels to be eligible for Cover Traffic. See Running multiple nodes.

Table of Contents