# ZK Proof

We have one last thing to investigate - the zk proof generation of the gameplay procedure.

Now click the "Game Proof" button on the top header of this page:

<figure><img src="/files/ZkdQMWYAK716EhNmYCGC" alt=""><figcaption></figcaption></figure>

You will see a popup window like this:

<figure><img src="/files/JyBAae4oAjNQpWjzFTbz" alt=""><figcaption></figcaption></figure>

This is the step history record window of your gameplay. After you play some steps, it will become:

<figure><img src="/files/jy8ES2b1QdO2JXGIkeb7" alt=""><figcaption></figcaption></figure>

Every square like "3:i64" is a step record of this gameplay. And while you end this game, such like:

<figure><img src="/files/iQ9dGeauwgJmeFVNOb9i" alt=""><figcaption></figcaption></figure>

Check the game proof window:

<figure><img src="/files/3lUPZOHtq323Pso4tijS" alt=""><figcaption></figcaption></figure>

The steps increased, and right now we can create a proof for it.

Click the red button at the right-bottom corner. A wallet popup will be triggered, like:

<figure><img src="/files/zRCakrmctSGYu24OUILy" alt=""><figcaption></figcaption></figure>

After the signing process, it will generate a zk proof for this gameplay and submit it to the Blade game server.

<figure><img src="/files/uCjkkmBc8hERJqJFq8Qe" alt=""><figcaption></figcaption></figure>

Now we have finished the entire ZK game development flow, next you can make your own game according to this guide. Good luck!


---

# 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.bladedao.games/zkunity-game-engine/zkunity-guide/demo-a-roguelike-card-game/zk-proof.md?ask=<question>
```

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.
