I happened to see the sharing image of the live PPT in the zk technology community. Can you briefly explain it, This 40 second video is a demo demonstration of zk technology by ETH Foundation researcher @ drakefjustin on @ eth_deofs demo day. It mainly demonstrates that Justin's zkLighthouse client does not need to be re executed, that is, as long as a ZK proof is verified, it can confirm whether the entire ETH block is executed correctly. If this is placed on the main network, it means that zk becomes the execution layer of ETH (there is no need to perform verification between nodes, only the generated zk proof needs to be verified), and zk becomes the execution layer of L1. (But this estimate is still quite some time away from the actual mainnet, can it be released in 26 years?)? The following image should be a partial PowerPoint presentation for sharing: -This is a multi-party ZK proof cluster -Unified proof aggregator（ http://ethproofs.org ） -Gossip Release Network -The complete pipeline of client validators (such as Lighthouse) Left: The blue area on the left lists 7 different proof cluster providers, each of which is calculating and generating ZK proofs. Each cluster represents a team's prover, including @ brevis_zk, @ SuccinchLabs, and so on middle: http://ethproofs.org (Proof aggregation node) -This is a unified proof collector&aggregator: -Receive proof from all provers -Broadcast proof to gossip network Ethproofs gossip node This is a proof forwarding node in the P2P gossip layer: 1/From http://ethproofs.org receipt confirmation 2/Spread to all subscribers through the gossip network ExecutionProofs subnet This is a subnet specifically designed for Execution Layer ZK Proofs. The function is: 1/Continuously receive gossip proofs 2/Responsible for classification, deduplication, and ensuring the validity of proof 3/Open subscription interface to clients 4/Final: Justin's zkLighthouse (Client Validator) 5/This is a modified Lighthouse (ETH client) that supports verifying ZK Execution Proof. It is achieved through: Subscribe → receive proof of ExecutionProofs subnet Local verify → Verify ZKP locally on the client side Replace or enhance existing Execution Layer validation Final objective: To use ZKP proof to verify the correctness of Ethereum block execution (i.e. ZK-EVM for Ethereum Core) Overall process: Multiple prover clusters producing execution ZK proofs in parallel 1/proofs → http://ethproofs.org 2/ethproofs.org → gossip → ExecutionProofs subnet 3/zkLighthouse client subscription to subnet 4/Client local verification ZK proofs 5/Complete implementation of decentralized, verifiable, and trustless Ethereum block execution proof