Request for Grant Proposals: Cross Chain Bridges | Up to US$150,000

It is time to unify Ethereum - privately.

Top teams are invited to build on Aztec’s privacy-preserving Layer 2 to create cross-chain applications that extend its privacy and decentralization guarantees to all major L2s. With up to US$150,000 in funding, the goal is to help pioneer the next generation of private, scalable, and interoperable solutions.

This is just the beginning of Aztec’s broader mission to bring privacy to all Ethereum chains—something we believe is critical for mass adoption. Over the past eight years, Aztec Labs has been refining Layer 2 privacy and scalability, starting with zk.money in 2021, and followed by Aztec Connect and Noir in 2022, culminating in the upcoming public testnet launch happening later this year.

With how mature ZK and account abstraction have become, it’s the perfect moment for talented builders to leverage Aztec’s unique execution environment—private and public states, seamless composability between private and public functions, and native account abstraction—to prevent further liquidity fragmentation and accelerate the future of Ethereum.

Submit your proposal on or before Sunday 23 March 2025 for a chance to receive funding and support. For more inspiration, check out Appendix 1 on Potential Areas of Interest. Together, let’s unify Ethereum—privately.

:warning:
EDIT
This deadline has now passed. Winners of this grant will be announced by 11th April 2024
:warning:

The Aztec L2 roadmap:

Grant Details and Submission Format

We are excited to support teams in their journey to build on Aztec. We will provide stipends of up to US$50,000 per team to help offset the costs of research and development. We are particularly interested in teams with a long-term vision for privacy, the Aztec ecosystem and a commitment to contribute to the Aztec stack and developer community.

To ensure consistency and facilitate the review process, please adhere to the following submission format:

Title: Team/product name
Contact Details: How can we contact you? (Signal, email, etc.)
Summary: In 300 words or less, describe the cross-chain app you want to bridge, the other L2 Testnet you will connect to and the kind of bridge you want to build.
Start and End Date: It is recommended that work starts on Tue 1 April 2025 and require a functional version be released on the Aztec Testnet by June 2025.
About You: A short paragraph with details about your team’s background, relevant experience and expertise. Show us that you have what it takes and why you are best placed to execute the long-term mission of creating an interop solution to bring privacy to your favourite L2!
Details you should cover:

  1. The cross-chain app you plan to demo
  2. What kind of bridge you will build and why
  3. How the design will meet the requirements
  4. Technical hurdles that will need to be overcome
  5. The user flow and journey

Make this section unique and try to stand out from other proposals. You could even write an example bridge contract or show a UI to stand out!

Grant Milestones and Roadmap: Submit a timeline and milestones to deliver on the requirements. We expect 3-5 milestones to get to an MVP-ready cross-chain app deployed between Aztec’s testnet and another L2, and 2-3 items dedicated to future work (post-launch improvements, feature additions, and mainnet launch). Please indicate your longer-term roadmap and how you want to keep building in the long run.
Grant Amount Requested: Any grant requests over US$50,000 will be immediately rejected. Successful projects may get further grant support post-launch, although it is not guaranteed.
Grant Budget Rationale: Explain comprehensively why you are requesting the amount of funds, and how it relates to milestones and timelines.
Questions: Any outstanding questions. Any confidential questions can also be sent to rahul[at]aztec-labs[dot]com

Submissions should be created as a new post on this forum, tagged bridge and rfgp. Once the new post is created, please refer back to this RFGP and post the link to your proposal as a comment.

Please submit proposals by Sunday 23 March 202.

