> 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-3/conclusion.md).

# Conclusion

Well done for making it through this tutorial! You should have everything you need to begin creating zk circuits using Halo2. Of course there is still a lot to learn, and there are many different ways to implement circuits that we haven't covered. We believe you will discover some of those on your zk implementation journey, and you can find several more examples of code elsewhere (such as the examples folder in the halo2\_proofs folder in this repo)

We wish you the best on your journey!

### Improving this book

If you have any suggestions to help improve this book, please don't hesitate to contact us at <erroldrummond@pm.me>

### Acknowledgements

A big thank you to @Han0110, @Kilic and @CPerezz for their support in understanding the codebase well enough to create this mini book.


---

# 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-3/conclusion.md?ask=<question>&goal=<endgoal>
```

`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.