How to Apply

Tags

Ecosystem Need

Today, tracking open calls across ecosystems requires monitoring individual program pages, mailing lists, social media feeds, and aggregator spreadsheets. There is no single, structured source of truth. The consequences are: - Builders miss deadlines or never discover opportunities that match their expertise. - Funders receive fewer and less diverse proposals than the ecosystem can offer. - Tool builders who want to surface opportunities (in dashboards, bots, or AI agents) have no reliable, machine-readable feed to build on. - Existing directories (Blockworks Grantfarm, Karma Funding Map, AlphaGrowth, various Airtable databases) are valuable but fragmented, manually maintained, and lack a shared schema or API. Related standardization efforts, such as DAOstar’s DAOIP-5 Grants Metadata Standard and schema.org/Grant, have laid important groundwork for structured grants data. This project should build on that progress rather than start from scratch.

Hard Requirements

All hub software, standards, and data outputs must be **open source**, with code, schemas, and datasets published in public repositories under a permissive license (MIT, Apache 2.0, or CC0 for data). Standard - Define a standard RFP object format that is versioned, documented, and validated Publishing - Community submissions: anyone can submit an RFP entry, which remains pending until reviewed and approved through the governance process - Direct publishing: approved organizations can publish and update their own RFPs as verified publishers Access - Provide a public, unauthenticated REST or GraphQL API with search, filtering (by funder, category, status, deadline, ecosystem), and pagination. - Provide a documented export mechanism so integrators can regularly fetch the full dataset without relying on the live API. Data quality and Sync - Define how updates are tracked, broadcasted, and applied for both community-submitted entries and verified publisher entries, including the sync mechanism (for example, webhooks, polling, RSS/Atom feeds, or snapshots). - Define how duplicates are detected and how conflicts, corrections, and stale entries are resolved. The system should handle the case where the same RFP is submitted by a community member and later claimed by the verified publisher. - Every entry should carry provenance metadata: who submitted or published it, when, and whether it has been verified against the original source. Governance - Define review and approval rules for community submissions, dispute handling procedures, and how verified publisher status is granted and revoked. - Define how changes to the standard and dataset rules are proposed, reviewed, and released over time. - The hub must be non-discriminatory in indexing. Inclusion rules must be transparent and applied consistently. If the hub supports any form of ranking, featured placement, or recommendation, the policies governing those decisions must be explicit and publicly documented. Adoption proof - During the pilot, EF Grants Management supplies RFPs and at least two additional RFP sources provide ongoing updates, with written commitments included in the proposal Reference frontend - Provide a minimal reference frontend that supports basic discovery and links users to the original source to apply. The frontend should serve as a working demonstration of the API and as a template for community-built interfaces.

Soft Requirements

Team experience - Demonstrated experience in web3 public goods funding, grants, or related ecosystem work - Proven track record operating a public API in production, and shipping and maintaining an open source project or public dataset Long term ownership and contributions - The proposing team is expected to own long term maintenance of the standard, the API, data ingestion, and dataset publishing - The project should include clear contribution guidelines Documentation and handoff - Publisher and integrator onboarding guidance, including quickstart examples, validation tooling, and API client samples in at least one popular language.

Resources

Timeline