# Staking For on-chain games, players will be asked to use their wallet to sign a **Stake** to enter a match. The **Stake** object is an EIP712 record () that guarantees later payment of entry fee.
In this example, the payload you are being asked to sign includes all the typical EIP712 security features (these are discussed in more detail in [Networking + Security](/hangman/networking-+-security.md)), as well as an **amount** and **fee**. These are in Wei.
Because this payload is an EIP712 payload, Metamask and other wallets are able to type check and present a nice UI. Once signed, the Hangman server hangs onto this signature. On completion of the match by both parties, the Hangman server submits both player's signed stakes, as well as the winner to the [Game Wallet](https://github.com/spyre-io/game-wallet) contract. The contract itself is responsible for verifying the stakes and awarding players. On Base Mainnet, the contract resides [here](https://basescan.org/address/0x8de63e674fcb47ec596b6320e091a9aa972cf077). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.hangmanclash.com/hangman/matchmaking/staking.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.