Requirements

  • Bridge to another L2 testnet
  • Cross-chain demo app
    • A UI for executing transactions in Aztec or another L2 from Aztec – read below for example flows.
  • Bridge design:
    • What kind of bridge do you want to build? Detail your trust assumptions. Trusted parties are acceptable for this MVP, but your roadmap should include a path to remove single points of failure (e.g., via RIP 7755, a light client approach, or ZK proofs). For additional information refer here.
  • Flows:
    • Private deposit into Aztec from any chain.
    • Private withdrawal from Aztec to another L2 to execute a cross-chain intent.
    • Public deposits and withdrawals (optional).
    • Note: give extra thought to the withdrawal flow from Aztec, since a user would withdraw to execute cross-chain intents.
    • An example app could be a flow like
      • Control assets on another chain via a private multisig on Aztec
      • Maintain zk proof of passports on Aztec and use that for credit scores or other regulatory features apps on public L2s require to get institutional adoption.
      • Simply paying someone privately on another L2.
      • Proving an NFT ownership on another chain to get access to special items.
    • Some more sample flows are mentioned in the additional context document.
  • Gas Fee Management:
    • Your solution should sponsor gas fees for users on Aztec. Refer to additional context document here.
    • Our solution should sponsor gas fees for the other L2 (e.g., EIP-7702/4337) (optional).
  • Edge Cases:
    • Outline how you’ll address cancellations, L2 re-orgs, refunds for solvers or other edge cases you can think of.
  • UX:
    • Outline how you plan to mitigate UX, pre-confirmations and expected bridging time. Using EIP-7702 or 4337 makes it so only one transaction is needed on each chain.
    • In the short term, a user would need both an EVM wallet and an Aztec wallet. Long term, it should move to users requiring just 1 wallet (which can generate relevant permits for Aztec transactions).

A deeper understanding of the types of bridges Aztec can support will clarify these requirements. Please refer to the following document with additional context for further details.

FAQs

Are there existing wallets, explorers, and L1 token bridges for Aztec testnet already?
At launch, we anticipate testnet to have several wallets, explorers, and L1 to L2 bridges live.

Is Aztec EVM-compatible?
No, but it is a Turing-complete smart contract environment that allows for both public and private execution. Read more here.

Where do we build this? When testnet and mainnet?

  • You will start working on the Sandbox, a local development environment (most similar to Anvil of Ethereum) along with Aztec.nr smart contracts and TXE (our testing toolkit).
  • A decentralized testnet is expected to go live in Q1 2025.
  • Mainnet Ignition is expected to happen by mid-2025.

Are there any smart contract standards?
The Aztec Labs’ monorepo also has some sample contracts and apps.
DeFi Wonderland has also recently started working on contract standards here

Do I need ALL the requirements done by the June deadline?
No. We only need a minimal working cross-chain app deployed to testnet by June 2025. You don’t have to fulfill all requirements, but please provide a roadmap showing priorities and timelines. We expect at least one milestone to come after the deadline. Throughout the process, you’ll work closely with Aztec Labs and our ecosystem to address blockers and iterate.

Do you have a preference for certain L2 testnets?
No! All of Ethereum is one.

Any EIPs for standards that I need to follow?
No! This is intentionally EIP/ERC/RIP agnostic.

What kind of bridges can I build?
Refer to this doc for additional context.

What should I know about Aztec to build a good bridge?
Refer to this doc for additional context.

Appendix 1: Potential Other Areas of Interest

  • UMA’s Optimistic Oracle - create an Aztec variant to this or integrate UMA’s Optimistic Oracle into the Aztec testnet. This is useful for prediction markets, bridges, and generic dispute resolution.
  • Blocknative’s gas.network - extend it to have Aztec support. Bridges want to charge fees based on gas fees of the other network. This either requires a trusted oracle (provided by the filler) or ideally some onchain contract that tells you the gas situation in the other chain. Blocknative’s gas.network is exactly that.
  • Privacy-preserving RPC providers - RPC services are useful to send a user’s transaction to a node or to query state information. However, this leaks to an RPC what a user wants to do, their address, and IP address. Consider integrating a mixnet like Hopr or building a privacy-preserving RPC proxy.
  • FPC (Fee Payment Contracts) - most similar to paymasters in EVM land. FPCs act as the fee payer on behalf of the end user and instead allow users to pay fees in any token they accept. Through FPCs, users could also pay fee privately and accept refunds from sequencers without leaking their address. Read more here.

Disclaimer

