> For the complete documentation index, see [llms.txt](https://erroldrummond.gitbook.io/halo2-tutorial/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://erroldrummond.gitbook.io/halo2-tutorial/section-2/proper-proving.md). # Proper proving In the last section we made use of the mock prover. Now we would like to go further and use a more advanced prover that will do each step independently (prover/verifier key generation, proof generation, verification). ### Keys In order to go through the full process of proving, we are going to need to create verifying and proving keys. If you went through the preliminaries you should recall that the verifying key is needed in order to check the correctness of a proof. It essentially contains info about what circuit the proof is referring to (where is each gate and how are they connected?). The proving key essentially consists of the filled out circuit, from which we can create the proof. #### Verifying key Since we don't need to know any of the wire values to create the verifying key, we can supply an empty circuit - i.e. all `Value`s are `unknown`. We also need to prepare some parameters that are going to be used by the proof system to make these keys. #### Proving key --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://erroldrummond.gitbook.io/halo2-tutorial/section-2/proper-proving.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.