The same thing happened again, when trying to send those tokens: Wallet has pre-unconfirmed transactions.
With a quick search I found out that this same thing has happened to many others on several testnets. Didn’t find what it is about, though.
I still can use my tokens for uploading though. I started a big upload of ubuntu-18.04.4-desktop-amd64.iso a couple of day ago. It always froze after 60-100 chunks, and now I tried with that, and it still behaves the same.
Hmm… but trying with any small file that is of my own making and guaranteed to not be in the network already, the upload freezes. Maybe ubuntu-18.04.4-desktop-amd64.iso has already been uploaded by someone else, and the seeming relative success is because I don’t need to pay? But why doesn’t it just go all the way through?
80 nodes running for one week, earnings approx 1000 nanos uploading to network failed everytime by now. So better to use home spare hardware than leased vps.
Yesterday I had one laptop running about 80 nodes. For a long time tt had about 5 nodes having one shunning. Then later, when I think my router started to cough upon me adding more nodes via another laptop, more nodes started to get shunned.
I don’t know yet, if it was the router or my 400/50 connection reaching it’s limits. The uploading from here were somewhat high for sure as there were a lot of GETs and them some other use of the connection.
And at least one network participant upgraded to the latest version
Very unsure this really qualifies for bad node detection to be triggered at this stage of the game… But no matter what version you are using this might (just maybe !) be a reason for being wrongly accused of being a bad guy
It is not necessarily terrible at least that is not my current conclusion.
It is just over 1 slap on the wrist per node per device since they started.
It also seems very evenly spread out.
Its just annoying really, I have lighting fast internet a good router and dedicated devices running at virtually no load and the nodes get flagged accross the board.
I decided to go very light in order to know if going hard is the issue.
Difficult to know if pushing is causing issues when you dont know what happens when you take it easy.
Will amp it up later with a fresh start and compare.
Considering the small size of the network then one shun per node is actually possible with some/many of them being your own nodes and problems of 2 nodes behind the one router talking to each other (they don’t talk)
I have been trying to start nodes using node-launchpad-v0.1.3 without much success. I am running windows10/11 on different machines. I can add nodes but cannot get passed message being displayed that says (please wait…)? would like to be ready to start nodes when Wave 1 Beta begins.
I have two laptops, one has 17 nodes and the other 21 nodes running at the moment, and they have been like this for about two hours. They were set up with upnp flag.
My routers Port Sharing tab shows that the one having 17 nodes has 17 “Independent port sharing” enabled, but the one having 21 nodes has only 15. If I remember right, it used to have more, maybe even the amount of nodes. Is this normal?
Both laptops have one node being Shunned x1, and on both of them most of the nodes have a number in StoreCost column in Vdash. And on both machines some nodes have even earned some nanos!
EDIT: Whenever I add a node to either machine, the number of “Independent Port Sharing” adds up correspondingly. So some of them have probably dropped for some reason, but it does not have any evident effect on the nodes running.
I’ve been uploading by just repeating the uploads. It has taken most of the day but one upload of 108 chunks keeps failing due to greedy nodes, but the number of chunks left is falling gradually, currently at 14.
Having said that I am running out of tokens, only 55k nanos left so a new testnet or another small handout would be nice:
uploading to network failed everytime by now. So better to use home spare hardware than leased vps.