The published request for proposal and ideas herein are explicitly published as discussion points to invite community feedback in the community forums. Robust design and developer discussion is the best way for the community to collectively secure and govern the network as well as ensure cross-chain interoperability. Any ultimate governance and cross-chain designs will be a result of the analysis and feedback of the community.The information set out herein is for discussion purposes only and does not represent any binding indication or commitment by Aztec Labs and/or affiliates and their employees//consultants to take any action whatsoever, including relating to the structure and/or any potential operation of the Aztec protocol or the protocol roadmap. In particular: (i) nothing in this post (and any response to this post) is intended to create any contractual or other form of legal, investment, financial, tax or advisory relationship between Aztec Labs or third parties who engage with such posts (including, without limitation, by submitting comments, a proposal and/or responding to posts including any medium such as X, Discord, etc), (ii) by engaging with any post, the relevant persons are consenting to Aztec Labs’ use and publication of such engagement and related information on an open-source basis (and agree that Aztec Labs will not treat such engagement and related information as confidential), and (iii) Aztec Labs is not under any duty to consider any or all engagements, and that consideration of such engagements and any decision to award grants or other rewards for any such engagement is entirely at Aztec Labs’ sole discretion. Please do not rely on any information on this forum for any purpose - the development, release, and timing of any products, features or functionality remains subject to change and is currently entirely hypothetical. Nothing on this forum post should be treated as an offer to sell any security or any other asset by Aztec Labs or its affiliates, and you should not rely on any forum posts or content for advice of any kind, including legal, investment, financial, tax or other professional advice.

13 Likes

:globe_with_meridians: Introducing Our Proposal: Confidential Cross-Chain Bridging for Aztec :rocket:

We’re excited to share our proposal for a privacy-preserving, trust-minimized cross-chain intent execution framework connecting Aztec with Optimism, Arbitrum, or any other Ethereum-settled L2s.

Our approach focuses on enabling both public and private intents, leveraging ERC-7683, Aztec Portals, and Ethereum storage proofs to ensure solvers can only claim funds after proving execution.
The design introduces a solver-based model that avoids centralized intermediaries and liquidity fragmentation, aligning with Aztec’s vision of confidential, gas-efficient, and scalable cross-chain interoperability.

We look forward to your feedback and insights! :page_facing_up::backhand_index_pointing_down:

Read the full proposal

2 Likes

Proposal to Integrate Aztec into the TRAIN Protocol

The TRAIN Protocol uses an intent/solver based system secured by Atomic Swaps and Local Verification. This ensures uniform, trustless security across all chains. This allows any network to integrate under the same security framework, enabling infinite scalability.

We are excited to bring confidential cross-chain bridging with Aztec.

Read the full proposal.

1 Like

:rocket: Introducing Our Proposal: Cross-Chain Messaging for Aztec :globe_with_meridians:

We just published our proposal for a Cross-Chain Messaging Infrastructure, enabling seamless interoperability between Aztec and other L2s.

:small_blue_diamond: Built on ERC-7683 Cross-Chain Intents
:small_blue_diamond: Supports privacy-preserving transactions
:small_blue_diamond: Enables secure bridging, cross-chain DeFi, and more

Our approach starts with a fast centralized prototype, evolving into a fully decentralized model to align with Aztec’s vision of private and efficient cross-chain execution.

We’d love your feedback! :page_facing_up::backhand_index_pointing_down:

Read the full proposal here

5 Likes
2 Likes
1 Like

Proposing to enable native Bitcoin along with EVM L1 & L2s cross-chain swaps to Aztec.

Garden is the fastest Bitcoin bridge currently, enabling cross-chain swaps in as little as 30 seconds. It is built using an intents-based architecture with trustless settlements, ensuring zero custody risk for users. To date, we have processed over $1.16 billion in swap volume on the mainnet.

In the first phase, since the proposal guide suggests building Aztec to EVM L2s bridging on the testnet, we built a testnet dApp to give an experience of the swap flow at testnet.garden.finance (supports bridging between Ethereum Sepolia, Base Sepolia, Arbitrum Sepolia, Citrea Testnet, Bitcoin testnet 4, and Monad Testnet), the flow for Aztec would be the same.

Looking forward to feedback on the complete proposal here.

1 Like

The Blocksense team proposes to develop a general-purpose bridge mechanism that will enable deep interoperability with any chain connected to the Blocksense Network (over 40 testnets at the moment).

We intend to demonstrate the capabilities of the bridge by developing an ERC-7683-based cross-chain swaps DApp, as well as remote management of funds through an Aztec private multi-sig.

We are looking forward to your feedback on our full proposal.

3 Likes
1 Like

RaidGuild brings the right combination of expertise, experience, and execution ability to develop a bridge to connect Aztec to the OP Superchain.

We intend to extend Aztec’s privacy to Optimism (and other EVM L2s later) with a general-purpose cross-chain messaging protocol that can handle arbitrary data and multiple token standards for maximum composability.

