FAQ
Anyone Protocol
Does the Anyone Network integrate with other networks?
No, Anyone operates on its own privacy network and does not integrate directly with other networks. Though it is always possible to access the Internet through the Anyone network.
Contribution Rewards
What rewards can I expect to earn from my relay?
While the minimum rewards emitted to relay operators is fixed, the amount of tokens you earn will be dependent both on the total number of relays and your own performance (as well as a number of other factors). Read the Tokenomics to find out more.
Why did I not receive my Airdrop rewards?
If you haven't received your redeemed rewards, here are a few steps to troubleshoot the issue:
Check the Redemption Status: Ensure that the redemption process was completed successfully. Remember that ONLY rewards which were redeemed before the weekly deadline will be eligible for the airdrop.
Check you met the eligibility criteria. For non-hardware relays, 100 mainnet ANyONe tokens must be held for EACH relay associated with your wallet in a claimed state. Failure to meet this criterion will result in NONE of your redeemed rewards being eligible for the airdrop. The rewards for every period where this is the case will be forfeited.
Why do some of my relays earn more than others?
The earnings of your relays can vary due to several factors: 1. Consensus Weight: Each relay is assigned a consensus weight based on its measured bandwidth. Higher bandwidth typically means a higher consensus weight, leading to more rewards. 2. Uptime: Relays with consistent uptime are rewarded more. The network has uptime quality tiers, allocating 20% of rewards to relays with high uptime. 3. Relay Type: Different types of relays (e.g., hardware vs. virtual) may have different reward structures. 4. Geolocation and Relay Families: Rewards can be influenced by the relay's location and its association with relay families, which can affect network diversity and load balancing.
What is the purpose of the NFT?
When acquiring on of the first on thousand hardware devices, obtaining an Atornaut NFT is a prerequisite. This NFT isn't merely a digital collectible; it bestows a 100% bonus on relay rewards when staked. It entitles hardware relays to a bonus pool on top of normal relay rewards. Thus, possessing an NFT isn't solely about owning a digital asset; it's about enhancing earnings within the ecosystem and the only way to get one of the first devices.
You can find more information on the NFT on the mint page: https://mint.ator.io
Do I need to lock up $ANYONE to register a relay?
Locking up tokens is not required for operators registering the Anyone Router Hardware.
Note: For more information about the Anyone Router, visit -> https://www.anyone.io/hardware
For any other relays, on the incentivized testnet, you lock up Sepolia Anyone tokens, visit the faucet to acquire some:
To qualify for rewards, 100 mainnet ANyONe tokens must be held for EACH relay associated with your wallet in a claimed state. Failure to meet this criterion will result in none of your redeemed rewards being eligible for the next airdrop. The rewards for every period where this is the case will be forfeited.
Can I use multiple wallet addresses?
No. It is forbidden to use multiple wallets for the relays you operate. All relays must be associated with the same wallet address. If you have multiple hardware relays, all NFTs must also be moved to the same wallet address.
Why is my hardware relay not showing up properly on the dashboard?
The dashboard will only recognize and validate a fingerprint if:
The Anyone Router hardware is updated the latest version
It has an NFT ID and wallet added in the RCP
The wallet associated with it holds this NFT on it.
When the Anyone Relay is validated as hardware it will not require locking 100 ANYONE, and will be designated as 'hardware'.
If the Anyone Relay is installed without the NFT ID, it will show up like non-hardware on the dashboard or not at all.
The logic as of now is that the only way to make sure the hardware is validated properly again, is to:
1. Make sure the Anyone Relay is updated to the latest version.
2. First add the NFT ID to the RCP, apply and reboot. The NFT needs to be in the Ethereum address that is added to the RCP.
3. Lock, claim and then renounce the fingerprint.
4. Wait for a couple of hours and the fingerprint should pop up again, recognized as Hardware.
This is due to the relay registration contract needing to update all the data again. This logic will be changed going forward before main net.
Read this for more information on how to use the rewards dashboard: https://docs.anyone.io/rewards
Why is my relay showing up against the wrong wallet in the dashboard?
If your relay is appearing against the wrong wallet then you must renounce it in order to then claim it against the correct wallet address.
And then go ahead and change the wallet address. See: How do I change the wallet address associated with my relay?
How do I change the wallet address associated with my relay?
First, make sure to update the relay with the correct wallet details.
For Hardware Relays, do this via the RCP. For other relays, update the Contact Info line in the anonrc file.
Once you have done this, you must restart the relay for the changes to stick.
Lastly, renounce the relay on the old wallet address. After a period of approximately 2-4 hours, the relay should appear against the correct wallet in the dashboard, available to lock and/or claim.
Relay Operations
What is the purpose of the relay?
The Anyone Relay is the backbone of the entire privacy network. Whether run via software or our hardware, relays are the nodes that encrypt and forward users' traffic to anonymize it from both external participants and the relay itself. The performance and resilience of the Anyone Network is directly tied to the number of reliability of relays. Anyone can run a relay, contribute to the project and be incentivized for it.
Can I run multiple relays?
Yes, you can run multiple relays on your home network. Note however that multiple relays behind a single IP address may not necessarily result in a predictable increase in rewards, as they may compete with each other. For example, adding a second relay is unlikely to result in a two-fold increase in rewards. If possible, try to run your relays in different locations, as this benefits the network and is likely to result in higher consensus weights being achieved.
When running more than one relay it is required to configure your relays with MyFamily.
Can I run multiple Hardware Relays on my local network?
Yes, you can run multiple relays on your home network. Note however that multiple relays behind a single IP address may not necessarily result in a two-fold increase in rewards, as they may compete with each other. If possible, try to run your relays in different locations, as this benefits the network and is likely to result in higher consensus weights being achieved.
When running more than one relay it is required to configure your relays with MyFamily.
How do I run a relay using my own device on my home network?
Full instructions on how to spin up your own Anyone relay from home are provided in the Anyone Docs here: https://docs.anyone.io/relay
Can I run a relay if I have a dynamic IP address?
Yes, you can run a relay on your home network if you have a dynamic IP address. You may experience short periods of unreachability and subsequent changes in your consensus weight and your relay’s flags when your IP address changes. For most users where changes are relatively infrequent, the impact of this should be minimal. There are some ISPs who will change your IP address on a very frequent basis, sometimes every 2-3 days. It should be noted that whilst this does not prevent you from running a relay, such frequent changes may prevent your relay from being seen as stable by the network, which in turn could have a negative impact on your consensus weight and rewards.
Do all VPS providers allow me to run a relay?
Not all VPS providers allow running relays. Some may have restrictions on bandwidth usage or running certain types of network services. It's important to check the terms of service of your chosen VPS provider to ensure they permit running a relay on their infrastructure. If in doubt, contact their support for clarification.
If you are considering running exit relays - we recommend you explicitly ask them before getting started.
Why do I need to declare my relays as a family?
Declaring your relays as a Relay Family is important for several reasons:
Network Integrity: It helps maintain the integrity of the Anyone Network by ensuring that multiple relays operated by the same entity are recognized as such. This transparency is crucial for preventing sybil attacks, where a single operator might try to unfairly influence the network by running multiple relays.
Reward Allocation: By declaring your relays as a family, you can optimise the allocation of rewards. The network can distribute rewards more fairly based on the collective performance and contribution of your relays.
Load Balancing: It aids in effective load balancing by allowing the network to understand the distribution and control of relays, ensuring that traffic is managed efficiently across the network.
Network Diversity: Encourages diversity in the network by clearly identifying and managing relays under a single operator, which helps in building a more robust and secure network.
By using the MyFamily option, you ensure that your relays are properly recognized and managed within the Anyone Network.
Can I backup and restore my fingerprint and keys?
What to backup:
/var/lib/anon/keys - (the whole folder)
/etc/anon/anonrc - (your config file)
You can use something like WinSCP to connect to your relay via SSH (on Windows) and copy the files off.
How to restore your backed-up keys: Install the relay as per the normal installation instructions. As soon as the install is finished, stop the relay:
systemctl stop anon
Connect to the relay via WinSCP or other, and replace everything inside the keys folder and the config file:
/var/lib/anon/keys - (the whole folder)
/etc/anon/anonrc - (your config file)
Now, to ensure you haven’t broken any ownership permissions by moving files etc, run:
chown -R debian-anon:debian-anon /var/lib/anon
Then startup your relay again:
systemctl start anon
Source: Discord Community Post
How do I update my Hardware Relay?
You can find instructions on how to update your Hardware Relay, along with the latest update files here in the Anyone Docs
How do I edit the anonrc configuration file in Debian?
You can use text editing tools like 'nano'.
sudo apt-get install nano
sudo nano /etc/anon/anonrc
Save and exit:
Press 'Ctrl+X' to exit.
Press 'y' and hit ENTER to confirm the changes.
How to install nyx for monitoring in Debian?
sudo apt-get install nyx --yes
To run Nyx, type: sudo nyx
Note: see Confirm ORPort Reachability for more information on monitoring reachability.
How can I check that my relay is online?
For hardware relays
1. Access the Relay Control Panel (RCP):
Connect to the same network as your relay.
Open a web browser and go to `http://relayup.local`.
Log in using the credentials: - Username:
relayup- Password:admin2. Check the 'Home' Page:Navigate to the 'Network' section.
Look for the "Reachability" status indicated with "OR Port Reachable".
If the status is 'OK' and 'Reachable', your relay is online and functioning properly. 3. Light Indicators:
Ensure all lights on the relay are pulsing in the Anon Blue colour, indicating a successful setup. 4. Logs:
Check the logs in the control panel for more details on the process. If everything checks out, congratulations! Your relay is online and ready to provide bandwidth to the Anyone Network. If you encounter any issues, feel free to reach out for further assistance!
Virtual relays
Install NYX and check for a message that your relay has confirmed reachability. You should also see flags start to appear if the relay is online and reachable.
Use the Anyone API to check your relay’s status by adding your fingerprint to the end of the following URL: https://api.ec.anyone.tech/relays/
Check the rewards dashboard and look for a green dot confirming the relay was online at the last check.
Does restarting my relay affect its recorded uptime?
Restarting your relay for short periods, like when installing updates, generally won't significantly impact your rewards. The Anyone Protocol rewards system considers uptime quality tiers, which focus on consistent uptime over longer periods. Brief downtimes for maintenance are expected and typically won't affect your relay's standing in these tiers. Just ensure your relay is back online promptly to maintain its performance and uptime record.
Why is my VPS relay not reachable?
Check if the datacenter's firewall is blocking the required ports. You may need to configure the firewall to allow traffic through the specific ports used by the relay.
Why is my relay not reachable?
If your relay is not reachable, there could be several reasons. Here are some common issues and solutions:
Firewall and Network Configurations: Ensure that your firewall settings allow traffic through the necessary ports. Check the Firewall and Network Configurations section for detailed instructions.
Router Port Forwarding: Your router might not be forwarding the required ports to your relay. Make sure port forwarding is correctly set up. Refer to the Router Port Forwarding section.
CGNAT Issues: If you're behind a Carrier-Grade NAT (CGNAT), it might block incoming connections. You can diagnose this issue in the Diagnosing CGNAT and Public IPv4 section.
ORPort Reachability: Confirm that your ORPort is reachable from the outside. This is crucial for the relay to function properly. Check the Confirm ORPort Reachability section.
Is there a workaround for CGNAT?
If your ISP uses CGNAT, currently there is no workaround that will allow you to run a relay on your home network. You cannot use a VPN or WireGuard as a workaround.
Request a Public IP from Your ISP: Contact your ISP and request a dynamic or static public IP address. Some ISPs may charge for this service. Alternatively, consider running a relay on a VPS in a data center.
Relay Performance and Troubleshooting
Why is my relay dropping its flags?
When your relay is dropping its flags, it usually indicates an issue with its performance or configuration. Here are some common reasons and solutions:
Low Bandwidth or Uptime: Ensure your relay has a stable internet connection and meets the minimum bandwidth requirements. Consistent uptime is crucial for maintaining flags.
Configuration Issues: Double-check your relay's configuration settings. Incorrect settings can lead to flag drops. Make sure your relay is configured correctly according to the latest guidelines.
Network Changes: If your ISP changes your IP address frequently, it might affect your relay's stability. Consider using a static IP.
Resource Limitations: Ensure your device has enough resources (CPU, RAM) to handle the relay operations. Overloaded systems can cause performance issues.
Software Updates: Make sure your Anon software is up-to-date. Updates often include bug fixes and performance improvements.
Relay Reputation: If your relay has been flagged for suspicious activity or poor performance in the past, it might affect its current status. Ensure your relay complies with all network policies.
What do the relay flags mean?
In the Anyone Network, relays can be assigned various flags that indicate their roles or characteristics. Here are some common relay flags and their meanings:
Guard: This flag is given to relays that are suitable for being the first hop in a circuit. They have high uptime and reliability.
Exit: Relays with this flag allow traffic to exit the network to the internet. They follow specific exit policies.
Middle: These relays are used for the middle hops in a circuit. They don't have specific entry or exit roles.
Stable: Relays with this flag have been consistently online and reliable over a long period.
Fast: This flag is assigned to relays with high bandwidth, making them suitable for handling large amounts of traffic.
HSDir: These relays can store and serve hidden service descriptors, making them part of the hidden services infrastructure.
V2Dir: Relays with this flag can serve directory information to clients.
Each flag helps the network efficiently route traffic and maintain security and performance.
Why doesn’t my hardware relay pulse blue?
f your relay isn't pulsing in the Anon Blue colour, it might indicate an issue with the setup. Here are a few steps to troubleshoot:
Check Reachability: Ensure the "Reachability" status on the 'Home' page under the 'Network' section is 'OK'. If not, verify your port forwarding settings and ensure your router has a public IPv4 address and is not behind CGNAT. See https://docs.anyone.io/relay/troubleshooting-common-issues for further details.
Review Logs: Check the logs in the Relay Control Panel for any error messages or warnings that might indicate what's wrong.
Network Configuration: Make sure your network settings are correctly configured, including any necessary port forwarding rules. https://docs.anyone.io/relay/troubleshooting-common-issues/confirm-orport-reachability
Update Software: Ensure your Anon software is updated to the latest version. Follow the update instructions carefully, especially regarding USB drive usage. https://docs.anyone.io/hardware/updates
Restart the Relay: Sometimes, a simple restart can resolve connectivity issues. Turn the relay off, save changes, reboot, then turn it on again, save changes, and reboot.
If these steps don't resolve the issue, feel free to join the Anyone Discord Community or raise a support ticket for further assistance!
How long does it take for my consensus weight to increase?
The increase in your consensus weight depends on several factors, including your relay's uptime and performance. Generally, it can take a few days to a couple of weeks for your relay to be recognized and for its consensus weight to adjust accordingly. Following this, the score may continue to increase for a period of weeks and months. Consistent uptime and maintaining good performance metrics are key to improving your consensus weight.
Why is my consensus weight so low?
Your consensus weight might be low due to several factors:
Bandwidth: Ensure your relay is providing sufficient bandwidth. The network measures and adjusts your consensus weight based on your relay's bandwidth performance.
Uptime: Consistent uptime is crucial. Relays with higher uptime are rewarded with better consensus weights.
Geolocation and Diversity: The network benefits from diverse relay locations. If your relay is in an area with many others, it might affect your weight.
Network Conditions: Temporary network conditions or changes in the network's overall load can also impact your consensus weight.
Remember, your bandwidth will show as zero when you first start your relay. Have patience over the first few days once you have confirmed the relay is online and reachable. You should see it increase after a couple of days have passed.
Why is my observed bandwidth low when my relay has a fast connection?
Firstly it is important that the speed of your relay is determined by the network, not simply the speed of your line. There could be several reasons why your observed bandwidth is low despite having a fast connection.
It is important to note that the speed displayed in the rewards dashboard uses MiB/s (Mebibytes per second) not megabits per second. A reported Observed Bandwidth of 10 MiB/s is equivalent to approximately 84 megabits per second.
1. Configuration Settings: Ensure that your RelayBandwidthRate and RelayBandwidthBurst settings are configured correctly. These settings control the maximum bandwidth your relay can use. 2. Network Congestion: Other devices on your network might be using bandwidth, causing congestion. Check if other applications or devices are consuming significant bandwidth. 5. Relay Uptime: Consistent uptime is crucial. If your relay frequently disconnects, it might not be fully utilised by the network. 6. Network Diversity: The Anyone Network benefits from diverse relay locations. If there are many relays in your area, traffic might be distributed among them, affecting your observed bandwidth. 7. Consensus Weight: Your relay's consensus weight might be low. This score affects how much traffic your relay receives. It can be influenced by factors like uptime and bandwidth measurements. 8. Hardware Limitations: Ensure your hardware can handle the relay's demands. While the Anyone Relay doesn't require high CPU/GPU power, it still needs reliable hardware.
9. Up-speed is key. Traffic on the Anyone network is typically synchronous i.e., your relay will send and receive roughly the same volume of data. The up-speed of your internet service is therefore likely to determine the observed bandwidth your relay is able to achieve, not your down-speed.
Why does my relay say ‘client not installed’?
If your relay is indicating that the client is not installed, it could be due to a few reasons. Here are some steps to troubleshoot: 1. Check Installation: Ensure that the Anon Client is properly installed on your device. You can verify this by checking if the `bin/anon` binary is present. If the client is not installed, try to trigger an install in the RCP. Go to Relay settings and turn the Relay OFF, save changes, reboot, then turn it ON again, save changes, and reboot. Recheck the status in the Relay Control Panel. If the problem persists, raise a support ticket for further help.
2. Network Connection: Make sure your relay is connected to the internet, either via Ethernet or WiFi. A lack of connection might prevent the client from being installed. 3. Software Update: Ensure your relay is running the latest software version. You can update it by downloading the latest version from the official site and following the update instructions. 4. Logs: Check the logs in the control panel for any error messages that might give more insight into the issue. If these steps don't resolve the issue, feel free to reach out to the Anyone Discord Community for further assistance, or raise a support ticket.
Last updated
