I have a hundred running on my desktop, which is on most of the time. Rewards have dropped to zero over the past 4 days. Possibly something’s gone wrong with my setup but I agree that most people won’t bother to run nodes on their spare capacity (the original USP of the network) if they don’t see much in the way of reward.
4 Likes
There are close to zero uploads at the moment so it will improve won’t it?
2 Likes
In which direction? I bet that the moment more tokens can be mined we will see more millions of nodes from the big players.
Check out the Dev Forum
2 Likes
That’s what we want isn’t it? I know more nodes means less rewards for us but as long as there is some competition between the whales we will have a successful network won’t we?
3 Likes
when uploads start flying and we get some usage going the rewards should start to flow more evenly and everyone should get something.
2 Likes
The upload process is still not running smoothly, and it seems that the team considers the increase in nodes under such circumstances as a kind of robustness test. Since it is a self-replicating network and nodes do not receive fees when someone downloads data, large-scale mining on the cloud will soon become inefficient due to traffic costs. The fundamental assumption of this project is that node operation cannot be centralized due to bandwidth costs. And that assumption remains unchanged.
1 Like
It depends on how you define success, for you and me as token holders this is definitely success…
This is only true for a small part of the planet. You and I may be running tens of thousands of nodes on unlimited fiber lines, but most of the planet doesn’t have that…
Check out the Dev Forum
2 Likes
20 nodes, port forward, fixed IP
4 rewards in 48 hrs
Looking at logs, quite a bit of relay work going on…
5 Likes
What strings are you grepping for to reach that conclusion?
I KNOW the devs are busy but it would be great if one of them could take a little time to produce a short list of strings we should be grepping for and the likely cause if we see a preponderence of these strings.
And how many constitutes a “preponderence”
2 Likes
My simple definition would be that anyone can easily Upload/download, anyone is able to earn enough to pay for their own data and when we can , have no blockchain payments. How would you define it?
1 Like
The bandwitdh is considered a national strategic asset and is managed under the concept that the government supplies it to individuals at a low cost. Therefore, the number of broadband connections allowed per person is limited. I am already using the maximum allocation and cannot increase it further.
If you want to use it without limitations, you need to apply for a business-grade 1G unlimited service, which costs around $1,000 per month. This means that small-scale individual users have an advantage.
Soon, as uploads become more efficient and downloads increase, large-scale nodes running on the cloud will disappear due to cost issues. Don’t worry.
Autonomi is designed in a way that prevents node operators from accumulating massive profits through centralization, like Bitcoin mining. It is much more beneficial to build something on top of this system.
No one can earn huge money from Autonomi node operation. It is art of this great network. Because it is truly decentralized. Isn’t it wounderful?
5 Likes
Can I get brief detail how this Tetris running on my chrome browser directly ? It is really interesting.
Hello Autonomi to the world non-dev user 
2 Likes
I’m no grepper, I just look at the nodes that have the most connections and scroll through the log.
Cant remember the exact text, but it’s clear that relay work is being done.
I look forward to the ANT commissions coming my way in future.
Judging by Discord, there be no shortage of dependent nodes paying the tax.
1 Like
It’s a good point. Right now we have
- Directly connected
- port forward
- Behind full cone nat
- upnp
Then the remainder are relay clients. They relay through others. We are making moves to limit the relay clients to 25% of payments and the other 75% to the relay node itself. That’s to find a middle ground of encouraging people to port forward if they can.
That may leave behind a small % of folks. They can get a von perhaps, but even that’s a cost and hit or miss. So we have a road to get to have every node from home working.
However clients are fine, they don’t need any of that right now. They just always connect.
12 Likes
So for fun I got the easy how to port forward in detail from chatgpt, which seems to know Autonomi CLI, please correct if the AI is wrong. Cheers
To successfully set up port forwarding for 100 antnodes on the Autonomi network, you need to configure your router, operating system firewall, and antctl CLI correctly. Here’s how to do each step in detail:
- Configure Internet Router for UDP Port Forwarding (50001-50100)
Your router is the first barrier between the internet and your local devices. You need to forward UDP ports 50001-50100 to the machine(s) running the antnodes.
Steps to Set Up Port Forwarding in Router
1. Log into your router
• Open a browser and go to your router’s admin page (typically 192.168.1.1 or 192.168.0.1).
• Log in with your admin credentials.
2. Locate Port Forwarding Settings
• This is often found under Advanced Settings → NAT → Port Forwarding.
3. Set Up the UDP Port Range for Antnodes
• Service Name: AutonomiAntnodes
• Protocol: UDP
• External Port Range: 50001-50100
• Internal Port Range: 50001-50100
• Internal IP Address: The LAN IP of the machine running the antnodes (e.g., 192.168.1.100).
• Enable the rule and save changes.
4. Restart Router if Necessary
• Some routers require a reboot to apply changes.
Testing Port Forwarding
• Use an online tool like canyouseeme.org or nc -u -l 50001 to test if ports are open.
• Alternatively, use nmap from another machine:
nmap -sU -p 50001-50100
- Configure Operating System Firewall (Windows/Linux/MacOS)
Each antnode must be allowed through the local OS firewall for UDP traffic on ports 50001-50100.
Windows Firewall Rules (PowerShell)
Run these commands as Administrator:
Allow inbound traffic for antnode on UDP ports 50001-50100
New-NetFirewallRule -DisplayName “AutonomiAntnode Inbound” -Direction Inbound -Protocol UDP -LocalPort 50001-50100 -Action Allow
Allow outbound traffic for antnode on UDP ports 50001-50100
New-NetFirewallRule -DisplayName “AutonomiAntnode Outbound” -Direction Outbound -Protocol UDP -LocalPort 50001-50100 -Action Allow
To check if the rules exist:
Get-NetFirewallRule | Where-Object { $_.DisplayName -like “AutonomiAntnode” }
Linux Firewall Rules (UFW and iptables)
For UFW (Uncomplicated Firewall):
sudo ufw allow 50001:50100/udp comment “Allow Autonomi Antnodes UDP”
sudo ufw reload
For iptables:
sudo iptables -A INPUT -p udp --dport 50001:50100 -j ACCEPT
sudo iptables -A OUTPUT -p udp --dport 50001:50100 -j ACCEPT
sudo iptables-save | sudo tee /etc/iptables/rules.v4
To verify:
sudo iptables -L -v -n | grep 50001
MacOS Firewall Rules
For pfctl (Packet Filter):
1. Open the firewall config:
sudo nano /etc/pf.conf
2. Add these rules:
pass in proto udp from any to any port 50001:50100
pass out proto udp from any to any port 50001:50100
3. Apply changes:
sudo pfctl -f /etc/pf.conf
sudo pfctl -e
- Configure antctl CLI for UDP Ports 50001-50100
antctl is the command-line interface for Autonomi, where you specify the UDP ports that antnodes should use.
Steps
1. Open a terminal on the machine running the antnodes.
2. Enter the following command to register the UDP ports:
antctl set-port --udp 50001-50100
3. Confirm the settings:
antctl get-config
This should show:
UDP Ports: 50001-50100
4. Restart the antnode service (if necessary):
systemctl restart antnode
Final Testing
Once everything is configured:
• Run antnodes and check if they are communicating.
• Use netstat or ss to verify UDP ports are open:
netstat -anp | grep 50001
ss -ulnp | grep antnode
• Check logs for errors:
journalctl -u antnode --no-pager | tail -n 50
Recap
Router: Forward UDP ports 50001-50100 to the antnode server’s local IP.
Firewall: Allow inbound/outbound traffic for UDP ports 50001-50100.
antctl: Register UDP ports 50001-50100 for Autonomi antnodes.
After completing these steps, all 100 antnodes should be properly connected to the Autonomi network.
5 Likes
Great news! I don’t mind my nodes being busy doing this for the good of the network, but it’s frustrating when they don’t get rewarded. It can be a huge load on them too.
7 Likes
I don’t know the details of the environment, but it’s running AntTP, which is a http gateway/proxy which integrates the Autonomi libraries.
1 Like
As Traktion mentioned, it is running his AntTP project in the backend on a docker container. That container serves out Autonomi files directly to a port you can access with a web browser. So, if you were running it locally on your computer, you could reach your Autonomi files by going to http://localhost:8080/<autonomi_address>/.
What I did was run his container on my server, and then run Nginx (a web server) in front of it. I made it so connections to my website https://va.worldwidenodes.cyou/<autonomi_address>, forwards to his AntTP project on the backend. So, instead of you having to run it yourself locally, you can access this centralized version to retrieve your files.
I wanted non-technical people that felt intimidated by running his AntTP program to still have a way to see their files (or other public files), so everyone can see the potential.
7 Likes
About connections, this seems very relevant:
From there:
As context, I’m currently trying to build a file sharing application that should work well on a large amount of consumer devices that are likely behind NATs and firewalls.
4 Likes
Looks very comprehensive, others would need to verify the CLI inputs