Cover photo

Google Cloud Integrates Self ZK Passport

Self Protocol's proof-of-humanity zero-knowledge proofs (ZKPs) will be integrated into Google Cloud products to combat bots and ensure fair access for real humans.

Quick Take

  • Google Cloud integrates Self Protocol.

  • MEV tradeoffs in Glamsterdam EIPs.

  • Safe releases research on Cosigners.

  • Increase in validator exit queue.

Google Cloud Integrates Self ZK Passport

Self Protocol, a ZK-powered onchain identity platform, announced a partnership with Google Cloud to integrate its proof-of-humanity zero-knowledge proofs (ZKPs) into its products. Google Cloud’s Web3 Testnet Faucet will use Self to block bots and ensure fair access for real humans. A Mainnet Faucet will also leverage Self for both sybil resistance and privacy-preserving OFAC compliance. Google is also incorporating Self into its AI-enhanced Web3 tools, allowing verified human users to bypass strict rate limits in blockchain-aware AI systems, ensuring smoother access to AI resources for real humans. The collaboration aims to support privacy-first development. Self allows individuals to prove their identity without exposing sensitive data. Self is built with zk-SNARKs and uses onchain attestations on Celo.

MEV Tradeoffs in Glamsterdam EIPs

Researchers Hasu and Data Always published an MEV-focused analysis of key EIPs in the upcoming Glamsterdam upgrade, highlighting their tradeoffs for block building, auction design, censorship resistance, and decentralization. They conclude that Block-level Access Lists (BALs, EIP-7928) are unambiguously beneficial for the execution layer, although they come with increased bandwidth requirements. In contrast, the consensus-layer proposals, ePBS (EIP-7732), Reduced Slot Times (EIP-7782), and Fork-Choice Inclusion Lists (FOCIL, EIP-7805), each involve significant tradeoffs with no clear winner.  ePBS could improve MEV markets but introduces the Free Option Problem, increasing the risk of empty blocks. Reduced Slot Times may improve user experience but could hurt geographic decentralization by pressuring validators to co-locate. And FOCIL aims to enforce censorship resistance but offers limited protection for the types of transactions most at risk today.

Safe Research Introduces Cosigners

Safe, the largest smart wallet provider, published a research article on Cosigners, independent agents that perform offchain transaction checks, sign verified transactions, and work with Safe Guards to create a transaction-level safety net. The proposed solution addresses issues with blind signing and overreliance on user interfaces, which are common attack vectors. Cosigners analyze and verify transactions before they can be executed. The mechanism is enforced onchain through the Safe Guard, a security module that applies custom logic to each transaction. Safe notes that projects like Failsafe, Blockaid, and Hypernative Guardian offer hosted cosigner services. However, Safe believes that self-managed Safe Cosigners can enable active, verified transaction filtering along with programmable and economically incentivized safeguards.

Validator Withdrawal Queue Increases

The Ethereum validator exit queue has surged in recent weeks, with approximately 630,000 ETH now awaiting withdrawal from the Beacon Chain, according to data from Rated.Network. Although new validators continue to join the network, withdrawals are currently outpacing deposits by around 280,000 ETH. The queue is due to a protocol-level limit on the number of partial and full withdrawals allowed per slot. The wait time for a full exit is now approaching three weeks.

Glamsterdam Updates

Ethereum Ecosystem

US vs Storm

Incentives

Instiuttional

  • iShares Ethereum ETF $8.5b in 1yr

  • BitMine begins options trading

Disclaimer: Content is for informational purposes only, not endorsement or investment advice. The accuracy of information is not guaranteed.