Announcement: Preparing for Today’s (18th Dec) Network Reset

No subsidies, no market-rate payments from uploaders to node operators, no useful apps, and no expectation of permanent data storage.

Using this situation to try to reason that subsidies will be required in the live network is absurd.

The beta rewards have though clearly shown that node operators will respond to incentives, e.g. the massive drop off in nodes after rewards finished earlier in the month, and the massive growth in Ethereum addresses being used when the incentives pushed people towards that.

2 Likes

My best guess is that they feel that 1. there is abuse and want to change the rules on the fly or 2. they want to see what the turnout and behavior is when nobody has a clue about what is going on.

2 Likes

That’s right, it was a joke to show the absurdity of not having rules for the prizes.


Check out the Dev Forum

3 Likes

That is good to know :laughing:

Clear rules would help everyone.

I expect the team saying clearly ‘no leaderboard’, means rewards will be based only on the percentage of attos you earn, at least from now until the next milestone where they’ve said they’ll release more details.

But, time will tell!

3 Likes

Maybe someone can help me here:
Started nodes on my old imac with ubuntu, then on an old Microsoft Surface running Win10.
But cannot get nodes to run on my PC (AMD Ryzen 7 3700X, 4TB on the E drive, 64GB RAM), Win11

Error adding new nodesstrong text
When trying run a node, we reached the maximum amount of retries (5).
Could this be a firewall blocking nodes starting?
Or ports on your router already in use?

Firewall settings are the same as for the MS Surface, so it cant be that.
“Or ports on your router are already in use” - how would i check this? how can i investigate?

One other question:
How can I clean out the configuration for Launchpad?
Via Manage Nodes I reduced the number of nodes to zero.
I reset all Nodes.
I stopped node-launchpad.exe and the various antnode.exe programmes in Task Manager.
I deleted the contents of the Node folder.

At this point I thought it must be clean. So i rebooted and tried again. I was quite surprised to see that it opened with 2 Antnodes still showing as Added. Then I saw that my wallet address was still there so there must be a configuration file somewhere. Where is it so i can delete it too? or is there a better way to do complete this clean up?

And even if I delete the node-launchpad.exe, then delete the entire folder, check there are no processes running, then reboot, then download new, then extract to a new location and start again, my wallet address is still there and there are still 2 failing Antnodes present. Where is this information saved?

I found it
C:\Users\xxxx\AppData\Roaming

now i found the error. it refused to run nodes when i changed the disk drive to my 4TB HDD

Maybe some final moment tweaks, and we get more information in todays Dev Update?

1 Like

[quote=“DavidMc0, post:25, topic:40813”]
rewards will be based only on the percentage of attos you earn
[/quote].

I thought it was mentioned that rewards will be based on wallet activity, earning and spending, when Dave is released for uploads? So the more we upload and use the attos we earn, the better chance of receiving rewards?

1 Like

Something like that was discussed. We’ll need to wait until more announcements are made before getting a good understanding I expect.

3 Likes

@Chriso So far ok node-side, but client-side I cannot connect.

Both awe and ant fail to acquire enough peers and fail to connect when I ask them to upload. Possibly due to a not so great connection (mobile hotspot) but I haven’t had any problems recently to suggest the connection is bad at the moment. antup works fine too.

LOG for ant upload:
ant.zip (19.8 KB)

EDIT: since autonomi 0.3.1 the above issue seems not to be present but there’s a problem with not getting enough quotes: Issue #2573

3 Likes

I have the same issue using the same library versions and environment variables as before. This is for sn_httpd. Not tried CLI yet.

I was planning to bump to more recent versions, but just saw your post and it looked similar.

1 Like

CPU load seems very small.

RAM load seems higher than before.
6 nodes consume 2.26GB, ranging from 220MB to 770MB per node.

The 2 oldest nodes consume between 600MB - 800MB, and all the rest between 220MB to 330MB each. There does not seem to be much correlation with other figures, than the age. For example the RAM consumption does not seem to change in sync with number of connections, that themselves change quite quickly from around 200 - 300 to about 2000 max. and soon back around 200 - 300 again.

2 Likes

seeing exactly the same…

using ant client, latest release, lots of

Failed to dial: DialError(DialPeerConditionFalse(NotDialing) followed eventually with General networking error: GetRecordError(QueryTimeout)

digging further it’s seeing an issue with the supplied bootstrap peers being unresponsive- > AS14061 DigitalOcean, LLC

 ERROR ant_bootstrap::contacts 208] Failed to get bootstrap addrs from URL http://139.59.198.251/bootstrap_cache.json: reqwest::Error { kind: Request, url: "http://139.59.198.251/bootstrap_cache.json", source: TimedOut }
Dial Errors

