ChainCatcher message, Ethereum co-founder Vitalik Buterin pointed out in his latest article "A Deeper Dive into Cross-L2 Reads for Wallets and Other Use Cases" that a feasible solution for implementing cross-chain social recovery wallets is to maintain a key vault stored in a specific location, along with multiple wallets in different locations that can read the key vault. Cross-chain proofs are key to achieving this functionality and need to be deeply optimized. Feasible solutions include zero-knowledge proofs (ZK-SNARK), waiting for Verkle proofs, or custom KZG solutions.In the long run, we need to implement aggregation protocols that package all user-submitted operations by generating aggregate proofs to reduce costs. This may require integration into the ERC-4337 ecosystem, which might necessitate some modifications to ERC-4337. At the same time, to reduce the latency of reading L1 state from L2, L2 should be optimized.Wallets can not only be placed on L2 but also on systems with lower connectivity to Ethereum, such as L3 or independent chains that only agree to include Ethereum state roots. However, the key vault should be placed on L1 or high-security ZK-rollup L2. Although this increases complexity, setting up the key vault on L2 may be a more cost-effective solution in the long run. In this process, we also need to commit to protecting privacy. (Source link)