Thanks again! Update is live!
1 Like
You can see it on the dashboard, when you hover mouse over version number
that makes no sense…that version number has always been much lower than what this announcement told us was the lowest version else we would get DQ.
even when the post was made only 4 months ago… how are we suppose to know what do when the information given out in such a short timeframe is conflicting.
so we should just disregard what that post says?
and why would it even be written if it was wrong at the time it was written, was it just suppose to inform us about that version DQ was turned on… and the version thing is just how it will become at one point…
1 Like
I do not see any conflict - the lowest version of storagenode to join the network is 1.13.0. But minimum version to run a node is 1.22.2
Today I Learned that the 1.13.0 in the version mouseover is the minimal allowed to join the network. Would still like to see the minimum to receive ingress (currently 1.22.2) included in the mouseover.
1 Like
but a node with version 1.13.0 that joins the network gets DQ,
according to that statement, but maybe thats what you mean by joining the network…
or are you referring to that joining the network doesn’t mean on gets data
and running a node means that the node can get data…
but then again… why is the post giving out incorrect information at the time it was created…
since it can then still be more than 3 minor updates without getting DQ
if joining the network means you get DQ below this limit… maybe it should have a better name…
since not respecting that limit will destroy the node
2 Likes
I am still on 1.21.2 and have up- & downloads so far.
I think it is when the docker 1.24.4 version is released.
Any time I’ve been below the “storagenode: minimum: version:” listed in https://version.storj.io/ my ingress has flatlined, and I’ve been told I need to update to be properly taking part. Not sure how you’re working or if my understanding is incorrect.
I’m with @SGC on this one I must say, I’m very confused what versions disqualify nodes or not considering that hovering the version on the dashboard shows Running the minimal allowed version: 1.13.0: That is way more than 3 minor versions behind!
Did I miss something?
2 Likes
Why would we DQ old nodes and not just pause ingress like in the past?
I don’t know what Storj’s specific reason for drawing the lines where they have, but it is pretty standard for software vendors to require a certain minimum version for support. Known bugs, incompatibility with newer network features, etc. could be valid reasons to require being on a more recent version.
1 Like
I’m glad somebody brought up the question of minimum versions, I was going to ask about that. It is unclear how to get disqualified by just 1 version number.
A great and simple thing would be to simply show all the info on version tooltip.
“Latest software version is: vx.y.z
Limited ingress below this version: vx1.y1.z1
Node disqualification below this version x2.y2.z2”
4 Likes
It would be even greater if the color of the version number would change. Like green if version is up to date, yellow and orange if updates have been missed, red if no ingress anymore and maybe black if below minimum or something like that.
6 Likes
Yeah, that’s a great idea, simple and effective.
Maybe green for latest, green with “Update available” when 1 behind, then organge for no ingress and red if in danger of DQ.
exactly. And it will be disqualified due to
It’s still valid - do not allow your node to be older than three minor updates.
I do not think that disqualification is enabled, if your node behind the three minor versions, but it:
- will not receive any ingress;
- could not be paid for usage because of outdated orders version (discussed on the forum) and they can be rejected.
2 posts were merged into an existing topic: Maintenance: us2.tardigrade.io downtime - February 28th 2021
What is your question ?
1 Like
zkSync Transaction ID
Depending on which payout method you have chosen the payout history on the storage node payout dashboard will link to the zksync block explorer or etherscan.