What I said was that if my node has very high pricing, and clients are created to look for lower prices, then there’s an incentive replace that node with another which has a chance to earn. I can’t see a client accepting a price of hundreds of tokens per chunk, so there’s no point (from an earnings viewpoint) in keeping that node running.
This creates a potential problem in that if nodes reach that point, because the network is full, we might see an increase in churn as people shut down those nodes and start new ones.
🔗 Connected to the Network Chunking 1 files...
**************************************
Your current balance: 0.999998694
Transfer cost estimate: 0.000000284
Your balance estimate after transfer: 0.999998410
**************************************
real 0m9.352s
user 0m1.187s
sys 0m0.491s
400+0 records in
400+0 records out
409600 bytes (410 kB, 400 KiB) copied, 0.00221455 s, 185 MB/s
Logging to directory: "/home/ubuntu/.local/share/safe/client/logs/log_2024-05-18_22-40-13"
safe client built with git version: 16f3484 / stable / 16f3484 / 2024-05-09
Instantiating a SAFE client...
Connecting to the network with 49 peers
🔗 Connected to the Network Chunking 1 files...
**************************************
Your current balance: 0.999998694
Transfer cost estimate: 12.511372062
Your balance estimate after transfer: 18446744062.198178248
**************************************
real 0m3.976s
user 0m0.952s
sys 0m0.372s
That’s the log from my cost_tracker script for 2 consecutive attempts. Why does it estimate the wallet balance will jump from 0.999998694 which is genuinely what it is to 18446744062.198178248 after the upload of 4 chunks? Is this some kind of overflow?
Here is the log file from this upload in case is it is useful:-
willie@gagarin:~$ safe files download "safe.log" 5263eec93dd185169fe43156e848048d39515aa9c8505aca9b87e1ab6ab17546
Logging to directory: "/home/willie/.local/share/safe/client/logs/log_2024-05-19_00-30-29"
safe client built with git version: 16f3484 / stable / 16f3484 / 2024-05-09
Instantiating a SAFE client...
Connecting to the network with 1 peers
🔗 Connected to the Network Downloading "safe.log" from 5263eec93dd185169fe43156e848048d39515aa9c8505aca9b87e1ab6ab17546 with batch-size 16
Error downloading "safe.log": Network Error GetRecord Query Error RecordNotFound.
Some strange behaviour. Maybe? I had to kill my nodes, but then later spun up 20 news ones. After a few hours, I’ve received over 11000 records, but only got 66 nanos. Feels like I’ve been cheated, lol. I’ll wait and see if things even out…
Which is probably bad news overall.
I’ll try a few uploads.
Nah its no well…
willie@gagarin:~/.local/share/safe/launchpad/logs$ safe files upload -p ~/books/Ansible_\ Up\ and\ Running\ -\ Bas\ Meijer\ \&\ Lorin\ Hochstein\ \&\ René\ Moser.pdf
Logging to directory: "/home/willie/.local/share/safe/client/logs/log_2024-05-19_02-09-00"
safe client built with git version: 16f3484 / stable / 16f3484 / 2024-05-09
Instantiating a SAFE client...
Connecting to the network with 49 peers
🔗 Connected to the Network Chunking 1 files...
"/home/willie/books/Ansible_ Up and Running - Bas Meijer & Lorin Hochstein & René Moser.pdf" will be made public and linkable
Splitting and uploading "/home/willie/books/Ansible_ Up and Running - Bas Meijer & Lorin Hochstein & René Moser.pdf" into 32 chunks
⠂ [00:03:09] [----------------------------------------] 0/32
Until @aatonnomicc coughed to maybe having killed the network with node stopping and starting I was going to say I think I’d broken it. I needed some balance on the machine I’ve been running the upload_tricker script that uploads 400KB of random data every few seconds because the upload costs were getting large. So I ran a line that hit the faucet every 10 seconds while I made a cup of tea. I forgot and ended up going out for the day.
I have a balance of 420 tokens but they can’t be transferred anywhere and now sending and receiving tokens to any machine doesn’t work. Now the faucet doesn’t work at all. It still might have been me that broke the faucet. Or it might be the thing we’ve seen in the past where payments can’t be made because records can’t be stored.
The cost_tracker is still running as it just gets an estimate and there are some crazy costs there for 4 chunks. About 9/10 are still reasonable but a lot of the ones that aren’t are very large.
It would be nice to see if the network is salvageable with a large influx of nodes that are kept running and if the unevenness of the costs would disappear and payments start working reliably again.
Actually, token transfers are still working. They just have to not involve this wallet that was trying to get from the faucet.
Just found this though. I accidentally did a receive of a send I’d already done. It didn’t come up with the double spend error like before and just didn’t increase the balance:-
safe@sn-test-01:~/testfiles$ safe wallet address
Logging to directory: "/home/safe/.local/share/safe/client/logs/log_2024-05-19_06-43-15"
safe client built with git version: 16f3484 / stable / 16f3484 / 2024-05-09
8170dd02f03671dd2ce9ceee7b4dde152f220565832402f0cdcf07f4c9221a17b4db57b17bf8b3bd70298881c7165c7f
safe@sn-test-01:~/testfiles$ time safe wallet receive 90cc6e015614c7cc0e3a82ccfccc482eadcce9cc0ee4cc81cc646a508acc4cc5cc76202474a2cc2089cc691abdcc5db2cc98ccbacc79edcc95ccd1cc57bccc4ee7ccf3cce2cc10a3cc0a342a321a1149507f3cd9cc661640265dc0cc6a35694121e0cc44114f82cc24d4ccebcc1169f6cc7180cc37a3cc50a0cc48a2cc21c8cc465ee0cc8acc6000dceccc4d5e0d7553f4cce8ccf6cc1edaccaacc4977ffcc7487cca6cca8cc9accc6cc39e3ccedccfaccf1cc0a47f0cc5d70f9ccb3cc115be8ccd7cc1eb5ccf3ccb6cc5d19dacc1c3a3e0bd0cc74beccedcc93cc7d9eccc8ccf1cc591e8dcc85ccebccedcc6f1cddccffcc8dcc30d4cc7e40aecc35cbccc3cc5ee2cc5afdcc30e2cc24a8cccfcc2cb8cc7fcacc10527c7134bccc60317c2dedcc98cc3ec3cc5d0c2e602995cccecc3b7be3cc8cccfdcc697400dc1ad0cc95cc1213471c68d2cc96ccc0cce3cc21ecccf2ccf6ccbbcc363b2b2885cc11d7cc8acca5cc52559ecc2122fbccc2cce9ccebcc7284cca9ccfbccaecc94ccd3ccadccc8cc93cc3a28adcc3000dc9391646574707972636e45a981
Logging to directory: "/home/safe/.local/share/safe/client/logs/log_2024-05-19_06-47-09"
safe client built with git version: 16f3484 / stable / 16f3484 / 2024-05-09
Instantiating a SAFE client...
Connecting to the network with 49 peers
🔗 Connected to the Network Successfully parsed transfer.
Verifying transfer with the Network...
Successfully verified transfer.
Successfully stored cash_note to wallet dir.
Old balance: 0.099999989
New balance: 0.109999989
real 0m22.359s
user 0m0.597s
sys 0m0.381s
safe@sn-test-01:~/testfiles$ safe wallet receive 90cc6e015614c7cc0e3a82ccfccc482eadcce9cc0ee4cc81cc646a508acc4cc5cc76202474a2cc2089cc691abdcc5db2cc98ccbacc79edcc95ccd1cc57bccc4ee7ccf3cce2cc10a3cc0a342a321a1149507f3cd9cc661640265dc0cc6a35694121e0cc44114f82cc24d4ccebcc1169f6cc7180cc37a3cc50a0cc48a2cc21c8cc465ee0cc8acc6000dceccc4d5e0d7553f4cce8ccf6cc1edaccaacc4977ffcc7487cca6cca8cc9accc6cc39e3ccedccfaccf1cc0a47f0cc5d70f9ccb3cc115be8ccd7cc1eb5ccf3ccb6cc5d19dacc1c3a3e0bd0cc74beccedcc93cc7d9eccc8ccf1cc591e8dcc85ccebccedcc6f1cddccffcc8dcc30d4cc7e40aecc35cbccc3cc5ee2cc5afdcc30e2cc24a8cccfcc2cb8cc7fcacc10527c7134bccc60317c2dedcc98cc3ec3cc5d0c2e602995cccecc3b7be3cc8cccfdcc697400dc1ad0cc95cc1213471c68d2cc96ccc0cce3cc21ecccf2ccf6ccbbcc363b2b2885cc11d7cc8acca5cc52559ecc2122fbccc2cce9ccebcc7284cca9ccfbccaecc94ccd3ccadccc8cc93cc3a28adcc3000dc9391646574707972636e45a981
Logging to directory: "/home/safe/.local/share/safe/client/logs/log_2024-05-19_06-50-11"
safe client built with git version: 16f3484 / stable / 16f3484 / 2024-05-09
Instantiating a SAFE client...
Connecting to the network with 49 peers
🔗 Connected to the Network Successfully parsed transfer.
Verifying transfer with the Network...
Successfully verified transfer.
Successfully stored cash_note to wallet dir.
Old balance: 0.109999989
New balance: 0.109999989
lots of nodes incoming after my adventures getting things moved over to safenode-manager 0.7.6
to sudo or not to sudo that is the question ?
if I start without sudo all node directory’s shift back to there ~/.local/share/safe/node location
which is cool but they die or crash which is not very convenient.
if you run everything including status as sudo it works same as before on safenode-manager 0.7.5
fist attempt
0: Not enough balance in wallet to pay for chunk. We have NanoTokens(11689074824) but need NanoTokens(683494412469) to pay for the chunk
second attempt
0: Not enough balance in wallet to pay for chunk. We have NanoTokens(11689074824) but need NanoTokens(683494412458) to pay for the chunk
@storage_guy uploads are back following a steep drop in upload prices
ubuntu@sby:~$ safe files estimate -p ~/b.txt
Logging to directory: "/home/ubuntu/.local/share/safe/client/logs/log_2024-05-20_00-55-46"
safe client built with git version: 6771a01 / stable / 6771a01 / 2024-05-17
Instantiating a SAFE client...
Connecting to the network with 49 peers
🔗 Connected to the Network Chunking 1 files...
**************************************
Your current balance: 11.689074824
Transfer cost estimate: 580.970250450
Your balance estimate after transfer: 18446743504.428375990
**************************************
followed by
ubuntu@sby:~$ safe files estimate -p ~/b.txt
Logging to directory: "/home/ubuntu/.local/share/safe/client/logs/log_2024-05-20_01-16-13"
safe client built with git version: 6771a01 / stable / 6771a01 / 2024-05-17
Instantiating a SAFE client...
Connecting to the network with 49 peers
🔗 Connected to the Network Chunking 1 files...
**************************************
Your current balance: 11.689074824
Transfer cost estimate: 0.000000220
Your balance estimate after transfer: 11.689074604
**************************************
and a test upload of the same file was successful
ubuntu@sby:~$ safe files upload -p ~/b.txt
Logging to directory: "/home/ubuntu/.local/share/safe/client/logs/log_2024-05-20_01-16-55"
safe client built with git version: 6771a01 / stable / 6771a01 / 2024-05-17
Instantiating a SAFE client...
Connecting to the network with 49 peers
🔗 Connected to the Network "/home/ubuntu/b.txt" will be made public and linkable
Splitting and uploading "/home/ubuntu/b.txt" into 4 chunks
**************************************
* Uploaded Files *
**************************************
"b.txt" a2f76f93c9fab5d955b3e539f21722a8d01ecd47e847b8b9b9f267704c75835a
Among 4 chunks, found 0 already existed in network, uploaded the leftover 4 chunks in 42 seconds
**************************************
* Payment Details *
**************************************
Made payment of NanoTokens(220) for 4 chunks
Made payment of NanoTokens(36) for royalties fees
New wallet balance: 11.689074568
…
