store hashes of releases in blockchain?

[jkister]

would be a good idea to also store hashes of release files in the blockchain, like on memo.cash or other. github+blockchain safer.

[The-One-Law]

I probably did something wrong,
before digging into panic
I will recheck everything but this is an argument for nailing hashes to the blockchain.
You could do this on memo or member or even use the
{Exquisitely Lovely} OP_RETURN option on the desktop version
without even breaking a sweat.
[manj-pc Bch]$ sha256sum Electron-Cash-4.2.0-x86_64.AppImage
77617a7b525448fbb59e6c92f245a063bb542d5477f82baeb1dea9048f1df518 Electron-Cash-4.2.0-x86_64.AppImage
[manj-pc Bch]$ cat SHA256.Electron-Cash-4.2.0-x64_64.AppImage.txt
5cf72937300a80e4290fda6877319eed7f3a77fa82c6e068d0d4619551d8c3e0 Electron-Cash-4.2.0-x86_64.AppImage

[The-One-Law]

It really does actually read
" keys-n-hashes/sigs-and-sums/4.2.0/win-linux/SHA256.Electron-Cash-4.2.0-x64_64.AppImage.txt "
my fail, sorry to bother you guys - carry on...

[The-One-Law]

Still dare not use 4.2.0
and I see you uploading the same mistake for 4.2.1

https://github.com/Electron-Cash/keys-n-hashes/blob/master/sigs-and-sums/4.2.1/win-linux/SHA256.Electron-Cash-4.2.1-x64_64.AppImage.txt

it is x86-64 and the hashes for 4.2.0 do not match.
I am using 4.1.1 because the hashes do not match