AztecShield RPC Proxy

Aztec
,
1

AztecShield RPC Proxy

Summary

AztecShield is a privacy-preserving RPC proxy for Aztec’s Layer 2 testnet, tackling the leakage of user data—IP addresses, wallet addresses, and transaction intent—in standard RPC services. Built on my high-performance RPC client (2300+ blocks/second), it might integrates Hopr’s mixnet (not really sure about the full technical details for now, need more research tbh) about the for anonymous routing and zk-encryption to secure requests, ensuring nodes see nothing sensitive. The demo is a lightweight CLI tool: users send private transactions (e.g., deposits) or query state (e.g., balances), all anonymized by the proxy. Unlike bridge-focused proposals, AztecShield targets Appendix 1’s call for privacy-preserving RPC providers, enhancing Aztec’s infrastructure.

Launching with Aztec’s Q1 2025 testnet, it uses a semi-trusted proxy (I host it initially) with a roadmap to decentralize via community nodes. Challenges include mixnet latency (offset by connection pooling) and adapting my EVM client to Aztec’s zk-state (tested via Sandbox). The flow is straightforward: encrypt a request locally, route it through AztecShield, and get a private response—e.g., aztecshield query balance hides all traces. It’s lean, fast, and purpose-built for privacy.

As a solo dev, I bring proven RPC skills and a drive to bolster Aztec’s privacy mission. AztecShield delivers a reusable tool for developers and wallets, preventing metadata leaks at the network layer. Starting April 1, 2025, I’ll ship an MVP by June 2025, with plans for mainnet and broader adoption. This isn’t a bridge—it’s a foundational step to secure Aztec’s ecosystem, aligning with the RFGP’s vision of private, unified Ethereum.

Start and End Date

  • Start: Tuesday, April 1, 2025
  • End (MVP): Monday, June 30, 2025 (functional version on Aztec testnet)

About

I’m Malik, a solo blockchain developer with crafting efficient RPC tools. My Ethereum RPC client(GitHub - malik672/palantiri: A super fast ethereum rpc client), hitting 2300+ blocks/second with zero-copy parsing. Self-taught in dev, saw this late but this is really something I would like to take on and deliver a lean, impactful proxy and contribute it to the ecosystem, pushing Ethereum’s private future.

Grant Amount Requested

US$25,000

Details

  • Demo App: CLI tool for private transactions (e.g., deposits) and state queries (e.g., balances).
  • Proxy Design: Hopr mixnet routing + zk-encryption. Semi-trusted (my node) for MVP, with trustless roadmap.
  • Why This: Directly solves RPC privacy leaks (per Appendix 1), leveraging Hopr for speed.
  • Requirements: Masks IP, address, and intent, meeting RFGP’s privacy focus.
  • Technical Hurdles:
    • Mixnet delays—handled by pooling.
    • Aztec adaptation—via Sandbox/Aztec.nr.
  • User Flow:
    1. Run aztecshield tx --deposit 5.
  • Unique Edge: 2300+ blocks/second speed with privacy, shipped as an open-source CLI.