# Can't initialize state variable in proxy contract on deployment in UUPS pattern **URL:** \ **Category:** Contracts\ **Tags:** proxies, upgrades, truffle, openzeppelin-contracts\ **Created:** [June 6, 2022, 12:26pm UTC](https://forum.openzeppelin.com/t/cant-initialize-state-variable-in-proxy-contract-on-deployment-in-uups-pattern/29401 "2022-06-06T12:26:44Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Skyge](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/skyge/32/343_2.png) [@Skyge](https://forum.openzeppelin.com/u/Skyge)\ **Post date:** [June 7, 2022, 1:45am UTC](https://forum.openzeppelin.com/t/cant-initialize-state-variable-in-proxy-contract-on-deployment-in-uups-pattern/29401/2 "2022-06-07T01:45:29Z")
Hi, welcome to the community! 👋 I think if you want to use the UUPS pattern, you should specify it, cause there are two patterns: Transparent Proxy and UUPS. And maybe you can have a look at this tutorial: > [@UUPS Proxies: Tutorial (Solidity + JavaScript)](https://forum.openzeppelin.com/t/uups-proxies-tutorial-solidity-javascript/7786): > > UUPS Proxies: A Tutorial In this tutorial we will deploy an upgradeable contract using the UUPS proxy pattern. We assume some familiarity with Ethereum upgradeable proxies. Introduction to UUPS The original proxies included in OpenZeppelin followed the [Transparent Proxy Pattern](https://blog.openzeppelin.com/the-transparent-proxy-pattern/). While this pattern is still provided, our recommendation is now shifting towards UUPS proxies, which are both lightweight and versatile. The name UUPS comes from [EIP1822](https://eips.ethereum.org/EIPS/eip-1822), which first documented the pattern. While both … --- _[View the full topic](https://forum.openzeppelin.com/t/cant-initialize-state-variable-in-proxy-contract-on-deployment-in-uups-pattern/29401)._