Teleporter Grants - Process & Eligibility Criteria

Many of you have participated in the inaugural Community Grants Round, which was very open-ended and employed Gitcoin’s quadratic funding model.

The upcoming Community Grants round will be a little different, and focus on a new piece of infrastructure that has the potential to transform the Avalanche ecosystem, enabling key use-cases that haven’t been possible until now.

Introducing Teleporter Grants:

These grants will provide focused financial support to projects demonstrating potential, innovation, or strategic importance to the Avalanche Teleporter ecosystem. They will target projects that enhance existing bridge contracts, expand application contracts, and create seamless multi-chain user interfaces (see more details/ideas at the bottom of this post).

Hybrid Funding Model

This Community Grants Round will adopt a hybrid funding model, with a combination of Direct Funding and Retroactive Funding.

  • Direct Grants will be provided upfront, only providing the minimum necessary funding for developers to reach a specific milestone.
  • Retroactive Grants will happen 1-2 months after the Direct Grants have concluded, and provide retroactive funding for developers that have reached their stated milestones. The bulk of the funding will be in the form of retroactive funding, and a committee comprising of community members, Avalanche Foundation board and Ava Labs engineers will be formed to vote on the allocation.

Objectives

  • Encourage development in areas within the Avalanche Teleporter ecosystem, such as bridge contract enhancements, application contract expansion, and multi-chain user interfaces.
  • Provide targeted financial support to individuals and teams working on projects that align with Avalanche’s strategic goals.
  • Encourage innovative projects that showcase the potential of Avalanche Teleporter and attract new users to the ecosystem.

Eligibility Criteria

Alignment with Avalanche Teleporter Ecosystem

  • Projects must align with the Avalanche Teleporter ecosystem and contribute to its growth and development.
  • Proposals should outline how the project will create value for the Avalanche community, enhance user experience, or drive the adoption of the Avalanche Teleporter.
  • Projects should focus on one or more of the following themes:
    • Existing Bridge Contract Enhancements: Complex use cases with ERC20 and Native token bridges, cross-chain swaps and liquidity utilization, or seamless P2P payment apps using USDC-denominated Subnets.
    • Expanding Application Contracts: VRFs, Chainlink integrations, NFT Bridge and marketplace experiences, or custom applications leveraging Teleporter.
    • Seamless Multi-Chain User Interfaces: UIs that make multiple chains feel like one using Teleporter, cross-chain asset management, and interaction, or innovative user experiences for Subnets and the Avalanche ecosystem.

Contribute to Innovation and Ecosystem Growth

  • Projects should showcase innovative ideas, technologies, or approaches that have the potential to impact the Avalanche Teleporter ecosystem significantly.
  • Proposals should articulate the project’s expected outcomes and benefits, such as engagement, improved protocol functionality, or expanded use cases.
  • For projects focusing on technical innovation, proposals should demonstrate the team’s technical expertise and ability to implement the project successfully within the proposed timeline and budget.

Funding and Budget

  • Proposals should provide a breakdown of the project’s budget and clearly explain how the requested funds will be allocated.
  • Projects should demonstrate a clear need for the requested funding and explain how the grant will enable them to achieve their goals and create value for the Avalanche Teleporter ecosystem.

Reporting and Communication

  • Projects must commit to providing regular progress updates and maintaining open communication with the Avalanche community in the Avalanche Forum for the grant period.
  • Proposals should include a plan for sharing project milestones, successes, and learnings with the broader community.

Evaluation Process

  • Proposals will be reviewed by a committee comprising Avalanche Foundation, Ava Labs, and community representatives.
  • Projects will be evaluated based on their adherence to the eligibility criteria, potential impact, and alignment with Avalanche Teleporter’s strategic goals.
  • The committee will prioritize projects likely to succeed and drive significant growth and adoption within the Avalanche Teleporter ecosystem.

Unsure what to build? Teleporter Devs have some ideas for you:

  • Use Existing Bridge Contract:
    • Demonstrate more complex use cases with the existing ERC20 and Native token bridges. For example, the sendAndCall interface enables the direct use of bridged tokens in dApps on other chains, such as performing swaps, using the tokens to pay for fees when invoking services, etc.
    • Initiate a swap on a Subnet with more liquidity to get a better price. For example, Avalanche C-Chain has ample liquidity, as it is integrated with tons of DEXs, CEXs, and other platforms. A user could conduct a swap using Teleporter and get the best price guaranteed (on C-chain) without having to leave their Subnet.
    • Seamless P2P payment app on a USDC-denominated Subnet that uses Teleporter token bridge contracts to obtain USDC as the native gas token
  • Expand on other application contracts (e.g. VRFs, NFT Bridge):
    • Build a seamless UI on top of the simple betting game in the VRF repo to build a sticky dApp for users
    • Replicate the VRF contracts to obtain Chainlink Price Feeds or Functions from C-chain to a Subnet using Teleporter
    • Create a seamless experience for your users where they don’t have to deal with any of the web3 nuances like gas or bridging: users can purchase an NFT on Avalanche C-Chain seemingly without having to leave, but the NFT itself is minted on a “gasless Subnet”.
    • Write your own application contract! The possibilities are endless :slight_smile:
  • Or really, any UI where you can show us that you can use Teleporter to make multiple chains feel like one.
4 Likes

Where can I find this topic grant into Gitcoin explorer? I already create the project into Gitcoin builder

1 Like

Here is the Gitcoin submission link: Gitcoin | Builder

2 Likes

Just release https://builder.gitcoin.co/#/chains/43114/registry/0x/projects/0x2b5a1a293bb1c67358d0fe11d90605defe739e53d51c14c845341b3d8b50abe1

Very exited to build a trust, Safe and Secure solution for all stablecoins holders on Avax. With Europe Regulation, RWA will be a key component for institutionnal Partner.

nb: I was Og in ftm and avax / Was rekt with multichain hack in the Defi summer so i think we really need something secure and scalable here

Dyor Ledgity :innocent:

1 Like

Hi, given that we participated with good results, IMHO, in the first round (see https://gap.karmahq.xyz/project/improve-the-security-of-the-avalanche-network-by-auditing-porting-and-testing-its-fundamental-tools-on-openbsdadj/grants?tab=milestones-and-updates and https://www.pasosdejesus.org/avalanche-adJ/). We would like to continue auditing, porting to OpenBSD/adJ and testing in this second round but focused on the Avalanche Teleporter Ecosystem.

Out of the first run we could port the most recent versions of avalanchego, coreth, subnet-evm and avalanche-network-runner and we are running for one month a validator node on OpenBSD/adJ on testnet. We were also able to port an older avalanche-cli (the current version of avalanche-cli doesn’t compile yet with the most recen tools that we ported see Issue 2077 in avalanche-cli).

For the second round we would like to validate a couple of subnets on testnet and audit and test with them the “ERC20 and Native token bridge”. To do that we need to (1) port a newer version of avalanche-cli once it is released, (2) port/test/audit awm-relayer, (3) keep updated ports of all the mentioned tools as testnet/mainnet employ newer versions (for example we expect a PR we made on all tools to improve security to be merged soon and a new version of all the tools will be released, see PR 3080 in avalanchego), (4) improve the support for OpenBSD/adJ in all the mentioned tools as we validate with them, (5) join as validator on testnet of two existing subnets or create new ones, (6) audit/test the ERC20 and Native token bridge with nodes running on OpenBSD/adJ.

I think it is possible to attain these goals within 3 months.

What do you think about proposing this project for the second round? What do you recommend to improve?

1 Like