# Create2

The [<mark style="color:purple;">`CREATE2`</mark>](https://eips.ethereum.org/EIPS/eip-1014) opcode lets us predict the address where a contract will be deployed beforehand. This opens up lots of possibilities to improve [<mark style="color:purple;">user onboarding and scalability</mark>](https://blog.openzeppelin.com/getting-the-most-out-of-create2/).

In Kinto, all our contracts use **CREATE2** to ensure proxy addresses are deployed to deterministic addresses. In practice, this means that given the same code and random number (*salt*) the contract will be deployed at the same address.

### Arachnid Proxy

To enable CREATE2 capabilities, we have deployed the Arachnid proxy to the following address.

`0x4e59b44847b379578588920ca78fbf26c0b4956c`

{% hint style="info" %}
To read more about how CREATE2 works under the hood, visit the [<mark style="color:purple;">following page from OpenZeppelin</mark>](https://docs.openzeppelin.com/cli/2.8/deploying-with-create2)<mark style="color:purple;">.</mark>
{% endhint %}


---

# 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.kinto.xyz/kinto-the-modular-exchange/building-on-kinto/rollup-features/create2.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.