Yep, they didn’t clear out the data that migrated from the killed network to the new one. All they did was to fix the bug. It would have required another network reset to clear it out
Seems like there has been somewhat of a lack of updates or community involvement or otherwise scheduled marketing since wave 2, like a month ago. Waiting for wave 3 now, for more significant changes? (New libp2p update perhaps, though maybe that’s already in place.) Haven’t received any nanos, though that’s not bothering me much.
I’m not using launchpad but have had to reduce the number of nodes from 22 to 10 in one example.
If you haven’t already try again with a small number and see if that helps, although I noticed that my earnings stopped overnight so it seems to have slowed down a lot. So you also need to keep an eye on what others are reporting.
I did a test with launchpad for 24 hours and no earnings, 1/3 never got any PUTs and the other 2/3rds took a long time for all of them to get any PUTs.
I reset and started up my nodes with port forwarding and in 6 hours had 80 nanos from the 40 nodes
Anyone else have really low peer counts? Like 0-13. Running 10 nodes with port forwarding through safe node manager and nothing different from before.
Though… now that I think of it, I was doing electrical work in the house and had the breaker on/off several times within an hour… maybe I’m considered bad nodes now??
VDash uses the logs which give Routing Table peers - very stable and the ones the nodes wants to communicate with longer term
safenode-manager statususes the connection peers which is a highly variable figure compared to the RT peers and can be low one second and high the next
Yes, I have had 10 nodes running from home for 5 weeks. That’s the most I can run with my 80/20 ADSL and until Monday I sometimes had to switch up to 5 of them off to have enough bandwidth for Netflix, etc. They all still earn again after these multi hour switch offs. They use the port forwarding with the --ports option. They’ve been in existence for 5 weeks including through the upgrade. Example below. Their shun count is between 6 and 45. Example below.
I have 5 nodes running from another location using the --home-network option and they have run without being switched on and off. They’ve not earnt since the upgrade so I’m going to redeploy them using port forwarding. I was seeing if they would ever earn again and that’s enough time to tell me there is something wrong with them or the --home-network option. Their shun count is between 49 and 131. Example below.
I am Josh I am desperate to be on form and help out, just taking longer than I hoped for, but all going the right way. Never been in hospital in my life then get ill, PITA.
The main thing is the direction is great, I just wish the team had more space for support.