NoEncryptionNet [07/02/24 Testnet] [Offline]

  • The client and node installs without a problem,
  • Windows does not block the safe.exe file,
  • running the node on the computer at home runs without a problem,
  • checking the balance and downloading tokens from the tap works without a problem,
  • all commands run at the speed of light,
  • this is my the first testnet where everything works flawlessly,
PS C:\Users\gggg> safe wallet balance --peer-id=12D3KooWBSiYxWRXS23Ha5EKh4eoLC7zfW5TTLChns4R6rkK1zg1
Logging to directory: "C:\\Users\\gggg\\AppData\\Roaming\\safe\\client\\logs\\log_2024-02-07_14-14-02"
Built with git version: db930fd / main / db930fd
Node's rewards wallet balance (PeerId: 12D3KooWBSiYxWRXS23Ha5EKh4eoLC7zfW5TTLChns4R6rkK1zg1): 0.000000000
PS C:\Users\gggg> safe wallet get-faucet 178.128.166.148:8000
Logging to directory: "C:\\Users\\gggg\\AppData\\Roaming\\safe\\client\\logs\\log_2024-02-07_14-14-24"
Built with git version: db930fd / main / db930fd
Instantiating a SAFE client...
Trying to fetch the bootstrap peers from https://sn-testnet.s3.eu-west-2.amazonaws.com/network-contacts
Connecting to the network with 97 peers
🔗 Connected to the Network
Requesting token for wallet address: b73c14faf20b55807fc81c23aecf2822ec5cb0edd0d8c5722e5d6f1ace2377f95c06da3a45dd5b2edfa2a371adbcd6e7
Successfully parsed transfer.
Verifying transfer with the Network...
Successfully verified transfer.
Successfully stored cash_note to wallet dir.
Old balance: 100.000000000
New balance: 200.000000000
Successfully got tokens from faucet.
8 Likes

Was upload cost with versions 0 and 1 different from versions 2, 3 and 4?

3 Likes

I was able to download something finally! Woot!

david@david-Macmini:~/.local/share/safe/client/wallet$ safe files download "Landscape_0.tif" fc4b349dd4dce1f07ed31724dda85c819206f3530ab805284204839397dda4bd
Logging to directory: "/home/david/.local/share/safe/client/logs/log_2024-02-07_08-27-54"
Built with git version: db930fd / main / db930fd
Instantiating a SAFE client...
Trying to fetch the bootstrap peers from https://sn-testnet.s3.eu-west-2.amazonaws.com/network-contacts
Connecting to the network with 97 peers
🔗 Connected to the Network                                                                                                                    Downloading "Landscape_0.tif" from fc4b349dd4dce1f07ed31724dda85c819206f3530ab805284204839397dda4bd with batch-size 16
Saved "Landscape_0.tif" at /home/david/Downloads/Landscape_0.tif

7 Likes

I have small file, which seems to not survive:
b0c551356ff21b023ddb01add3fa74a8eb7db3a6a940722989e98c611507ae4c.

upd. This file is available in fact, some glitch just prevented its downloading previously.

5 Likes

You’re welcome. It’s great to see you using live prices and in a different currency. :clap:

10 Likes

To avoid choking when fetching records from other peers during replication, the fetch list is divided into batches.
When a node just started, it will have a long list to complete, to fetch records from other peers that supposed to be stored by this node.
So, it’s normal you will see such log, especially during startup.

However, if the number of entries in queue remains high (not reducing) for a while, then that shall be an alert there is something wrong.

12 Likes

So it is ok to have queue filled during replication. Got it.
Of course, 40ms is not enough to process all requests:

[2024-02-07T11:13:42.835189Z INFO sn_networking::replication_fetcher] Next to fetch....
[2024-02-07T11:13:42.835189Z DEBUG sn_networking::replication_fetcher] Number of records still to be retrieved: 21
...
[2024-02-07T11:13:42.875189Z INFO sn_networking::replication_fetcher] Next to fetch....
[2024-02-07T11:13:42.875189Z WARN sn_networking::replication_fetcher] Replication Fetcher doesn't have free capacity. Currently has 48 entries in queue.
3 Likes

Think I have node running and installed vdash as well.

9 Likes

The transfer of a 192 MB MOV file was aborted after more than 10 min:
Upload terminated due to un-recoverable error Err(SequentialUploadPaymentError)
Error:
0: Failed to upload chunk batch: Too many sequential upload payment failures

PS C:\Users\gggg> safe files upload E:\gggg\Desktop\Filmy_iphone\IMG_0032.MOV
Logging to directory: "C:\\Users\\gggg\\AppData\\Roaming\\safe\\client\\logs\\log_2024-02-07_14-47-19"
Built with git version: db930fd / main / db930fd
Instantiating a SAFE client...
Trying to fetch the bootstrap peers from https://sn-testnet.s3.eu-west-2.amazonaws.com/network-contacts
Connecting to the network with 97 peers
🔗 Connected to the Network
Starting to chunk "E:\\gggg\\Desktop\\Filmy_iphone\\IMG_0032.MOV" now.
Chunking 1 files...
⠁ [00:00:00] [----------------------------------------] 0/386
Uploading 386 chunks
⠐ [00:10:23] [----------------------------------------] 0/386
Upload terminated due to un-recoverable error Err(SequentialUploadPaymentError)
Error:
   0: Failed to upload chunk batch: Too many sequential upload payment failures

