do you have data from these satellites on your node?
This is from du
$ sudo du . -chd1
1.8G ./qstuylguhrn2ozjv4h2c6xpxykd622gtgurhql2k7k75wqaaaaaa
23G ./v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa
773G ./ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa
9.5G ./pmw6tvzmf2jv6giyybmmvl4o2ahqlaldsaeha4yx74n5aaaaaaaa
806G .
806G total
Yes, just not a lot of it (as expected, due to not being vetted)…
1 Like
So, it has a little amount of data.
Thus kind of expected to do not pass vetting yet.
But… even with so much data coming out of Saltlake at the moment?
I’m agree, it’s weird, why that node do not receive data from Saltlake, however, since it’s coming from the libuplink somewhere in the USA, perhaps this node is simple too far from the source and most of uploads if ever happen just canceled due to a long tail cancelation.
I don’t think so. One of these unvetted nodes is on a server with a vetted node: the vetted one is getting a lot of traffic with a success rate above 98% so long tail cancellations doesn’t seem like a problem.
I don’t know, I guess I just have to sit back and wait… but those nodes are missing out on the testing, which seems a shame.
Perhaps it’s related to a new node selection algorithm?
That was only implemented last week and these nodes are 2 or 3 months old without a single audit, though…
1 Like
Then I do not know why is that. Luck? Or a DDoS protection?
DDoS seems unlikely as I have vetted nodes running just fine on the same machine as the ones which are not getting vetted.
Luck… Well, I don’t know… I guess if there’s only a small number of us reporting this “problem” then maybe it really is just luck 
My last new node was also long time without audits and in one time I started to get them a lot.
So I think it is something with audit algo.
1 Like
Unvetted nodes get 1% of the new traffic. Since those satellites had very low traffic in the past year, I don’t see how they’d get any new traffic. New traffic leads to stored pieces, which leads to audits (the more pieces you have, the higher chance the satellite requests to audit a piece).
I agree with others about the vetting process needing to be tweaked: If the unvetted node is online for more than X months and still not fully vetted, send 100 audits to it on the spot. If it passes them, fully vet it. If it doesn’t have 100 pieces from a satellite in X months, consider it vetted.
I have some theory that new uploaded pieces are not audited for some period of time, to save some traffic or processing. but it is only my theory.
In my opinion the vetting process should be revised, in the sense that if a new node is started on an IP that already has other nodes checked, it should already be reliable, or at least have a faster vetting process. If an old and reliable node operator adds a disk you have out of the 10/20 disks it already has, why check it?
it check not only operator but hardware also, mostly people use old hdds, and it you share lot of data to hdd and it die, it is bad for network, so firstly you get little data, to qualify that hardware setup is stable.
1 Like
e[4mMay 2024 (Version: 14.0.0) [snapshot: 2024-05-26 23:58:01Z]e[0m
REPORTED BY TYPE METRIC PRICE DISK BANDWIDTH PAYOUT
Node Ingress Upload -not paid- 1.56 TB
Node Ingress Upload Repair -not paid- 71.10 GB
Node Egress Download $ 2.00 / TB (avg) 123.65 GB $ 0.25
Node Egress Download Repair $ 2.00 / TB (avg) 81.39 MB $ 0.00
Node Egress Download Audit $ 2.00 / TB (avg) 849.92 KB $ 0.00
Node Storage Disk Current Total -not paid- 1.01 TB
Node Storage ├ Blobs -not paid- 819.20 GB
Node Storage └ Trash ┐ -not paid- 195.54 GB
Node+Sat. Calc. Storage Uncollected Garbage ┤ -not paid- 210.30 GB
Node+Sat. Calc. Storage Total Unpaid Data <─┘ -not paid- 405.84 GB
Satellite Storage Disk Last Report -not paid- 608.90 GB
Satellite Storage Disk Average So Far -not paid- 396.33 GB
Satellite Storage Disk Usage Month $ 1.49 / TBm (avg) 338.84 GBm $ 0.50
________________________________________________________________________________________________________+
Total 338.84 GBm 1.76 TB $ 0.75
Estimated total by end of month 396.33 GBm 2.10 TB $ 0.91
*Note: Disk Last Report deviates 53.64% from Disk Average So Far, indicating last reported satellite stats may temporarily be inaccurate.
This will impact Disk Last Report, Uncollected Garbage and Total Unpaid Data estimation.
Please refrain from using this data to ask for support unless it doesn't resolve itself in a couple of days.
e[4m
Payout and held amount by satellite:e[0m
┌────────────────────────────────┬─────────────┬──────────────────────────┬─────────────────────────────────────────────────────────────┐
│ SATELLITE │ HELD AMOUNT │ REPUTATION │ PAYOUT THIS MONTH │
│ Joined Month │ Total │ Disq Susp Down │ Storage Egress Repair/Aud Held Payout │
├────────────────────────────────┼─────────────┼──────────────────────────┼─────────────────────────────────────────────────────────────┤
│ ap1.storj.io:7777 (0% Vetted > 0/100 Audits) │ │ $ 1.49/TBm $ 2.00/TB $ 2.00/TB 75% 25% │
│ 2024-03-25 3 │ $ 0.00 │ 0.00% 0.00% 0.00% │ $ 0.0027 $ 0.0006 $ 0.0001 -$ 0.0025 $ 0.0008 │
├────────────────────────────────┼─────────────┼──────────────────────────┼─────────────────────────────────────────────────────────────┤
│ eu1.storj.io:7777 (OK) │ │ │ $ 1.49/TBm $ 2.00/TB $ 2.00/TB 75% 25% │
│ 2024-03-25 3 │ $ 0.02 │ 0.00% 0.00% 0.00% │ $ 0.0622 $ 0.0203 $ 0.0001 -$ 0.0619 $ 0.0206 │
├────────────────────────────────┼─────────────┼──────────────────────────┼─────────────────────────────────────────────────────────────┤
│ saltlake.tardigrade.io:7777 (0% Vetted > 0/100 Audits) │ $ 1.49/TBm $ 2.00/TB $ 2.00/TB 75% 25% │
│ 2024-03-25 3 │ $ 0.00 │ 0.00% 0.00% 0.00% │ $ 0.0035 $ 0.0000 $ 0.0000 -$ 0.0026 $ 0.0009 │
├────────────────────────────────┼─────────────┼──────────────────────────┼─────────────────────────────────────────────────────────────┤
│ us1.storj.io:7777 (OK) │ │ │ $ 1.49/TBm $ 2.00/TB $ 2.00/TB 75% 25% │
│ 2024-03-25 3 │ $ 0.09 │ 0.00% 0.00% 0.00% │ $ 0.4365 $ 0.2264 $ 0.0000 -$ 0.4972 $ 0.1657 │
├────────────────────────────────┼─────────────┼──────────────────────────┼─────────────────────────────────────────────────────────────┤ +
│ TOTAL │ $ 0.11 │ │ $ 0.5049 $ 0.2473 $ 0.0002 -$ 0.5642 $ 0.1881 │
│ ESTIMATED END OF MONTH TOTAL │ $ 0.79 │ │ $ 0.6102 $ 0.2949 $ 0.0002 -$ 0.6790 $ 0.2263 │
└────────────────────────────────┴─────────────┴──────────────────────────┴─────────────────────────────────────────────────────────────┘
My 3 month old node hasn’t even started screening yet. I’ll check it once I start.
Same deal here, ~2 month old node. No audits received from SLC.
It is receiving ~ 10-12GB / day test data from SLC.
Compared to a vetted node getting ~2-300GB / day from SLC.
So it’s ~4-5% of the vetted traffic - which seems right.
NodeID 1RYftXMieo4emxKzZZFK1bXoySpy8sf1SceWgxg4LY4ezexViz
┌────────────────────────────────┬─────────────┬──────────────────────────┬─────────────────────────────────────────────────────────────┐
│ SATELLITE │ HELD AMOUNT │ REPUTATION │ PAYOUT THIS MONTH │
│ Joined Month │ Total │ Disq Susp Down │ Storage Egress Repair/Aud Held Payout │
├────────────────────────────────┼─────────────┼──────────────────────────┼─────────────────────────────────────────────────────────────┤
│ ap1.storj.io:7777 (0% Vetted > 0/100 Audits) │ │ $ 1.49/TBm $ 2.00/TB $ 2.00/TB 75% 25% │
│ 2024-03-22 3 │ $ 0.01 │ 0.00% 0.00% 0.00% │ $ 0.0031 $ 0.0010 $ 0.0000 -$ 0.0031 $ 0.0010 │
├────────────────────────────────┼─────────────┼──────────────────────────┼─────────────────────────────────────────────────────────────┤
│ eu1.storj.io:7777 (OK) │ │ │ $ 1.49/TBm $ 2.00/TB $ 2.00/TB 75% 25% │
│ 2024-03-22 3 │ $ 0.03 │ 0.00% 0.00% 0.20% │ $ 0.0501 $ 0.0071 $ 0.0000 -$ 0.0429 $ 0.0143 │
├────────────────────────────────┼─────────────┼──────────────────────────┼─────────────────────────────────────────────────────────────┤
│ saltlake.tardigrade.io:7777 (0% Vetted > 0/100 Audits) │ $ 1.49/TBm $ 2.00/TB $ 2.00/TB 75% 25% │
│ 2024-03-22 3 │ $ 0.00 │ 0.00% 0.00% 0.00% │ $ 0.0057 $ 0.0001 $ 0.0000 -$ 0.0043 $ 0.0014 │
├────────────────────────────────┼─────────────┼──────────────────────────┼─────────────────────────────────────────────────────────────┤
│ us1.storj.io:7777 (OK) │ │ │ $ 1.49/TBm $ 2.00/TB $ 2.00/TB 75% 25% │
│ 2024-03-22 3 │ $ 0.18 │ 0.00% 0.00% 0.18% │ $ 0.6179 $ 0.3095 $ 0.0001 -$ 0.6957 $ 0.2319 │
├────────────────────────────────┼─────────────┼──────────────────────────┼─────────────────────────────────────────────────────────────┤ +
│ TOTAL │ $ 0.22 │ │ $ 0.6768 $ 0.3177 $ 0.0002 -$ 0.7460 $ 0.2487 │
│ ESTIMATED END OF MONTH TOTAL │ $ 1.09 │ │ $ 0.7994 $ 0.3718 $ 0.0002 -$ 0.8786 $ 0.2929 │
└────────────────────────────────┴─────────────┴──────────────────────────┴─────────────────────────────────────────────────────────────┘
From what i gather, there are two kinds of data being uploaded to saltlake: testing and reservation. Testing data (ie recent bandwidth testing) isn’t committed to the satellite, so the satellite knows nothing about it (can’t request an audit for a piece it doesn’t know exists). The reservation data may have not been started uploading yet, so no new traffic (accounted for) => no pieces on the node (from the satellite’s point of view) => nothing to audit.
Well, we are being paid for the test data, so the satellite must know something about it…
1 Like