The SHA-1 of the .ZIP file is:
9a3efe6130ba21ab2ade9df38ff9d52a539d9693
I dont have the zip file because I deleted it once I extracted it
The SHA-1 of of my .EXE file is:
11428c3bdf728860fd057c411a95b14e13f05dbc
Are the ZIP and EXE checksum suppose to be different? is mine safe?
Hi Everyone, happy that PhoenixMiner has returned to help sort this thing out. So I have a couple concerns and hope maybe you folks can help me.
When I download the 5.5c for windows from the new github (
https://github.com/PhoenixMinerDevTeam/PhoenixMiner/releases/) the SHA1 I get is:
SHA1: 191F35A6F90C5CAA9C95813A1B1737E642F73C67
Which is in the .txt file, but I thought that it should match the original SHA1 from Mega, which was:
SHA-1: 9a3efe6130ba21ab2ade9df38ff9d52a539d9693
PhoenixMiner did you modify the zip? Everyone else, do the internal files match the .zip from Mega?
My second question is regarding the files from PhoenixMiner.org, which I admit I have used and am coming to realize I need to be more careful about what I use. Do we know if those files are bad? The zip file is obviously different as they have added a bunch of .bat files to work with a lot of different pools. The phoenixminer.exe is also clearly different than what is in the 5.5c zip from github. Which for obvious reasons has me worried. So in summary:
Phoenixminer.exe from phoenixminer.org SHA1: 11428C3BDF728860FD057C411A95B14E13F05DBC
Phoenixminer.exe from github 5.5c win.zip SHA1: 5DC5405194097044854A28F2EABDD99E16A1517F
I am quoting someone who mentioned the SHA1 from what they thought was the .exe from the original mega file, which actually matches the .org one.