Version 0.64.0

Your account screen can now check what is stored against what your file list describes, and put back a file that is stored and paid for but missing from the list.

A file reaches the storage network, is certified on chain and is committed to the server before its row is written into your own file list, and that last step can fail — it does when the list is open read-only because the current version would not open. NMTS already refuses an upload while the list cannot take the result, and holds a write that fails mid-upload until the list can take it, but a tab closed while one is held loses it, and what is left is a file that is stored, paid for, and has no name and no folder. Until now there was no way to find out whether that had ever happened to anyone; the check runs only when you press it, because it reads every page of your file record, and it also reports rows in your list whose bytes the storage network does not hold. It will not put back a file whose real size cannot be worked out: with file size hiding on, the stored pieces are encrypted from more bytes than the file holds, and the number that says how many was in the row that is missing.