This is the Infrastructure Committee's open call for proposals for Q3/Q4 2025. If you are an infrastructure provider, development team, or NEAR ecosystem contributor and have an idea to improve NEAR’s infrastructure, we encourage you to submit a proposal.<h2 class="heading-node">Areas Of Interest</h2>The Infrastructure Committee will consider any proposal that helps make the NEAR ecosystem a more compelling place for web3 builders and users. That includes, but is not limited to, these key areas:<ul class="list-node tight" data-tight="true"><li>Protocol Development</li><li>Contract and Token Standards</li><li>Wallets</li><li>Oracles</li><li>Bridges</li><li>On-ramps / Off-ramps</li><li>Relayers</li><li>Explorers</li><li>Indexers</li><li>Data Lakes</li></ul><h2 class="heading-node">Proposal Markup</h2>Please use the following markup templates when submitting the body of your proposal.<a class="link" href="https://docs.google.com/document/d/1UZRfOE1JAOhsnSmp-RmL2hY7KPJbpBImKZVvPV4YJmA/edit?usp=sharing](https://docs.google.com/document/d/1UZRfOE1JAOhsnSmp-RmL2hY7KPJbpBImKZVvPV4YJmA/edit?usp=sharing)" target="">Proposal Template</a><h1 class="heading-node">Process Summary</h1>Generally, the process proceeds as follows;1. You draft the proposal, then the Infrastructure Committee members are free to review and offer suggestions.2. Once everyone feels the proposal is ready, it moves to voting. The committee votes asynchronously and in regular committee meetings. A proposal is approved if it receives a majority vote from the Committee members.3. In the event of a rejection, you will be informed, usually via the Telegram group established. Guidance may be offered on how to update the proposal for resubmission.4. If your proposal is approved, you will move into the Funding Pipeline. You (or your company) will complete the KYC/B process, which involves providing your personal or company information for verification purposes. Next will be a legal working agreement, and finally, a test transaction will be conducted to ensure the target wallet address is correct.Learn more about <a class="link" href="https://near-foundation.notion.site/The-Proposal-Process-1d6da22d7b6480c2bf29c471b7abd978" target="_blank">submitting a proposal</a>. Learn more about our <a class="link" href="https://near-foundation.notion.site/The-Funding-Process-1d6da22d7b648010969afb67b93df6f0" target="_blank">funding process</a>.<h1 class="heading-node">Evaluation Criteria</h1>The Committee intentionally does not publish strict evaluation criteria for proposals and does not publish its meeting notes. This subjective approach helps us be honest, decisive, and unrestrained in our ability to effect change in the NEAR ecosystem. All RFPs, proposals, committee decisions, and funding allocations are published for community transparency and accountability.That said, the Committee greatly appreciates proposals that:<ul class="list-node tight" data-tight="true"><li>Add new capabilities to the NEAR ecosystem</li><li>Fill in gaps or address challenges faced by NEAR builders and users</li><li>Bring new developers or users into the NEAR ecosystem</li></ul>Generally speaking, the Committee believes infrastructure providers in the NEAR ecosystem should be economically self-sustaining, with a business model that does not rely on continuous grants from the Committee or other funding bodies. For instance, we have rejected proposals from RPC providers to fund all setup and operation of RPC nodes so that developers would get free access to RPC services. But we are open to alternate arrangements, such as loans to help cover initial setup costs and grants in exchange for service credits we (or the NEAR Foundation) can distribute to NEAR builders.We are also eager to fund projects that benefit the ecosystem but have no direct revenue potential, such as open-source libraries.Often, a blockchain business involves creating some new open-source specification or protocol and then building a for-profit business on top of that protocol. We are open to funding the “protocol” portion of the effort to help get your NEAR ecosystem business off the ground.

Use [the template](https://docs.google.com/document/d/1UZRfOE1JAOhsnSmp-RmL2hY7KPJbpBImKZVvPV4YJmA/edit?tab=t.0).

# Milestone #1 - NAME OF MILESTONE

Payment Amount:

Duration:

Description:

Definition of Done:

# Milestone #2  - NAME OF MILESTONE

Payment Amount:

Duration:

Description:

Definition of Done:

Iker Alustiza

Infrastructure Committee

Infrastructure Committee Open Proposals Q3/Q4 2025

Milestone 1

Milestone 2

Pingpay

Jayythew

Payment for submission #19

Michelle Weber

Milestone 3

Milestone 4

Milestone 5

Extension of State Parts proposal

Evgeny Kuzyakov

Payment for submission #23

Goldsky Mirror

Hemanth Soni

Token Vault

Edward | Meteor Wallet

Payment for submission #37

Nikita Grechino | Chainspect

Allium Full integration

Milestone 1 Prepayment

Milestone 6

Milestone 7

Milestone 8

NearBlocks 2 year extension

Support for running Archival RPC nodes

NEAR Playground v2

Upfront payment

Halfway payment

Token Terminal

Sebastian Motelay

Meteor Wallet - Big Query Pipeline Maintenance

Upfront

Privy Plugin for Near-Connect

Peerfolio

Near VRF

Kyler Nguyen

GioroX AI | WAP3: Web3-based Agent-Native Payment & Provenance Protocol for NEAR