# 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 %}