Please see our full proposal here: Aztec <> EVM L2 Cross-Chain Messaging Protocol

We look forward to building with you! :crossed_swords:

1 Like

Aztec Ghost: Run Transactions Anonymously on Optimistic L2s using Privacy Relayers

The Psycho Virtual team is excited to propose Aztec Ghost, an application that enables users to run trading transactions for ERC-20 tokens and NFTs anonymously, without revealing the user’s address by leveraging Aztec as a messaging intent source. The consequences of this builds a safe and secure bridge where users can bridge their assets from an optimistic L2 to Aztec and vice versa

Read our full proposal here.

2 Likes

Proposal: Privacy-Preserving Cryptographic Bridge

KRNL Labs is building a trust-minimized, privacy-preserving bridge that enables seamless cross-chain transactions between Aztec and any blockchain levering elliptic curve cryptography (ECDSA, EdDSA, or BLS schemes). This solution leverages KRNL Labs’ established cryptographic bridge and enhances it by integrating aztec.js functionality as an adapter. The modification enables the use of PXE from the node, thereby increasing pre-validation, security, and efficiency.

Immediate Scope

The proposal outlines the development of an MVP that demonstrates secure, confidential cross-chain asset transfers (native and ERC20) between Aztec and selected Ethereum L2s (e.g. Base, Arbitrum, Optimism), with a roadmap for broader interoperability.

Our full proposal can be viewed here or as a document.

1 Like

Grant Proposal: Private P2P Bridge – Universal L2 Privacy for P2P Trading

We’re building Private P2P Bridge, a relayer-based bridge that brings privacy to cross-L2 stablecoin trades. The system locks USDC on Base, moves zk-USDC through Aztec for private execution, and releases USDC to Arbitrum.

How It Works:

  • Merchants list P2P trades across L2s.
  • Buyers initiate escrowed transactions, fully private on Aztec.

More details: Full Proposal

1 Like
1 Like

Grant Proposal: Private Voting Bridge

1 Like

Proposal: Bringing Wormhole to Aztec

The Wormhole Foundation and Nethermind propose implementing the Wormhole messaging protocol on Aztec.

Wormhole encompasses message passing, cross-chain queries, fungible and non-fungible token bridging, intent-based bridging, and native token transfers. For this grant, we will focus on implementing core message passing, off-chain guardian and relaying functionality, and a PoC token bridge with privacy features.

1 Like

Proposal :
Based on our understanding of the MVP scope and considering the future scalability of this interchain solution between Aztec and other L2’s or L1’s, our proposal is based on the follow key elements of User experience and technical architecture

  1. Modular components
  2. Custom ZK-proof based proving of deposit and withdrawal by managing and synchronizing the state on all connected chains.
  3. Allow for message (proof) transmission.
  4. Assets on each chain managed by liquidity provisioning on those chains and balanced via 3rd party LP’s
  5. Integrate with an existing dumb message bridging solution, this is a faster solution for the MVP and also scalable.

Our overall solution consists of the following elements for executing a cross chain operation. These elements itself has its own features and dependencies

  1. Bridge Core : This is the main operational logic implemented as smart contracts.
  2. Merkle Trees : These trees represent methods to keep the records secure for the inter chain protocol. There will be two types of trees, one each for every chain ( let’s call it “chain tree’ which stores the state of every chain) and one “global tree” which contains the state ( root of chain tree) of every connected chain
  3. Interchain communication ( Keepers) : Operator of various off chain processes like roll-up / state synchronization etc. Keepers run the Interchain client process
  4. Messaging Bridge : Selection of message bridge is made keeping in considerations of Relayers, Validators, Gas Quotations, Customizability, Technical intricacy, number of supported networks and the trustless nature of the bridge itself.
  5. dApp : will allow users to interact with the bridge and person cross chain intents.
  6. RPC provider

Our Team consists of members from zkMonk enginnering community and members of the Panther Protocol team with deep expertise in architecting, building and executing scalable solutions.
Our contact : contact-- at–zkmonk–dot–org

Detailed Proposal:

  1. High level Architecture

This is a conceptual architecture of the Bridge that we propose. We can expect a few changes as we start the detailed design and implementation.

Theoretically, this is a privacy bridge but can be extended to make it a public bridge by exposing certain elements of the input data.

