Repair traffic started to rise, I see 4TB Egress in 6 days, most of it come last days, but small repair ingress.
I guess for SNOs with multiple nodes… even if they start uploading more to service repairs… ideally they could gain more as their other nodes start winning their own ingress-from-repairs? Everybody is going to be watching their graphs ![]()
I’m still waiting for US bloom filters to start again and humble us…
I dont see big repair ingress.
This is only confirms, that we shouldn’t invite to invest into a hardware. I was not happy when this post has been posted, because it could be a problem in the future, I shared my concerns (and I was right), but we believed that we can onboard this customer to the Public Network as fast as possible. The only problem, that the customer is shifted to SOC2 Type II on a final stage of the paperwork.
The core problem remains:
If Wasabi wants to onboard a large new customer they build a datacenter. If Storj wants to onboard a large customer what shall they rely on? That enough people with tiny 4TB drives accidentally decide to become node operators. Thousands of them just right in time so the customer can be onboarded?
Probably not a strategy that works.
I rather think in such cases it is inevitable that people see a chance and buy drives.
Maybe not today with the Vivint experience and the disk prices…
That’s why SOC2 for the global network should be very much on the top of the list for the next leadership team if any.
I believe, that we can offer a surge pricing, as we did in the past.
It takes years, we are were in a position of a few weeks. Select was already here, thus - no options, or allow them to go.
Which would even push SNOs to buy stuff.
Should have started that earlier then. And hopefully the next leadership team will handle that better.
Demand for SOC2 was low and usually came with requirements for placement in US DCs. But yes, it’s good to offer when you know how it will turn out. There were no predictions about such demand.
So we continued the process, but now, unfortunately, it’s been put on hold again due to current circumstances; there’s no funding for it right now.
33899 and growing nicely… ![]()

