Outcome permalink

Outcome g2vQViOTdu

Verified sha256(serverSeed) reproduces the recorded serverHash.

Recorded parameters

Endpoint
GET /api/ints
Client seed
btc-000000000000000000012ecf3859fb16c7b0a660596c9375b48415518812fa72
Server hash
2ce81c703878ce016a75c63b4d1abd7734f1b36fbd2c4bae475afd5070a7bf88
Server seed
7306ea1a6436f3c0246c8f9f87f62af54f0c04e8b25bec4b6ce6f7eb32704b59
Cursor
1000000432
Nonce
0
Count
12
Min
1
Max
410
Recorded at
2026-07-05T01:00:01.598Z

Outcome

371, 70, 158, 232, 278, 360, 183, 334, 196, 347, 366, 365

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-000000000000000000012ecf3859fb16c7b0a660596c9375b48415518812fa72: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 →