This is similar to IBC in the way that each chain stores some information about the state of the other chain but in our case the state of the interchain alone is recorded and updated in the Merkle tree.
Every deposit can be treated as creation of an UTXO and a withdrawal is spending of the UTXO.

ZK proof ensures that users who can prove their deposit in the origin chain are allowed to withdraw from the destination chain. After withdrawal, the state is updated to stop double spending of any deposit(s) on any connected chain. Also users generally specify the destination chain while making an interchain intent.

  1. Bridge Type and why?

ZK bridge for private bridging of assets. Integration with an existing Message bridge allows for modularity and scalability.
Keepers are the off chain entity that runs the Interchain client which helps in reading and synchronizing the state of interchain deposits and withdrawal. In the future Keepers can fall part of the larger validator network either within the Aztec ecosystem or derive security by integrating to the Eigen layer etc. This can be the future enhancements.

  1. How the design meet the requirements

It is generic and can be used by individual users within Aztec or other L2’s or in the future, we can create endpoints for dApps within Aztec to seamlessly integrate.

The modular architecture supports any asset type and flexibility of making changes to different models without impacting the core functionality.

It is trustless, private and secured using zero knowledge.

It also fits well with Aztec private transactions using the PXE client side solution for dApps and also works well with the public transaction.

  1. Technical hurdles that need to be overcome

Integration with a 3rd party message bridging has dependency to have implementation available on Aztec and other L2’s but this can easily be mitigated and then scaled.

  1. User flow and journey

  2. Private bridging between Aztec and destination chain (L2)

  3. Private bridging from other L2’s to Aztec

MVP Grant Amount

MVP Duration : 3 months

Based on our high level estimation and resource planned for MVP will be USD 48,000 ( USD Forty Eight Thousand). This does not cover any third party implementation or integration cost or any changes on the Aztec side that may arise during the development phase.

Further details about our resource plan and roadmap for the future, please check out this document. ( the tool wont allow to add more images here)

1 Like

Proposal name: Chameleon - Cross-chain private multi-sig

Chameleon is a private cross-chain multisig solution that enables users to control assets on public L2s through a privacy-preserving multisig on Aztec. Our bridge connects Aztec testnet to Optimism Sepolia by using a hybrid approach that combines a relayer network with an optimistic verification mechanism. Users can privately create and manage multisig wallets on Aztec with customizable X out of Y signers thresholds, then use these to authorize transactions on Optimism without revealing tany of the signers or voting patterns. This creates powerful use cases for DAOs, treasury management, and organizations wanting privacy while interacting with defi on public networks to tap into their liquidity sources.

Full proposal

2 Likes
1 Like

Contact Details
Email: [sam@undefy.io]
Telegram: lucidsamuel

TLDR: Aztec <> Superchain Bridge
Kage Kurō is a privacy-focused cross-chain bridge that facilitates confidential asset transfers between Aztec and Optimism (Superchain ecosystem). It utilizes Merkle proofs to securely aggregate and verify transaction intents, ensuring trust-minimized interoperability. Integration with EigenDA enhances scalability and data availability, maintaining privacy and efficiency in cross-chain operations.

Summary:
We propose Kage Kurō, a privacy-first cross-chain bridge that connects Aztec with Optimism in the superchain ecosystem. Our system enables confidential asset transfers by creating “intents” on the source chain, which are hashed and recorded in a Merkle tree. Off-chain relayers aggregate these intents and transmit the aggregated Merkle roots (secured via threshold signatures) to the target chain using protocols like LayerZero, with EigenDA ensuring decentralized data availability. On Optimism, solvers verify individual intents using Merkle proofs before executing asset transfers and claiming reimbursements. This approach ensures trust-minimized, efficient, and private cross-chain interoperability, reducing gas costs and enabling selective disclosure for regulatory compliance.

About Us (Kage Protocol):
Kage Protocol is a portal to private DeFi comprising of a suite of products that enable users to interact with decentralized finance while preserving confidentiality at every layer. Our team comprises blockchain engineers and cryptographers with relevant experiences in:
Zero-knowledge proofs (ZKPs) and privacy-preserving computations.

  • Cross-chain interoperability and bridging protocols.
  • EVM-compatible smart contract development and emerging ERC standards (e.g., ERC-4337).

Kage Protocol was built to redefine the DeFi landscape by ensuring that every transaction from payments to lending and staking is executed with uncompromised privacy.

Read full proposal

1 Like