Location:
   sn_cli\src\subcommands\files\mod.rs:415

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

May I ask for some guidance?

2 Likes

could you have a retry with batch_size reduced and a different file ?

safe files upload --batch-size 8 <different_file_path>
4 Likes

Now I need to find out how make those fancy @Josh plots with ram over time… those 5 nodes are a very small statistic … But for my pi the current values look as non-spectacular as ram usage can be imagined… ~50mb per node… Not rising… Pi not getting very hot …

5 Likes

My node is having 1006 records right now. Looks like close to the limit.
But files are still uploading at reasonable price (Made payment of 0.000007682 for 7 chunks).
Should it be like that?

4 Likes

I’m just trying, but with the same file, if it doesn’t work I’ll try uploading a smaller file.

3 Likes

seems correct.
the pricing curve has been refactored to allow more evenly distributed.

the max store of 2048 records is also now just an alert, which will just raise some signal and may trigger some self-cleanup.
It will not block anything.

9 Likes

Uploaded “mixtral-8x7b-instruct-v0.1.Q6_K.gguf” af4c83f1c16fbc213661f808a9fb1654a0a433617889d61a310ec3c86cec631b
Among 73219 chunks, found 0 already existed in network, uploaded the leftover 73219 chunks in 122 minutes 11 seconds.

No failed chunks… impressive. Feel free to try downloading it to see if it’s all together.

6 Likes

35gb - right?

3 Likes

There’s a plot of RAM use over time in the status for each individual node. It’s not shown by default but you can cycle through all the timeline plots using ‘t’ or hide the logfile to see more timelines by pressing ‘l’.

For more help press ‘?’.

5 Likes

Yes, 35.7 / 38,378,760,128 bytes.

3 Likes

I was finally able to access the Faucet!!!


david@david-Macmini:~/.local/share/safe/client/wallet$ safe wallet get-faucet 178.128.166.148:8000                                                           Logging to directory: "/home/david/.local/share/safe/client/logs/log_2024-02-07_09-36-40"
Built with git version: db930fd / main / db930fd
Instantiating a SAFE client...
Trying to fetch the bootstrap peers from https://sn-testnet.s3.eu-west-2.amazonaws.com/network-contacts
Connecting to the network with 97 peers
🔗 Connected to the Network                                                                                                                                  Requesting token for wallet address: a9ca885e1cabf92d10ac99c3729ec20502d93417bdc38761aab1f7f7f12bd0cd7f87bd63bccedc8b42cbc8bab5199577
Successfully parsed transfer.
Verifying transfer with the Network...
Successfully verified transfer.
Successfully stored cash_note to wallet dir.
Old balance: 0.000000000
New balance: 100.000000000
Successfully got tokens from faucet.
[1]+  Terminated              safenode
david@david-Macmini:~/.local/share/safe/client/wallet$

YES, I’M CURRENTLY ACTING LIKE A SMALL CHILD IN A CANDY SHOP. SUE ME. :wink:

Just had to test uploading whatever was on the machine.

david@david-Macmini:~/Downloads$ safe files upload safeup-0.4.0-x86_64-unknown-linux-musl.zip
Logging to directory: "/home/david/.local/share/safe/client/logs/log_2024-02-07_10-17-37"
Built with git version: db930fd / main / db930fd
Instantiating a SAFE client...
Trying to fetch the bootstrap peers from https://sn-testnet.s3.eu-west-2.amazonaws.com/network-contacts
Connecting to the network with 97 peers
🔗 Connected to the Network                                                                                                                    Starting to chunk "safeup-0.4.0-x86_64-unknown-linux-musl.zip" now.
Chunking 1 files...
⠁ [00:00:00] [----------------------------------------] 0/9                                                                                    Uploading 9 chunks
**************************************
*          Uploaded Files            *
*                                    *
*  These are not public by default.  *
*     Reupload with `-p` option      *
*      to publish the datamaps.      *
**************************************
"safeup-0.4.0-x86_64-unknown-linux-musl.zip" 2954beafbae42208fe6c4dcb63875dd11f9862586ca26957d6325e0af35e8d2d
Among 9 chunks, found 0 already existed in network, uploaded the leftover 9 chunks in 29 seconds
**************************************
*          Payment Details           *
**************************************
Made payment of 0.000007840 for 9 chunks
Made payment of 0.000001379 for royalties fees
New wallet balance: 99.999990781
david@david-Macmini:~/Downloads$

7 Likes

Yes, I only paid for the chunks that were not uploaded before.

4 Likes