Recorded parameters
- Endpoint
GET /api/ints- Client seed
btc-0000000000000000000170249ddcae6a6e84a1613cd86728753cb8fbe5f7efa6- Server hash
4103a31ac50a9a8720b8f8c4bc0ee03659ef4be80ce71f03091ff7f99ad632af- Server seed
ba5007c17667112db1435c468f937f6f8266151e811718aea6d1eb649fc8f88f- Cursor
1000000436- Nonce
0- Count
12- Min
1- Max
30- Recorded at
- 2026-07-06T20:20:01.461Z
Outcome
17, 13, 17, 15, 20, 25, 10, 25, 3, 28, 11, 1
Permalink
How to reproduce this yourself
1. Confirm the server hash:
2. Re-derive the values: HMAC-SHA256(serverSeed,
3. Confirm the public hash on the verify form: Open in /verify →
Reference implementation: @provableio/provable-core.
1. Confirm the server hash:
sha256(serverSeed) === serverHash — try it now with the revealed serverSeed above.2. Re-derive the values: HMAC-SHA256(serverSeed,
"btc-0000000000000000000170249ddcae6a6e84a1613cd86728753cb8fbe5f7efa6:0:<round>"), then map bytes to ints.3. Confirm the public hash on the verify form: Open in /verify →
Reference implementation: @provableio/provable-core.