> For the complete documentation index, see [llms.txt](https://trueodds.gitbook.io/trueodds/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trueodds.gitbook.io/trueodds/dice-game/verifying-your-bet.md).

# Verifying your bet

The commit-reveal fallacy - and how you can know your bet is provably fair.

## Seeds and Hashes

When you attempt to beat the other party in our dice game (refer to [What is it?](/trueodds/dice-game/what-is-it.md#how-does-our-game-work)), and before the ICP transaction is asked for you to sign, you will be able to see your *hash* for said bet. Then, after the dice is thrown and the result is decided, you will be able to see the verifying info, which will contain your *hash* as well as that bet's *seed.* 

You will then be able to verify your bet by hashing your *seed.* That way you will be able to confirm that the seed that was used to throw the dice is the one that was shown (hashed) before payment was requested.

## How to hash your seeds

If you want to personally confirm your bet or build your own verifying tool, you can use the following SHA224 Motoko implementation to do so:

{% embed url="<https://github.com/flyq/motoko-sha224/blob/main/src/SHA224.mo>" %}

Steps to take:

* Install the DFINITY Developer SDK.
* Create a new canister (you can use `dfx new`)
* Call the `sha224()` in the SHA224.mo file and pass it your seeds.

### Verifying canister

Alternatively you can use our open-sourced verifying canister. Head to It's Candid interface and pass your bet seeds to the verify function.\
\
Candid Interface: <https://a4gq6-oaaaa-aaaab-qaa4q-cai.raw.ic0.app/?id=wyycy-oyaaa-aaaah-abjfq-cai>

If you don't want to interact with the live version, feel free to deploy your own instance of the Verify canister locally.

Code of the canister: <https://gitlab.com/trueoddsicp/verify-canister><br>