Node Operator Fireside Discussion

If there are any questions or topics you want covered during the fireside chat, please add them here!


When will multi-node dashboards be possible?
What about a native Synology application?
What trends are you seeing with inbound data? Is Storj becoming more popular?
How many nodes are currently in production?

  • Would like to hear something about ethereum scaling solutions you are keeping an eye on.
  • Can you already share anything about aligning payouts with the new pricing?
  • Could you share some info on node churn rates you’re seeing?
  • What are the expectations about network growth over the coming months? A year? Multiple years?
  • A while back there was some talk about possibly tuning RS numbers, any updates on this?
  • What can you tell us about current test data and traffic patterns? Any changes in that planned?

Edit as mentioned further down:


What’s the status of the web browser-compatible JS client library idea?


What other potential methods to pay SNO’s are you considering at the moment?

And a suggestion: If not everything can be answered during the Zoom, it would be great to receive the answers in this thread here.


Do problems like Trouble with UDP affect customer experience in any measurable way?

Does Storj plan to accept L2 payments?

Jocelyn was heavily involved in the forum community but since her departure that involvement doesn’t seem to have been replicated. Any plans to change that?

How much does Storj currently owe to SNO’s who have not signed up for L2 payments and haven’t met the threshold for L1?

How can Storj consider small SNO’s in any way profitable considering you need to wait up to a year for a L1 payment and L2 Exchanges are yet to exist?


Is there a plan to make Storj nodes resilient to SMR disk technology?
More generally I guess the questions is:
:arrow_right: Could the node software ensure that it automatically refuses ingress requests whenever the underlying storage system (HDD, SSD, …) cannot keep up? Is that feature considered?

Currently, if the storage system cannot keep up, the node eats up all the RAM of the system by caching data waiting to be written down, and gets killed by the system eventually. The only workaround currently is to limit the number of concurrent requests the node is authorize to process, which is a shame because that drastically limits its ability to handle bursts of requests (even SMR drives can keep up with high loads for some time before starting to stall - limiting the number of concurrent requests prevents the node from using this ability).

Cheers :slight_smile:


I was hoping we would see something like this directly in the Linux kernel: ext4-lazy.

1 Like

I love your post, great questions! But this is a stretch for sure. Chia and Storj have only one thing in common… they use HDD space. They use it for wildly different purposes though. There may be some mild competition on the supply side, but Storj is in a good position there as used space on Storj is much more valuable. Anyone doing both would be wise to remove Chia plots to make room for Storj when needed. That’s what I do at least.

I would be curious to know Pauls motivations for that career move though.

@john: I though of some more questions:

Both of these suggestions have gotten positive response from Storj Labs and a mention that “something like it will probably be implemented” but no further follow up.

1 Like

This is great. Thank you for the questions. We’ll get through all that we can and if we run out of time, we’ll get a blog post out with the rest or respond here.

If this fireside chat format works well, we’ll try to work this into our regular cadence.


That was great @john @jtolio @Knowledge ! Thanks for the updates.

I hope this will become a more frequent thing.

I think there were still plenty questions left to fill a few more of these. :slight_smile:


Thanks to everyone who attended and for the great questions. We’ll get the recording into the queue to get posted. We’ll go through the questions above and figure out what didn’t get covered and post answers as well.

The next Town Hall is scheduled for October 20 and we’ll have some Q&A around the TH, too.


Hope the recording will be hosted on the Storj network :wink:

@john I understand you have very limited time and huge demands but I must admit I was disappointed more questions were not addressed.

If a similar format was to be followed in future I doubt I would tune in live if most of the questions would be answered post event anyway. There would be little point to do so live.

I just hope it is released - and the other questions answered and not forgotten about and put on the back burner.

A purpose can change. And maybe they’d become interested in using all the space they have for something other than only mining. In any case I think it is worth a second thought if a member of the leadership team of a decentralized storage provider switches to another decentralized platform that handles large amounts of disk space.

I would expect the video to be be both on Storj and other channels. To be transparent, we posted the call for questions a week in advance and ended up getting all the questions the day before the fireside chat. We prepped and organized as quickly as we could, but it was a lot of ground to cover.

I will get around to answering the remaining questions, but it will take me probably a week or two to get through it all.

We’re considering a few options for the next one of these, including an AMA style, here or in Reddit, but we’ll post a poll when we have dates and give some options. We want to continue with the Fireside Chats, but we want to make sure the format is what the community will find most valuable.


@penfold we would have liked to have made it through more questions, also, but we will get all the answers posted.

Here’s a plug for the the next one of these - please post your questions earlier! JT and I are at a disadvantage from a time zone perspective. The bulk of the questions were posted in the middle of the night for us and the Fireside chat was first thing in the AM.

We’ll try to give even more notice next time. The AMA style here or in Reddit might also be more effective.

Overall though, we just appreciate the engagement!