> For the complete documentation index, see [llms.txt](https://docs.butter.markets/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.butter.markets/technical-docs/v1-dependencies.md).

# Dependencies

{% hint style="info" %}
This page lists the external contracts and services that v1 contracts depend on.
{% endhint %}

## Conditional tokens

Gnosis' [Conditional Token framework (archived)](https://web.archive.org/web/20241002172829/https://docs.gnosis.io/conditionaltokens/) provides the ability to create and manipulate tokens that are tied to a specific condition happening. `ConditionalTokens` is the core contract that manages among others the creation and redemption of conditional tokens.

The codebase also relies on `Wrapped1155Factory` which enables wrapping 1155 conditional tokens in ERC20s so participants can trade them on any AMM.

Both these contracts are re-deployed in their original and audited versions. We updated the build pipeline with modern tooling: see [here](https://github.com/butterygg/conditional-tokens-contracts) and [here](https://github.com/butterygg/1155-to-20).

## Reality.eth

[Reality.eth](https://reality.eth.limo) is the first oracle for which an adapter has been implemented.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.butter.markets/technical-docs/v1-dependencies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.