In smart contract development, a proxy contract is a contract that holds the state and the public contract address of an application but delegates its logic to a separate implementation contract. On EVM chains it uses the delegatecall instruction, which runs the implementation's code in the proxy's own storage context. Replacing the implementation address changes the behaviour without moving users' balances or data, which is the main route to smart contract upgradeability.
Common patterns include the transparent proxy, where only an admin can call upgrade functions; the UUPS pattern, where the upgrade logic lives in the implementation; and the beacon proxy, where many proxies read their implementation from one beacon. EIP-1967 standardised the storage slots that hold the implementation address. The main risk is control: whoever holds the admin key can change the code. Projects reduce this smart contract risk with timelocks, a multi-sig wallet or governance votes.
Ref 1070001358