Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-12 in hash.keys
sha256(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4) -> 0c1cc04ed84d47782d95653fe7b579fef7cd60c9cc52739b008bcb9c0842feb1
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4,08afacd78709a40ed92d4f53cdb02ef56543b91fc0b636e0a3be8a6567abd675) -> 00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 hmac512
Verify that the first bytes of the bet hash above is the lucky number
00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 -> 0049 -> 73
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-12 in hash.keys
sha256(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4) -> 0c1cc04ed84d47782d95653fe7b579fef7cd60c9cc52739b008bcb9c0842feb1
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4,08afacd78709a40ed92d4f53cdb02ef56543b91fc0b636e0a3be8a6567abd675) -> 00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 hmac512
Verify that the first bytes of the bet hash above is the lucky number
00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 -> 0049 -> 73
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-12 in hash.keys
sha256(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4) -> 0c1cc04ed84d47782d95653fe7b579fef7cd60c9cc52739b008bcb9c0842feb1
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4,08afacd78709a40ed92d4f53cdb02ef56543b91fc0b636e0a3be8a6567abd675) -> 00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 hmac512
Verify that the first bytes of the bet hash above is the lucky number
00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 -> 0049 -> 73
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-12 in hash.keys
sha256(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4) -> 0c1cc04ed84d47782d95653fe7b579fef7cd60c9cc52739b008bcb9c0842feb1
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4,08afacd78709a40ed92d4f53cdb02ef56543b91fc0b636e0a3be8a6567abd675) -> 00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 hmac512
Verify that the first bytes of the bet hash above is the lucky number
00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 -> 0049 -> 73
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-12 in hash.keys
sha256(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4) -> 0c1cc04ed84d47782d95653fe7b579fef7cd60c9cc52739b008bcb9c0842feb1
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4,08afacd78709a40ed92d4f53cdb02ef56543b91fc0b636e0a3be8a6567abd675) -> 00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 hmac512
Verify that the first bytes of the bet hash above is the lucky number
00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 -> 0049 -> 73
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-12 in hash.keys
sha256(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4) -> 0c1cc04ed84d47782d95653fe7b579fef7cd60c9cc52739b008bcb9c0842feb1
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4,08afacd78709a40ed92d4f53cdb02ef56543b91fc0b636e0a3be8a6567abd675) -> 00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 hmac512
Verify that the first bytes of the bet hash above is the lucky number
00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 -> 0049 -> 73
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-12 in hash.keys
sha256(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4) -> 0c1cc04ed84d47782d95653fe7b579fef7cd60c9cc52739b008bcb9c0842feb1
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4,08afacd78709a40ed92d4f53cdb02ef56543b91fc0b636e0a3be8a6567abd675) -> 00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 hmac512
Verify that the first bytes of the bet hash above is the lucky number
00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 -> 0049 -> 73
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-12 in hash.keys
sha256(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4) -> 0c1cc04ed84d47782d95653fe7b579fef7cd60c9cc52739b008bcb9c0842feb1
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4,08afacd78709a40ed92d4f53cdb02ef56543b91fc0b636e0a3be8a6567abd675) -> 00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 hmac512
Verify that the first bytes of the bet hash above is the lucky number
00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 -> 0049 -> 73
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-12 in hash.keys
sha256(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4) -> 0c1cc04ed84d47782d95653fe7b579fef7cd60c9cc52739b008bcb9c0842feb1
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4,08afacd78709a40ed92d4f53cdb02ef56543b91fc0b636e0a3be8a6567abd675) -> 00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 hmac512
Verify that the first bytes of the bet hash above is the lucky number
00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 -> 0049 -> 73
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-12 in hash.keys
sha256(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4) -> 0c1cc04ed84d47782d95653fe7b579fef7cd60c9cc52739b008bcb9c0842feb1
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4,08afacd78709a40ed92d4f53cdb02ef56543b91fc0b636e0a3be8a6567abd675) -> 00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 hmac512
Verify that the first bytes of the bet hash above is the lucky number
00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 -> 0049 -> 73
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-12 in hash.keys
sha256(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4) -> 0c1cc04ed84d47782d95653fe7b579fef7cd60c9cc52739b008bcb9c0842feb1
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4,08afacd78709a40ed92d4f53cdb02ef56543b91fc0b636e0a3be8a6567abd675) -> 00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 hmac512
Verify that the first bytes of the bet hash above is the lucky number
00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 -> 0049 -> 73
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-12 in hash.keys
sha256(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4) -> 0c1cc04ed84d47782d95653fe7b579fef7cd60c9cc52739b008bcb9c0842feb1
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(YIUQarPL71H43g2BKg8onH6xNr3ANSMsBYN1WHIF08MrdPFaCxBdscQ8KTu2uwn4,08afacd78709a40ed92d4f53cdb02ef56543b91fc0b636e0a3be8a6567abd675) -> 00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 hmac512
Verify that the first bytes of the bet hash above is the lucky number
00498815cb72522dc1ac3a1744616beed4e2e7ae4a57eed11c6755076e0e0552 -> 0049 -> 73