The PSE team introduced earlier is focusing on transforming and developing ETH privacy features as their main product research and development direction. Recently, the ETH PSE team shared the 2025 Roadmap, from which we can see several changes they are making. The Roadmap shows that PSE has shifted to a product-centric approach, which is a significant change compared to before. I looked at one of their Excel sheets, which listed over 280 privacy requirement scenarios, categorizing them, with each having a user scenario story, resembling the feel of a product development team, contrasting greatly with PSE's previous focus on cryptographic research. Key highlights from the 2025 Roadmap: - PSE upgrades to Ethereum's privacy steward - Focus on specific issues rather than pursuing flashy technologies - Centered on supporting the ecosystem rather than internal research projects - Concentrating on three main directions: 1/ Allowing information to be read from Ethereum without revealing identity or intent. (Private writing) 2/ Making private on-chain operations as cheap and seamless as public operations. (Private reading) 3/ Ensuring any data has privacy and accessibility. (Private proof) Short-term goals: 1/ Private transfers 2/ Voting protocols 3/ Institutional privacy solutions Additionally, while the demand for this type of infrastructure has not yet exploded, its importance will increase as institutions gradually move on-chain. The Polkadot parachain KSM has also shifted to a privacy-centric chain, while Quil, which is inherently privacy-focused, has been working hard towards version 2.1. Roadmap: User story: Projects supported by PSE:

RT @alacheng: After looking at Allora, I feel that the AI track really has its own characteristics. Among them, Sentient @SentientAGI is innovating in business models, model and community alignment, and model copyright protection, while 0G @0G_labs leans more towards AI blockchain (designed around AI characteristics) and the computing power aspect (decentralized computing power)...

Zama's fhEVM co-processor Three states: Public state / Off-chain state / Private state - (Public state) The states of traditional L1 blockchains are all public, lacking privacy. - (Off-chain state) ZK is off-chain state computation with on-chain proof, lacking composability for off-chain states. - (Private state) FHE is completely private state computation, with the private state being publicly available on-chain, allowing for composability between private states in on-chain contracts. Here, fhEVM has an authorization process, which is the encrypted state of the initial contract, managed through a threshold MPC protocol. The fhEVM co-processor runs FHE smart contracts on the EVM chain. - When a contract on L1 calls Zama's TFHE library to perform FHE operations, L1 itself does not perform any actual FHE computation but generates a pointer to the result. - The computation is then carried out by an off-chain server monitoring L1. - Developers can use Solidity and the fhEVM SDK to develop end-to-end encrypted dapps without needing cryptographic knowledge. - Everything done by the co-processor is publicly verifiable, and anyone can recompute the ciphertext to verify the results. - The fhEVM co-processor was initially operated by Zama, but will be opened up later (Zama FHE miners, take note). A simple application scenario: Composable on-chain identity DID: For example, your DID contract dapp, when you use an on-chain credit contract, the DID contract authorizes the credit contract with your permission, outputting your private identity state information (encrypted). The credit contract uses your DID information for risk assessment and interest rate evaluation in ciphertext state. This reflects the composability of ciphertext state (privacy) + FHE EVM contracts under ciphertext state computation. ZK is the verification/proof engine for secrets and computation. FHE is the computation engine under ciphertext state.