Latest Release March 20, 2025

How are you starting nodes then? This will dictate how you change the setting.

And him doing it or not doesn’t change that others are taking the opportunity - if you want to blame someone or something go for the node Software or the E-thing :wink:

4 Likes

Gotta agree, if users are doing anything that the network alows and it doesn’t boot them we can’t blame the user.

Also :+1: to Might for being honest. Everyone who cares about success should be honest about what they are doing whether that is perceived good or bad.

4 Likes

And if we help him, we only encourage others to take the piss as well.

No he’s not the worst, not by a long way.
Doesn’t make it right, either.

2 Likes

:man_shrugging:

Since I’m running at a loss when running nodes I honestly don’t care at all and congratulate whoever manages to find resources this cheap =D (and the more joining this fight for the cheapest resources the less every singled one of them gains ; )

2 Likes

Look, I mentioned I like transparancy so I’ll give you that. If all I’m getting in return is such a hostile attitude I’m quickly done sharing.

For your information, I have around 5MB per node (in the cloud) which is way below the 300 MB you think. It is still more than plenty for what the network requires nodes to have it this moment and my script is made to scale down nodes gradually way before they run into storage issues.

The reason I have 550k nodes is to counter the other big whales that are not updating. My nodes are running on devices that have <40% cpu usage, enough bandwidth and run the latest version. They’ve been doing that for over a month already. Running at a loss, for the better of the project.

My intentions have been nothing but good, I have shared every detail of it and even reached out to the team to give them more information about how people are optimizing node running.

And for what it’s worth, the things I’m asking for help with is for my home network nodes which has way to expensive hardware and cost me plenty because I wanted quality nodes at the start of the network. Those are not earning a thing and have also been running at a major loss since TGE.

Ask anything you want to know and I’ll shall answer in detail. But please don’t start the blame game and your hostile attitude towards me when you don’t know what you’re talking about.

8 Likes

Come on, how much does any given node consume at the moment? Does anyone have a node that would consume even 100MB?

Looking at the % of the emission I’m getting the network is around 5.5 million nodes. I doubt that’s true, because we know of plenty of people that run nodes and are not earning. Dimitar and some of his friends for example.

And yes, I’ve always updated within 24 hours.

3 Likes

Like about 10% of the official number? That’s interesting.

EDIT: for the sake of transparency, I’m running antnode: v0.3.9-rc.1 at the moment. Only 15 though.

1 Like

Starting a node directly like: ā€œ Nohup /root/.local/bin/antnode —port (port) —root-dir (ant location) etc. &ā€

1 Like

Yes, my 550k nodes are earning around 1600 ANT a day. ± 10% of the total emission.

4 Likes

ANT_LOG=ant_evm=info nohup /root/.local/bin/antnode etc&

1 Like

If that is indeed the case, you have my apologies.

4 Likes

At this point 300MB per node is plenty to have fully functional nodes. With less than 10 records on any of my nodes (average of 2 or 3), it suggests 50MB average per node is also very much enough.

If uploads were fully working then I doubt he could keep running them with only that much space.

But really until the disk is 80% (not node storage but disk) the nodes will be fully functional.

So while I agree that they are somewhat dysfunctional in that only in the short term they will perform, it is the keeping up to date that is important.

Actually based on my emissions earnings average the network would be 12.8 million. And since some are getting above the average per node, it might mean the network is small than this if using emissions payout as an estimate. Now that might be the network size of updated nodes and there are a lot more not updated

That’d be measuring nodes that are capable of getting emissions. IE nodes that are at latest release

7 Likes

Are we sure that it is just uploads?
Not to rock the boat too much but I managed 2 largish uploads within the last 24 hours.

One I downloaded immediately after successfully, 20 minutes later network error. Now I can’t download either of them.

We say uploads are not working and seemingly assume that downloads are fine.

5 Likes

Wonder how many of these we can still download?

The mint iso failed

time ant file download e7bb1b87c1f0e07cdb76ba5e82a425a8da712940c2d3553aa6791494e92aa54d . #md5sum feefb18e7916c9a16bb09923ed98df64 ubuntu-16.04.6-desktop-i386.iso
Logging to directory: "/home/willie/.local/share/autonomi/client/logs/log_2025-03-31_03-25-28"
šŸ”— Connected to the Network                                                                                                 Error: 
   0: Failed to fetch Public Archive from address
   1: General networking error: GetRecordError(QueryTimeout)
   2: GetRecord Query Error QueryTimeout
   3: Network query timed out

Location:
   ant-cli/src/actions/download.rs:108

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

real	0m54.677s
user	0m1.358s
sys	0m0.549s

mercifully quickly :slight_smile:

3 Likes

For uploads to work properly there are a few underlying bugs to be fixed. Like getting always the closest nodes when doing quotes, routing working more efficiently, and so on.

But to answer directly, of course uploads is not the only thing, but it is, if you will, the elephant in the room and the others are more around smooth sailing and not getting certain errors etc.

But as far as seeing the network act as a data network then yes it is the major one by far because it drags in so many other bugs that it depends on being fixed

Some of downloads is not getting the right nodes holding the data, and not every time either. This cause is fixed when uploads is working because that error is also affecting how reliable uploading is

3 Likes

He said 5MB, not 50MB though. But I’d wager that’s enough at the moment, too. Average of 2-3 records, and the record size probably much under the max. 4MB.

I note that I am earning well at the moment. I had a problem with blocked UDP traffic after the internet went down for 6 hours a few weeks ago on 3 different machines in different locations but from the same provider and it was fixed after changing the IP addresses, so I suspect that when the internet started I triggered some protection and that is why the UDP traffic was blocked…

The last 2 days with 20k nodes I have been earning 100 tokens per day, down from 250 per day before.

One of the machines with 7700 nodes was making 250 tokens per day, now it has dropped to 50 tokens.

The other people around me have given up, only 2 are mining at the moment. One is @Saykor on discord and likes to talk to @neo :wink: The other has put 7-8 machines at friends’ houses and his electricity and internet are free and he is happy with the mining… :happyant:


Check out the Dev Forum

2 Likes

At the moment, is there any other way to ascertain you nodes are reachable and useful, than getting either emissions or ANTs from uploads?

Drives me crazy with my 15 nodes to not get either. Not the for the money, of course, would never expect 15 nodes to earn much, but I’d like to know if they are fine or not. I run them with Formicaio, and it says everything is fine.