> For the complete documentation index, see [llms.txt](https://woken-exchange.gitbook.io/wokenexchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://woken-exchange.gitbook.io/wokenexchange/security/audit-and-verifications.md).

# Audit & Verifications

**Woken Exchange** V1 is a fork of UniswapV2, which itself has been audited many times.&#x20;

The smart contracts we have created and modified are as follows:

* Creating the Timekeeper.sol smart contract
* Modification of WokenFactory.sol smart contract (from UniswapV2Factory.sol)
* Modification of WokenPair.sol smart contract (from UniswapV2Pair.sol)

**All functionalities have been thoroughly tested by Solidity - Assembly experts.**

Since our code is open source, anyone can audit it.

We plan to set up a bug bounty program and have the 3 smart contracts audited by a specialized company, according to the [Roadmap](/wokenexchange/protocol-and-tokenomic/roadmap.md).<br>

{% embed url="<https://github.com/WokenExchange/Contracts>" %}


---

# 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://woken-exchange.gitbook.io/wokenexchange/security/audit-and-verifications.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.