addr=/ip4/65.108.206.179/udp/55026/quic-v1/p2p/12D3KooW9xGRxWXnkS3c8Yfe7Mx3oHQYK4FMucfjeNheDwgxkuqw Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠋ [00:00:34] [----------------------------------------] 0/1 addr=/ip4/47.207.67.50/udp/7606/quic-v1/p2p/12D3KooWRRNCXqbdiUyhQUfwKzVx1FXrUWRwBph9Mq6v7bPucb54 Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠈ [00:00:34] [----------------------------------------] 0/1 addr=/ip4/75.48.86.24/udp/13859/quic-v1/p2p/12D3KooWP6Vo72nqZrVmUQcRWoE2tQbWtmegpDBbX8VC4KBbbq4Y Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠈ [00:00:35] [----------------------------------------] 0/1 addr=/ip4/108.61.216.155/udp/50004/quic-v1/p2p/12D3KooWGqqdcrJRd3HcMfZSoMszXexvzqZ2ee8kv3VTRyXPNpek Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠁ [00:00:35] [----------------------------------------] 0/1 addr=/ip4/173.234.26.114/udp/6805/quic-v1/p2p/12D3KooWModS7bDpu9MVgZgky92QasKWYjQyrMK37tAVADnPKeoo Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) addr=/ip4/65.108.207.240/udp/55003/quic-v1/p2p/12D3KooWGZshM94ZRDs9kPs8kY1dGvZ6B3kEW4dpCZtN5QK1V6C1 Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠒ [00:00:35] [----------------------------------------] 0/1 addr=/ip4/65.108.127.86/udp/55025/quic-v1/p2p/12D3KooWBph9yznYFWKrgUVKRmSQX2bxXWAqBVmvMy49SHp6KaUd Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) addr=/ip4/65.109.156.111/udp/55017/quic-v1/p2p/12D3KooWNUizE4jGa8hiB4ULYEGj2fqAjhYJeMD4RTxUwTcW4odX Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠠ [00:00:36] [----------------------------------------] 0/1 addr=/ip4/157.90.130.124/udp/56754/quic-v1/p2p/12D3KooWBGFWM9Z2s7G4kgUPGzyV9vHDhmQrPAc9LK8geVVsoZte Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠒ [00:00:37] [----------------------------------------] 0/1 addr=/ip4/37.27.67.96/udp/55004/quic-v1/p2p/12D3KooWQHbcMo6j8rk9Lht7TvoX9uxfhnDXngr4SzqEvBrtYhCj Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠁ [00:00:38] [----------------------------------------] 0/1 addr=/ip4/65.108.100.44/udp/42621/quic-v1/p2p/12D3KooWCQg35aDqLnVXVexRypbBdJ4dDMaJC2KujGsE11SXXqnD Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠄ [00:00:39] [----------------------------------------] 0/1 addr=/ip4/135.181.182.178/udp/55011/quic-v1/p2p/12D3KooWNgZH7xmB2d7oJf9FLXxf1H4oxxuyKZwbeQfWh5fKdp3w Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠲ [00:00:41] [----------------------------------------] 0/1 addr=/ip4/94.130.221.166/udp/35370/quic-v1/p2p/12D3KooWM8UqmwKjc5L8tCfKQawzJ3DwrAKnkksxmEuuTaK4tvJG Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠤ [00:00:45] [----------------------------------------] 0/1 addr=/ip4/178.128.171.247/udp/46160/quic-v1/p2p/12D3KooWLSk2z9D7eda5oza5gRMZYJL7zohwNUC8r1VbgndyfnyU Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠠ [00:00:45] [----------------------------------------] 0/1 addr=/ip4/128.199.250.44/udp/45006/quic-v1/p2p/12D3KooWNHn3QiW6H7kMwcmUiPLujYidHdto5xdNodYLFJo8G276 Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠠ [00:00:45] [----------------------------------------] 0/1 addr=/ip4/65.108.195.221/udp/54036/quic-v1/p2p/12D3KooWAQRvGiz9rLEJLFDLAzPdaA6dqCLjqeGjHEKqbrT7FafC Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠤ [00:00:45] [----------------------------------------] 0/1 addr=/ip4/65.109.154.181/udp/55022/quic-v1/p2p/12D3KooWSNJ1pLJAYS8TgGjmhfy6DnmebL6vaPF8QKs1MVCArmrF Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠦ [00:00:45] [----------------------------------------] 0/1 addr=/ip4/65.109.57.238/udp/55016/quic-v1/p2p/12D3KooWDXrTqe3AZ7xSqbnVTEhSHkzoQbJC5a28Fkborjhx44Dq Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠒ [00:00:45] [----------------------------------------] 0/1 addr=/ip4/94.130.221.170/udp/51360/quic-v1/p2p/12D3KooWAkt9RuD9Uis871Pe8QdGjaCW3ob9Ucbs5qfm1WjsNVJk Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠦ [00:00:48] [----------------------------------------] 0/1 addr=/ip4/65.108.197.254/udp/48191/quic-v1/p2p/12D3KooWBo7oYcQ8F8c2NogxDEsahQpW3uG5wpV5uYdTSG23kNna Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠲ [00:00:53] [----------------------------------------] 0/1 addr=/ip4/139.59.161.74/udp/53512/quic-v1/p2p/12D3KooWPG4nvYaGMh3FpHe8FAdnDDgetRuSygTXSAgZ6y7KovFD Failed to dial: DialError(DialPeerConditionFalse(NotDialing)) ⠤ [00:01:02] [----------------------------------------] 0/1

don’t feel it’s internet link related, as seeing the same in multiple locations.

interestingly, around 1 in 5 requests for the files are getting through after a good > 5 mins getting peers, for a file size of less than 32MB.

Jad

2 Likes

Hey everyone,

Sorry, but I just have too much going on right now.

We will be able to come back to these issues, just give us a bit of time please–we are not ignoring you.

A hotfix is getting put together just now, hopefully to be released tomorrow.

11 Likes

Just to answer this quickly. If you’re talking here about the keys that had to be set at build time, those are no longer required.

5 Likes

I am seeing the complete opposite, way more cpu intensive.

2 Likes

Yes, I am about 40 to 50% more cpu usage per node

5 Likes

The hotfix is addressing the CPU issue guys, just give us a little bit of time please. It will be available as soon as humanly possible.

20 Likes

We understand, CPU usage is not a problem and something that doesn’t need immediate attention.

BTW any clue on what happened to store cost in the /metrics (no value there for it) and also not in the logs either. And wallet balances not being updated in the /metrics values either

1 Like