[Ethereum Developer Barry Releases New Progress on zkEVM Private Smart Contracts: Supports Private User States, But Lacks Private Global States] According to a report by Jinse Finance, Ethereum developer BarryWhiteHat stated in a post that with the commercialization of zero-knowledge proof virtual machines (zkEVM), an interesting opportunity has emerged: providing private smart contract infrastructure while maintaining compatibility with the Ethereum Virtual Machine (EVM). Developers can write Solidity code and compile it using a specific version of the Solidity compiler or some post-processing tools to create private smart contracts. There are significant trade-offs between private global states and privacy, with the core issue being that to generate a proof, one must know what is being proven. Therefore, it is impossible to have a private smart contract with a global public state that you are unaware of. Consequently, private smart contracts with private global states cannot exist. For example, applications like Uniswap cannot be implemented in a private form because the prover needs to know the balances of the two liquidity pools to prove that a swap transaction is executed correctly. As a result, some of the applications we are familiar with and favor cannot currently be implemented in a private form unless we have input-output (IO) functionality — which is precisely why IO is critical. It allows us to build a fully private Ethereum with trust assumptions entirely consistent with native Ethereum. However, this article aims to explore how to achieve a type of private smart contract — one that has private user states but lacks private global states — by adding the `pstore` and `pload` opcodes to `reth` and compiling them into the zero-knowledge proof virtual machine (zkEVM).