Show Posts
So I take it this isn't provavbly fair in anyway?
I looked at your site and found the script is
Int64 hashCode = 0;
if (!string.IsNullOrEmpty(hash))
{
byte[] byteContents = Encoding.Unicode.GetBytes(hash);
SHA256 hash = new SHA256CryptoServiceProvider();
byte[] hashText = hash.ComputeHash(byteContents);
Int64 hashCodeStart = BitConverter.ToInt64(hashText, 0);
Int64 hashCodeMedium = BitConverter.ToInt64(hashText,
;
Int64 hashCodeEnd = BitConverter.ToInt64(hashText, 24);
hashCode = hashCodeStart ^ hashCodeMedium ^ hashCodeEnd;
hashCode = Math.Abs(hashCode);
}
return (int)(hashCode % 29) + 1;
However where does it get those hashes from ?
I looked at your site and found the script is
Int64 hashCode = 0;
if (!string.IsNullOrEmpty(hash))
{
byte[] byteContents = Encoding.Unicode.GetBytes(hash);
SHA256 hash = new SHA256CryptoServiceProvider();
byte[] hashText = hash.ComputeHash(byteContents);
Int64 hashCodeStart = BitConverter.ToInt64(hashText, 0);
Int64 hashCodeMedium = BitConverter.ToInt64(hashText,
;Int64 hashCodeEnd = BitConverter.ToInt64(hashText, 24);
hashCode = hashCodeStart ^ hashCodeMedium ^ hashCodeEnd;
hashCode = Math.Abs(hashCode);
}
return (int)(hashCode % 29) + 1;
However where does it get those hashes from ?
Not sure if the script is correct, but based on the OP, the hashes are gotten from the bitcoin blockchain, from newly mined blocks. If adaseb has the correct script, you need to use hashCode % 30, not 29 and than add 1. Looks to me like it's provably fair.
29 % 29 gives 0, making #30 impossible to get, while 29 % 30 gives 29 which when one is added to, makes 30.
Yes, you're right. In application on server is that number represented by operator. In configuration this operator is 30. It was mistake only in text on web.
I checked database and number 30 was calculated in some blocks. For example in 448800. I corrected text on website. Thanks for warning.
