# Changelog v1.24.4 **URL:** \ **Category:** STORJLINGS\ **Tags:** official-changelog\ **Created:** [February 26, 2021, 1:00pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995 "2021-02-26T13:00:06Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![littleskunk](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/littleskunk/32/63_2.png) [@littleskunk](https://forum.storj.io/u/littleskunk)\ **Post date:** [February 26, 2021, 1:00pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/1 "2021-02-26T13:00:06Z")
> **[Release v1.24.4 · storj/storj](https://github.com/storj/storj/releases/tag/v1.24.4)** > > Changelog > Storagenode > > \[+ 12fde34\] web/multinode: delete node option added to context menu > \[+ 2e1455b\] multinode/multinodedb: add sqlite3 support > \[+ 9e7e753\] sn/sndb/payouts: migrate distributed ==... **For Storage Nodes** **Undistributed Payout** On the storage node payout dashboard, we have added a few information regarding distributed and undistributed payout for the current and any previous month. **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. **Multinode Overview** Last release we introduced the new multinode dashboard. Remember the installation is still manual: [[Tech Preview] Storage Node Multinode Dashboard](https://forum.storj.io/t/tech-preview-storage-node-multinode-dashboard/11749) The multinode dashboard can now give a basic overview of used space, free space, bandwidth, and the storage node version. The payout information on the multinode dashboard is currently not correct. For now please use the payout information from the old storage node dashboard instead. ---
**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/5_5575768a8748004e209b776fc1b2916d.png) [@Vadim](https://forum.storj.io/u/Vadim)\ **Post date:** [February 26, 2021, 1:12pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/2 "2021-02-26T13:12:27Z")
what about of return audits count to API? ---
**Author:** ![deathlessdd](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/deathlessdd/32/6067_2.png) [@deathlessdd](https://forum.storj.io/u/deathlessdd)\ **Post date:** [February 26, 2021, 2:19pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/4 "2021-02-26T14:19:23Z")
The only thing that matters is the minimal version on here. [https://version.storj.io/](https://version.storj.io/) ---
**Author:** ![littleskunk](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/littleskunk/32/63_2.png) [@littleskunk](https://forum.storj.io/u/littleskunk)\ **Post date:** [February 26, 2021, 4:43pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/6 "2021-02-26T16:43:55Z")
> [@Vadim](#): > > what about of return audits count to API? I haven’t checked. I don’t see it in the commit history but it might have been hidden in another commit. ---
**Author:** ![littleskunk](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/littleskunk/32/63_2.png) [@littleskunk](https://forum.storj.io/u/littleskunk)\ **Post date:** [February 26, 2021, 5:00pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/7 "2021-02-26T17:00:38Z")
> [@CutieePie](#): > > So we skipping v1.23.4 ? What’s the implications on Ingress to nodes from a satellite as minimum supported version - I’m only asking as I track Github release, and if we are going to start skipping release numbers I’ll have to track releases another way so I can manually upgrade. Yes there was a v1.23 release. We used it to iterate quickly towards migrating the old satellites to the new multipart upload code base. That was executed on SLC and allowed us to discover and fix a few bugs. Over the next few weeks we are going to migrate all satellites. In general this can always happen. When it comes to deployments my biggest concern is that we screw up the satellite migration or the rolling upgrade. There is room for a bunch of errors that our unit tests wouldn’t cover. We do have a rolling upgrade test in place. That test is sensitive for version numbers. In order to get accurate test results we sometimes have to push a new release. With a point release we might bypass the rolling upgrade test and that can have some very bad consequences. ---
**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\ **Post date:** [February 26, 2021, 9:06pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/8 "2021-02-26T21:06:37Z")
> [@littleskunk](#): > > zkSync Transaction ID Do you happen to know what the contents/format of the receipt field would be for zkSync payouts. I’m going to have to make some adjustments for this in the earnings calculator but haven’t switched to zkSync myself yet, so I would need an example. Edit: Never mind, found it. Prefix will simply be zksync instead of eth. Simple enough. Looks like I’ll also be removing some warnings as there is a database migration included to fix missing distributed amounts for stefan-benten. Nice! That’ll clean up some historic misreporting. ---
**Author:** ![littleskunk](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/littleskunk/32/63_2.png) [@littleskunk](https://forum.storj.io/u/littleskunk)\ **Post date:** [February 26, 2021, 9:12pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/9 "2021-02-26T21:12:44Z")
I believe in the storage node database you would find something like this: `zksync:0x260abd6959105bd8ad078d0d62563016d545e9a7c753cfed50178fec7246420c` The dashboard will link: [https://zkscan.io/explorer/transactions/0x260abd6959105bd8ad078d0d62563016d545e9a7c753cfed50178fec7246420c](https://zkscan.io/explorer/transactions/0x260abd6959105bd8ad078d0d62563016d545e9a7c753cfed50178fec7246420c) ---
**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\ **Post date:** [February 26, 2021, 9:14pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/10 "2021-02-26T21:14:15Z")
Edited my previous message just too late. Thanks though! ---
**Author:** ![littleskunk](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/littleskunk/32/63_2.png) [@littleskunk](https://forum.storj.io/u/littleskunk)\ **Post date:** [February 26, 2021, 11:46pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/12 "2021-02-26T23:46:25Z")
> [@CutieePie](#): > > will be much better when cockroachDB deployed and Sats are global. I believe we have that already. Maybe not on all satellites because they get migrated one by one. It doesn’t change our currnet deployment. So lets assume we would have the “single point of failure” satellite with a postgres db in the background. The deployment process for such a setup was: 1. Upgrade DB to the new version. Old API and core instances must be able to run with the new DB. 2. Upgrade the API instances one by one. Hopefully the customer will not notice that the API instances are getting replaced with the new version. There should always be at least 1 API endpoint online. 3. Last but not least upgrade core and any other process that is left. Now the only difference in a multiregion satellite is the location. The deployment remains the same. ---
**Author:** ![SGC](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/sgc/32/1132_2.png) [@SGC](https://forum.storj.io/u/SGC)\ **Post date:** [February 27, 2021, 11:39am UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/13 "2021-02-27T11:39:48Z")
well actually according to previously announcements it’s 3 and pretty strict… tho it does sort of become 4 because it’s 3 updates they count… and outside is DQ > [@Keeping your node up to date, changes to storage node software! PLEASE READ this thread!](https://forum.storj.io/t/keeping-your-node-up-to-date-changes-to-storage-node-software-please-read-this-thread/9722): > > Hello Storage Node Operators!! We’ve got some important changes to the Storage Node Software and the network and it’s important that all of our SNOs are aware of and understand these changes. First, it’s vitally important that your storage node software automatically updates. If you have installed your storage node through [our official instructions](https://documentation.storj.io/setup/cli/software-updates) (either via our Windows installer or official Docker instructions using Watchtower), you have nothing to worry about and your node will automatical… > [@deathlessdd](#): > > The only thing that matters is the minimal version on here. [https://version.storj.io/](https://version.storj.io/) so since when? and why isn’t there like an easy place to get all these types of critical information… kind of ridiculous we can’t even agree on what version we can be on before we get DQ. should be pretty basic easy to check stuff… ---
**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\ **Post date:** [February 27, 2021, 11:56am UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/14 "2021-02-27T11:56:32Z")
Thanks again! Update is live! > [@Earnings calculator (Update 2023-12-05: v13.1.0 - Now with support for different payouts per satellite - Detailed earnings info and health status of your node, including vetting progress)](https://forum.storj.io/t/earnings-calculator-update-2021-02-27-v10-1-0-detailed-payout-information-now-includes-comparison-to-actual-payout-postponed-payouts-due-to-threshold-and-transaction-links/1794/377): > > Just a small update today to support zkSync transaction links for those who switched payouts to zkSync. It will now link to the appropriate [zkscan.io](http://zkscan.io) url for the transaction. The warning about stefan-benten misreporting payouts as postponed has been removed as the storagenode update to v1.24.4 will correct the nodes database. Unlike the previous update this one doesn’t require you to have updated to v1.24.4, but if you haven’t yet payouts for stefan-benten are still misreported (now without warn… ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [February 27, 2021, 12:35pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/15 "2021-02-27T12:35:12Z")
You can see it on the dashboard, when you hover mouse over version number ---
**Author:** ![SGC](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/sgc/32/1132_2.png) [@SGC](https://forum.storj.io/u/SGC)\ **Post date:** [February 27, 2021, 1:05pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/16 "2021-02-27T13:05:32Z")
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… > [@Keeping your node up to date, changes to storage node software! PLEASE READ this thread!](https://forum.storj.io/t/keeping-your-node-up-to-date-changes-to-storage-node-software-please-read-this-thread/9722): > > Hello Storage Node Operators!! We’ve got some important changes to the Storage Node Software and the network and it’s important that all of our SNOs are aware of and understand these changes. First, it’s vitally important that your storage node software automatically updates. If you have installed your storage node through [our official instructions](https://documentation.storj.io/setup/cli/software-updates) (either via our Windows installer or official Docker instructions using Watchtower), you have nothing to worry about and your node will automatical… ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [February 27, 2021, 2:20pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/17 "2021-02-27T14:20:18Z")
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 ---
**Author:** ![Craig](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/craig/32/1122_2.png) [@Craig](https://forum.storj.io/u/Craig)\ **Post date:** [February 27, 2021, 3:30pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/18 "2021-02-27T15:30:11Z")
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. ---
**Author:** ![SGC](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/sgc/32/1132_2.png) [@SGC](https://forum.storj.io/u/SGC)\ **Post date:** [February 27, 2021, 3:51pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/19 "2021-02-27T15:51:26Z")
> [@Alexey](#): > > 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 > [@Keeping your node up to date, changes to storage node software! PLEASE READ this thread!](https://forum.storj.io/t/keeping-your-node-up-to-date-changes-to-storage-node-software-please-read-this-thread/9722/1): > > We are going to start disqualifying nodes that are 3 minor releases behind. In the above example, 1.10 and older will get DQed. We will also be ensuring that the standard source code release will simply refuse to start if it’s 3 minor releases behind. 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 ---
**Author:** ![maxsch](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/maxsch/32/1130_2.png) [@maxsch](https://forum.storj.io/u/maxsch)\ **Post date:** [February 27, 2021, 3:54pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/20 "2021-02-27T15:54:46Z")
> [@Craig](#): > > (currently 1.22.2) 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. ---
**Author:** ![Craig](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/craig/32/1122_2.png) [@Craig](https://forum.storj.io/u/Craig)\ **Post date:** [February 27, 2021, 4:00pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/21 "2021-02-27T16:00:00Z")
Any time I’ve been below the “storagenode: minimum: version:” listed in [https://version.storj.io/](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. ---
**Author:** ![Pac](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pac/32/6053_2.png) [@Pac](https://forum.storj.io/u/Pac)\ **Post date:** [February 27, 2021, 4:04pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/22 "2021-02-27T16:04:03Z")
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? ---
**Author:** ![joesmoe](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/joesmoe/32/63_2.png) [@joesmoe](https://forum.storj.io/u/joesmoe)\ **Post date:** [February 27, 2021, 5:06pm UTC](https://forum.storj.io/t/changelog-v1-24-4/11995/23 "2021-02-27T17:06:36Z")
Why would we DQ old nodes and not just pause ingress like in the past? [Next page](https://forum.storj.io/t/changelog-v1-24-4/11995.md?page=2)