# Changelog v1.6.4 **URL:** \ **Category:** STORJLINGS\ **Tags:** official-changelog\ **Created:** [June 7, 2020, 3:17pm UTC](https://forum.storj.io/t/changelog-v1-6-4/7387 "2020-06-07T15:17:03Z")\ **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:** [June 7, 2020, 3:17pm UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/1 "2020-06-07T15:17:03Z")
> **[storj/storj](https://github.com/storj/storj/releases/tag/v1.6.4)** > > Ongoing Storj v3 development. Decentralized cloud object storage that is affordable, easy to use, private, and secure. - storj/storj **For Storage Nodes** **In Memory Used Serials** The storage node keeps the used serials list in memory instead of writing them into a SQLite DB. Serial numbers are used for double spend protection. To minimize memory usage we decreased the expire time for uplinks from 24 hours to 1 hour. Within 1 hour the uplink needs to start the transfer because otherwise, the storage nodes will reject the order. The transfer itself can still take longer than 1 hour. Orders are also still valid for 48 hours. After one hour the storage node can delete the used serials without any consequences. By default `storage2.max-used-serials-size` is 1 MB. If the maximum size is reached the node will start dropping random serial numbers. If you want to optimize your storage node you should take a look into monkit stats for `delete_random_serial` On a restart, the storage node will drop all serial numbers. For a short time, a malicious uplink could submit an old order twice while the storage node would get paid only once. However, the uplink still needs 29 pieces to reconstruct the file. Other storage nodes will keep rejecting the malicious uplink request. **500 MB Node Selection Threshold** With the previous release, we enabled the node selection cache on all satellites. The cache is refreshed every 3 minutes and as a result, nodes can still be selected for upload for up to 3 minutes after the node signaled that it’s nearly full. Nodes previously sent this signal when there was less than 100MB of space left, but this was insufficient and some nodes filled up that 100MB within the 3-minute delay. We raised it to 500MB to compensate for this. **Storage Node Payout History Fixed** We fixed the payout data on the satellite side. The storage node payment dashboard should show correct payout data from day 1 for all satellites. There was also a problem with the download traffic accounting on saltlake. The accounting was too slow compared to the number of orders the satellite had to process. In the beginning, Saltlake was falling behind with the accounting only for a few especially bigger storage nodes. For the majority of the smaller storage nodes, saltlake was still able to process all orders. Over time the number of affected storage nodes increased slowly. We fixed it in the first week of June and are currently moving the data into the May payout. **Storage Node Dashboard** We added total earning to the storage node dashboard and also a diagram that shows used space, free space, and garbage. We are aware that the values shown in the storage node CLI are inconsistent with the WebUI dashboard. The CLI dashboard is showing piece size + metadata but the WebUI dashboard is showing piece size only. This will be fixed with the following release. **Suspension Mode Audit Score** Last release we added `unknownAlpha` and `unknownBeta` values to the storage node dashboard API. Now `unknownScore` is available as well. **For Customers** **Bucket Value Attribution** For open-source projects, we offer an [open source partner program](https://storj.io/open-source/). Open source partners are getting a special partner ID and a short name from us. The short name can be used for a feature that we call [bucket value attribution](https://github.com/storj/storj/blob/a974db7eec9487f87f266aef09e2bbb329d2be1e/docs/blueprints/value-attribution.md). More information on how to enable this feature can be found here: [https://documentation.tardigrade.io/how-tos/configure-tools-for-the-partner-program](https://documentation.tardigrade.io/how-tos/configure-tools-for-the-partner-program) ---
**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/6_22734026db12803ebb3e059622ac3534.png) [@Vadim](https://forum.storj.io/u/Vadim)\ **Post date:** [June 7, 2020, 3:48pm UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/2 "2020-06-07T15:48:43Z")
Storj Team, i realy like new Version looks like. I show me much more information. ---
**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:** [June 7, 2020, 6:52pm UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/3 "2020-06-07T18:52:22Z")
The web dashboard is still wrong regarding past payouts > [@Web dashboard past payout information seems doesn't fixed yet](https://forum.storj.io/t/web-dashboard-past-payout-information-seems-doesnt-fixed-yet/7394): > > Storagenode version 1.6.3 The sum of payout is looks correct, but the data in the table is not because of wrong measure units of used storage I think. 29.6 TBh is 0.0405479452054795 TBm or $0.0608219178082192. But not $26.78. ---
**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:** [June 7, 2020, 8:25pm UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/4 "2020-06-07T20:25:01Z")
I think @stefanbenten still needs to update. ---
**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:** [June 7, 2020, 9:30pm UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/5 "2020-06-07T21:30:00Z")
didn’t littleskunk say there would be moved stuff from > [@littleskunk](#): > > In the beginning, Saltlake was falling behind with the accounting only for a few especially bigger storage nodes. For the majority of the smaller storage nodes, saltlake was still able to process all orders. Over time the number of affected storage nodes increased slowly. We fixed it in the first week of June and are currently moving the data into the May payout. most likely what you are seeing… because yeah the numbers look odd. ---
**Author:** ![Enzo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/enzo/32/60_2.png) [@Enzo](https://forum.storj.io/u/Enzo)\ **Post date:** [June 7, 2020, 11:37pm UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/6 "2020-06-07T23:37:37Z")
One of my nodes is still on 1.4.2… Mabey I should check the updater service… **Update:** I restarted the update service on my node, and it still has not updated… Should I just wait? Is 1.5.2 still being released? ---
**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:** [June 8, 2020, 7:21am UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/7 "2020-06-08T07:21:09Z")
1.5.2 is out across all platforms ---
**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:** [June 8, 2020, 7:35am UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/8 "2020-06-08T07:35:09Z")
With the new update rolling out I’m guessing the cursor has been reset and your node will receive 1.6.3 whenever it’s its turn. There is no need to rush it, 1.4.2 still works fine. ---
**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:** [June 8, 2020, 7:38am UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/9 "2020-06-08T07:38:19Z")
one will get warning emails from storj that using older node versions can hurt reputation tho… ---
**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:** [June 8, 2020, 7:42am UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/10 "2020-06-08T07:42:06Z")
Yes, but the minimum version is currently 1.3.0, so it’l work just fine and there won’t be a reputation impact. ---
**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:** [June 8, 2020, 7:46am UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/11 "2020-06-08T07:46:53Z")
yeah i kinda think it’s FAKENEWS to… but it says so in the emails… i really get to use so many new words under all this censorship xD ---
**Author:** ![Storgeez](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/storgeez/32/68_2.png) [@Storgeez](https://forum.storj.io/u/Storgeez)\ **Post date:** [June 8, 2020, 9:37pm UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/12 "2020-06-08T21:37:26Z")
I love the new hollow pie chart for disk space - finally we can see total used space! Also how about making the bandwidth chart show previous month and make the days since start of the month a different colour? And make it say “Traffic used this month”. The disk space graph isn’t switched with selected satellite for per-satellite view though, I just noticed. ---
**Author:** ![litori](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/litori/32/1132_2.png) [@litori](https://forum.storj.io/u/litori)\ **Post date:** [June 8, 2020, 10:11pm UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/13 "2020-06-08T22:11:56Z")
Can we have a dashboard feature to capture failed audits or critical errors and show it on the dashboard? ---
**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:** [June 8, 2020, 10:16pm UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/14 "2020-06-08T22:16:24Z")
Please use the ideas portal for that. ---
**Author:** ![buchette](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/buchette/32/6794_2.png) [@buchette](https://forum.storj.io/u/buchette)\ **Post date:** [June 9, 2020, 11:12pm UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/15 "2020-06-09T23:12:49Z")
> [@littleskunk](#): > > **In Memory Used Serials** does this really mitigates the db locks ? ---
**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:** [June 9, 2020, 11:15pm UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/16 "2020-06-09T23:15:03Z")
duno what changed… but my node just suddenly stopped doing the db locked thing… and i wasn’t able to get it back… kinda makes it seem a bit like it might also related to node age… but i duno. ---
**Author:** ![buchette](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/buchette/32/6794_2.png) [@buchette](https://forum.storj.io/u/buchette)\ **Post date:** [June 9, 2020, 11:17pm UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/17 "2020-06-09T23:17:29Z")
ok, my main node stopped having db locks , especially on this one, but now under heavy traffic it’s back. Can’t wait for the linux docker image update to see the difference. But storing in memory as a buffer just can be better performance wise. ---
**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:** [June 9, 2020, 11:22pm UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/18 "2020-06-09T23:22:46Z")
ill need to check if its back… there was a long long time with nearly no traffic which kinda disrupted my testing… and kinda forgot about it… also haven’t rebooted for a week and it’s usually after reboots it an issue for me… or during clean up… ill have to inspect my logs more closely ---
**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:** [June 10, 2020, 8:25am UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/19 "2020-06-10T08:25:24Z")
A post was split to a new topic: [FATAL Unrecoverable error {“error”: “CreateFile](https://forum.storj.io/t/fatal-unrecoverable-error-error-createfile/7456) ---
**Author:** ![node1](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/node1/32/6289_2.png) [@node1](https://forum.storj.io/u/node1)\ **Post date:** [June 15, 2020, 11:51am UTC](https://forum.storj.io/t/changelog-v1-6-4/7387/20 "2020-06-15T11:51:53Z")
Is this update stuck somewhere? My dockers still haven’t got it 😑 while it’s more then a week since it’s released. [Next page](https://forum.storj.io/t/changelog-v1-6-4/7387.md?page=2)