NLNico is right, if you want a detailed explanation, you'll have to provide a detailed question. What site did you play on?
If you're playing on a well known site, it's probable that there was an error somewhere. However, if it was on a lesser known dice site, they could be cheating you. Most sites on bitcointalk without negative feedback are not scams, but it is not a 100% guarantee.
Topic: Need help trying to calculate provably fair (Read 838 times)
Which site is this? The HMAC hash is indeed a1fa2bd2f8..
I assume something goes wrong because of all the special characters in their serverseed. Or they are just cheating you (: If you share some more context, I can have a look.
PS, for anyone who wants to read a generic article about how the provably fair mechanism works, I made a simple tutorial here: https://dicesites.com/provably-fair
I assume something goes wrong because of all the special characters in their serverseed. Or they are just cheating you (: If you share some more context, I can have a look.
PS, for anyone who wants to read a generic article about how the provably fair mechanism works, I made a simple tutorial here: https://dicesites.com/provably-fair
Hi, im just trying to figure out how to properly check a sites provably fair system but it's not matching up for the first step and im not sure if if i'm making a silly error or if their system is broken.
So their first step is
Step One, Verifying the Server Hash:
We need to now verify the server hash was created using the server seed and client seed.
Lookup "Free HMac Generator" on Google, or use this one.
Inside the box that tells you to input your message, paste in the server seed. (Be sure it is the seed and not the hash).
In the box that asks for the secret, input the client seed.
Choose SHA512 as the digest algorithm.
Select Compute HMAC
You should see that the hash generated matches the server hash above.
The hash is generated by combining the client seed and server seed, so if the hash is the same, that means the seeds were never modified.
this is the seeds/hash provided by them
Server Hash cec18dd0048b631b322dfe1a3e7ba3d8f7aff63feb4c7cb7c5d3fd52aab38cf958d8d7e1f843a7f 2fd36ee46aa5f6ffc7a68bf2c276ff4b2bbadf4c47973dee2
Server Seed Hash 26ba67a1b7a47824aad2ac4298c8f68bcec8aa152018ba5a14dfd4933e99bb3b92ddb42b9c51b55 d6090b92d6db2dcda6aba673320b5a09c1661ed22499ac285
Client Seed TjgkkSmxN4mETvXA
Server Seed HG@[FlNqBfUcCZg&J8Kjo[1gWFARl3r9^n5XwKd%!JoNBIk6viaRKq)[oHE*toR2YI^*TE6Xd*B
however when i hash the client+serverseed i am getting a1fa2bd2f869638fb819a099b38151bc47037ae0bc89e27da521922fc32d690367c217b37ad651d bd9d2de43867048bf22f25c398c33d0f6aa8c3c335af29111
am i missing something?
So their first step is
Step One, Verifying the Server Hash:
We need to now verify the server hash was created using the server seed and client seed.
Lookup "Free HMac Generator" on Google, or use this one.
Inside the box that tells you to input your message, paste in the server seed. (Be sure it is the seed and not the hash).
In the box that asks for the secret, input the client seed.
Choose SHA512 as the digest algorithm.
Select Compute HMAC
You should see that the hash generated matches the server hash above.
The hash is generated by combining the client seed and server seed, so if the hash is the same, that means the seeds were never modified.
this is the seeds/hash provided by them
Server Hash cec18dd0048b631b322dfe1a3e7ba3d8f7aff63feb4c7cb7c5d3fd52aab38cf958d8d7e1f843a7f 2fd36ee46aa5f6ffc7a68bf2c276ff4b2bbadf4c47973dee2
Server Seed Hash 26ba67a1b7a47824aad2ac4298c8f68bcec8aa152018ba5a14dfd4933e99bb3b92ddb42b9c51b55 d6090b92d6db2dcda6aba673320b5a09c1661ed22499ac285
Client Seed TjgkkSmxN4mETvXA
Server Seed HG@[FlNqBfUcCZg&J8Kjo[1gWFARl3r9^n5XwKd%!JoNBIk6viaRKq)[oHE*toR2YI^*TE6Xd*B
however when i hash the client+serverseed i am getting a1fa2bd2f869638fb819a099b38151bc47037ae0bc89e27da521922fc32d690367c217b37ad651d bd9d2de43867048bf22f25c398c33d0f6aa8c3c335af29111
am i missing something?
Jump to: