Is there average rate how much node should be getting rewards running x time?
I have one node which got 4 rewards and another node 0 for both running 48 hours.
Also seeing IncomingConnectionError in both nodes. For third node with home network false and port forwarding setup in router I am getting HandshakeTimedOut.
It can really vary as data is distributed randomly throughout the network. Each node is connected to different parts of the network. So some nodes perform better than others.
How many records for each node currently? How many connected peers?
Iām not aware of such a rate, Iāve always experienced what you describe. Partially the reason could be due to the already proven inaccuracy of the rewards value reported by the nodes, they are known to have issues and sometimes report more than the actual number of rewards received by the node (plus they reset when the node is restarted). Thus even if there is such an earning rate/pattern, you couldnāt verify it through the reported rewards value.
Iāve been seeing that as well, it doesnāt seem to be related to home-network mode.
Iāll be trying to dig in a bit, perhaps itās the IP as I am suspecting it to be. Do you see in your logs if the IP (as part of the multiaddress in the form /ip4/<ip>/udp/<port>/quic-v1/p2p) the node is saying to be listening on matches the public IP where port forwarding has been set up? ā¦Iād bet thatās the issue and Iāll need to find out a way to properly support no-home-network mode.
Getting a good bit further now, however my choicess for port and metrics range semm to be getting ignored
Try refreshing the page with Ctrl+F5, and then try again, get rid of those nodes you just created and create new ones. Also check the browser console (open it with Ctrl+F12) and see if there is any issue logged. There shouldnāt be any problem with the port ranges.
Also, I wouldnāt recommend using the no-home-network mode yet as there seems to be some issues with it, switch the Home-network mode on.
I must have fat-fingered something cos the next 2 nodes started as expected.
Thank you for the attentative and prompt support 
Iāll leave it for an hour or so and see if I earn anything - all was working well before when I used these ports - and the appropriate entries in the router config
My nodes just upgraded to 0.3.3 and connected peers got reset. Will report tomorrow.
Here are logs from that node with home network false. Cannot see my IP where port forwarding has been setup though.
[2025-01-09T19:44:03.176499Z WARN ant_networking::event::swarm 423] OutgoingConnectionError to PeerId("12D3KooWPvZ65ANSLEnKHu4rLSi4Ri29t7MzDnFZR2KQZbHP8JZy") on ConnectionId(2173) - WrongPeerId { obtained: PeerId("12D3KooWF5cTuyQz5qhw3irzEj3Yfqse1eoGPmCVESk8zQZzNkjU"), endpoint: Dialer { address: /ip4/87.97.161.21/udp/50070/quic-v1/p2p/12D3KooWPvZ65ANSLEnKHu4rLSi4Ri29t7MzDnFZR2KQZbHP8JZy, role_override: Dialer, port_use: Reuse } }
[2025-01-09T19:44:03.176514Z ERROR ant_networking::event::swarm 513] OutgoingConnectionError: WrongPeerId: obtained: PeerId("12D3KooWF5cTuyQz5qhw3irzEj3Yfqse1eoGPmCVESk8zQZzNkjU"), endpoint: Dialer { address: /ip4/87.97.161.21/udp/50070/quic-v1/p2p/12D3KooWPvZ65ANSLEnKHu4rLSi4Ri29t7MzDnFZR2KQZbHP8JZy, role_override: Dialer, port_use: Reuse }
[2025-01-09T19:44:03.176530Z WARN ant_networking::event::swarm 525] Tracking issue of PeerId("12D3KooWPvZ65ANSLEnKHu4rLSi4Ri29t7MzDnFZR2KQZbHP8JZy"). Clearing it out for now
[2025-01-09T19:44:07.513934Z ERROR ant_networking::event::kad 83] GetClosest Query task QueryId(15) errored with Timeout { key: [0, 36, 8, 1, 18, 32, 16, 163, 1, 241, 35, 70, 84, 36, 23, 77, 215, 230, 104, 92, 24, 63, 143, 25, 91, 93, 98, 250, 93, 22, 65, 246, 236, 147, 243, 7, 204, 157], peers: [PeerInfo { peer_id: PeerId("12D3KooWAwJreDzpsQqzaPzf3h2DevMHHfbDierQa7352N2mhE7E"), addrs: [/ip4/65.109.35.160/udp/17164/quic-v1/p2p/12D3KooWAwJreDzpsQqzaPzf3h2DevMHHfbDierQa7352N2mhE7E] }, PeerInfo { peer_id: PeerId("12D3KooWDKkdujFiLepZX8ahxcRVEUPGs2KQPSVPWXxJxJsXm6h2"), addrs: [/ip4/37.27.71.146/udp/55194/quic-v1/p2p/12D3KooWDKkdujFiLepZX8ahxcRVEUPGs2KQPSVPWXxJxJsXm6h2] }, PeerInfo { peer_id: PeerId("12D3KooWNMhxcRZzycdkfxPPm7HbnaZFMGvZPiyp1SfXwicSfxuu"), addrs: [/ip4/94.130.221.103/udp/54360/quic-v1/p2p/12D3KooWNMhxcRZzycdkfxPPm7HbnaZFMGvZPiyp1SfXwicSfxuu] }, PeerInfo { peer_id: PeerId("12D3KooWJsRS1G9dQECQgdQUsdEk1AsnfU5szD3QdZRx8f2tX2YP"), addrs: [/ip4/95.217.109.80/udp/50092/quic-v1/p2p/12D3KooWJsRS1G9dQECQgdQUsdEk1AsnfU5szD3QdZRx8f2tX2YP] }, PeerInfo { peer_id: PeerId("12D3KooWPrsyony6TVexfrvPdezJB7WdCqrJR5wu28wuojMMLB9F"), addrs: [/ip4/94.130.221.148/udp/49163/quic-v1/p2p/12D3KooWPrsyony6TVexfrvPdezJB7WdCqrJR5wu28wuojMMLB9F] }, PeerInfo { peer_id: PeerId("12D3KooWNE3U5286Fdq3rfQ7dhj1UqEZbbhRrSpnANtNJPG8Xb49"), addrs: [/ip4/135.181.180.183/udp/50299/quic-v1/p2p/12D3KooWNE3U5286Fdq3rfQ7dhj1UqEZbbhRrSpnANtNJPG8Xb49] }, PeerInfo { peer_id: PeerId("12D3KooWMBNnA74pBU9uaSzvRFyegRas2AgLeyqggAoNXYsHGKwF"), addrs: [/ip4/58.226.117.241/udp/53318/quic-v1/p2p/12D3KooWMBNnA74pBU9uaSzvRFyegRas2AgLeyqggAoNXYsHGKwF] }] }, QueryStats { requests: 26, success: 20, failure: 5, start: Some(Instant { tv_sec: 2249416, tv_nsec: 78155440 }), end: Some(Instant { tv_sec: 2249426, tv_nsec: 217958731 }) } - ProgressStep { count: 1, last: true }
[2025-01-09T19:44:08.134553Z WARN ant_networking::event::swarm 423] OutgoingConnectionError to PeerId("12D3KooWF2ubHbHd6HAsmTT2f6ZXJbKD4nBXFcVXE7PXM84wPgJL") on ConnectionId(2175) - Transport([(/ip4/148.251.88.241/udp/49133/quic-v1/p2p/12D3KooWF2ubHbHd6HAsmTT2f6ZXJbKD4nBXFcVXE7PXM84wPgJL, Other(Custom { kind: Other, error: Right(Custom { kind: Other, error: Custom { kind: Other, error: HandshakeTimedOut } }) }))])
[2025-01-09T19:44:08.134670Z ERROR ant_networking::event::swarm 435] Dial errors len : 1
[2025-01-09T19:44:08.134687Z ERROR ant_networking::event::swarm 438] OutgoingTransport error : Other(Custom { kind: Other, error: Right(Custom { kind: Other, error: Custom { kind: Other, error: HandshakeTimedOut } }) })
[2025-01-09T19:44:08.134741Z WARN ant_networking::event::swarm 477] Problematic error encountered: Custom { kind: Other, error: Right(Custom { kind: Other, error: Custom { kind: Other, error: HandshakeTimedOut } }) }
[2025-01-09T19:44:08.134753Z WARN ant_networking::event::swarm 525] Tracking issue of PeerId("12D3KooWF2ubHbHd6HAsmTT2f6ZXJbKD4nBXFcVXE7PXM84wPgJL"). Clearing it out for now
[2025-01-09T19:44:17.265450Z INFO ant_networking::driver 1024] Set responsible range to 8204755303002505823232167971131801540219037897541808588463592752575540378(242)
[2025-01-09T19:44:32.264936Z INFO ant_networking::driver 1024] Set responsible range to 8204755303002505823232167971131801540219037897541808588463592752575540378(242)
[2025-01-09T19:44:47.263968Z INFO ant_networking::driver 1024] Set responsible range to 8204755303002505823232167971131801540219037897541808588463592752575540378(242)
[2025-01-09T19:45:02.264989Z INFO ant_networking::driver 1024] Set responsible range to 8204755303002505823232167971131801540219037897541808588463592752575540378(242)
[2025-01-09T19:45:17.265045Z INFO ant_networking::driver 1024] Set responsible range to 8204755303002505823232167971131801540219037897541808588463592752575540378(242)
[2025-01-09T19:45:32.265712Z INFO ant_networking::driver 1024] Set responsible range to 8204755303002505823232167971131801540219037897541808588463592752575540378(242)
Thanks, this is making me think that ideally the IP could be displayed on the GUI for nodes with home-net off, Iāll have to see whatās possible/doable since I believe thatās not available on the /metrics service.
A quick look at the dashboard so far with 22 started so far - roughly 50% HomeNetwork - suggests the non-HomeNetwork nodes have generally fewer peers and always ZERO records.
Early days yet as no ārelevantā records are stored anywhere but those with HomeNetwork checked are storing records in various numbers from 20 to 180
I will fire up another 5-6 HomeNetwork nodes and report back in an hour or two.
My three nodes stopped on their own 27 hours ago, caught it 24 hours ago, fresh re-start of three nodes then, 24hrs later nothing yet after ticking along at 3 to 4 attos per dayā¦ just fyiā¦ Home network setup ā¦
likely too many tabs open on my browser that were active caused the problem with too high CPU % Utilization on this 4Core8Thread 8GB i5 10thgen with 256GB SSD setup Win11 2H2024, I have about 25% SSD space free to keep GC and Defrag running ok on this flash.
I am thinking the antnodes should be given slightly higher ring priority at the OS level ahead of any user space app, itās really the top priority set of apps in user space,
so really antnodes should get priority just above kernel space, because Linux, MAC MS WIN11 OSes could start (Linux /SWAP) swapping to VRAM,
when the Browser tabs for example, do chew up all the available RAM, that would be bad, really bad for the antnodes.
I was trying to implement this as something Formicaio can automatically do, i.e. when a node commits suicide Formicaio could wait for some period of time before restarting it automatically. But unfortunately the nodes donāt report an exit code which could be used to identify that scenario to then restart it, when a node commits suicide its exit code is 0 (which is usually an exit code for success/no-issues).
@bochaco
The top 10 are home network. They consistently receive less records when compared to having home network turned off. They tend to really lag in picking up records over time as well.
When home network is turned off they pick lots of records in the first minute or two.
Just some feedback.
I assume that could be because they go through the relay node/sā¦?.. hopefully the reintroduction of DCUtR which seems will be included in next/future version of antnode should help in this regardā¦
good find!
Here are mine 10 nodes, one of them is running with home network: false which seems to be getting same amount of records and conn. peers as others. After 24h I got 2 rewards from 2 nodes with 1 reward each.
I donāt see any benefits running with home network: false. Iāll switch back to home network and stop port forwarding.
Iāve made some progress with debugging the issue, I am currently testing a fix, if confirmed to work for my setup I should be able to release a new version in one or two days.
Hereās a bazaar one for you.
I opened my Formicaio interface yesterday and had a HUGE sum in my rewards balance.
Iām running a number of nodes on each of a few wallet addresses.
One wallet showed a balance of 93 last Iād checked. Then suddenly it showed 200000000000000000093. I queried @rusty.spork who checked the blockchain who said Iād been awarded 200 in random rewards. I havenāt figured out how to check the sub-blockchain those are on.
Is this possibly something that happened in the Formicaio app? Itās interesting that I was awarded 200, but all those extra zeros!!
