Outcome permalink

Outcome kFJkK9KAop

Verified sha256(serverSeed) reproduces the recorded serverHash.

Recorded parameters

Endpoint
GET /api/ints
Client seed
btc-0000000000000000000051e76cb37371ee3a0c92df90e16fb940007e7cd7b503
Server hash
91b770e05cca0ed81a62cb2a41de5b01596ce2e1dd7bc3053b2857da760b487e
Server seed
c7972fde7b78220648f6542366d67a5b64190e4917ba4a5ca40d1d63c1e6c7d0
Cursor
1000000434
Nonce
0
Count
12
Min
1
Max
420
Recorded at
2026-07-06T18:50:01.488Z

Outcome

111, 318, 193, 50, 401, 16, 275, 351, 345, 150, 388, 86

Permalink

How to reproduce this yourself
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-0000000000000000000051e76cb37371ee3a0c92df90e16fb940007e7cd7b503:0:<round>"), then map bytes to ints.
3. Confirm the public hash on the verify form: Open in /verify →
Reference implementation: @provableio/provable-core.

← Verify another outcome  ·  API docs →