In this call, we covered two major areas: (1) builder → proposer payment design, (2) fork choice signaling, and briefly discussed alternate designs and slot time implications. 1. Builder → Proposer Payment The current 7732 spec changes the builder-to-proposer payment flow in a way that may break existing staking pool contracts, requiring them to rewrite and re-audit their infra. We discussed two simple alternatives to preserve compatibility: Pay to the proposer’s withdrawal address Add a new field in the bid to specify a fee recipient (similar to validator registration today) Both options keep the payment within the CL, not EL. Lido (on the call) indicated this would be sufficient for their needs.

⏳ Genesis time related questions: Q: Is there any estimate time for the genesis of Oynx? A: Not yet, the deposit contract needs to hit the threshold of 16384 deposits then wait for 48 hours until genesis. ✉️ Deposit related questions: Q: If there is anyway to get back the GoETH I deposit in the topaz testnet with the shardwithdrawalkey ? A: There is no way to get back that GoETH. Deposits into eth2 phase 0 are one-way Q: https://prylabs.net/participate still sends ETH to old contract. A: Try clearing your browser cache

Author: Terence Tsao (terence@prysmaticlabs.com) :wave: Background In the current Ethereum road map, Ethereum2.0 (ETH2.0)'s phase 1 implements sharding of data. As the phase 1 spec continues to mature, evolve and improved by the researchers and the community members. There's great value and synergy to begin implement a phase 1 proof of concept client that aims to serve many great purposes. Prysm from Prysmatic Labs is the phase 0 beacon chain implementation in Golang. The project consists of implemenations of beacon node and validator client. Both implementations are aiming to be production ready as beacon chain goes mainnet starting day 0. As we are heading towards the mainnet production readiness phase for phase 0, it naturally makes sense to begin and explore experimental phase 1 functionality using Prysm. :goal_net: Outlined Goals Implement shard chains that get built along side beacon chain in run time, shard chains should be crosslinking with the beacon chain Implement benchmarks on what is feasible and what is not feasible with design decisions outlined in the spec

Author: Terence Tsao Objective In this page, we aim to achieve an end to end design between BN RPC server and VC RPC client so that BN can properly subscribes to attestation subnet such that: BN serving attester can find persistent peers on the subnet in question to publish attestation BN serving aggregator can join the subnet Required readings for background https://github.com/ethereum/eth2.0-specs/pull/1615