Ecosystem and builder programs exist, but public sizing is disclosed only through approved canonical materials.
Ecosystem Capital Framework
Grants Program
Aethelred frames ecosystem and builder programs as governed rollout surfaces rather than automatically public token buckets. This page reflects the current whitepaper and tokenomics posture: milestone-gated awards, governance-controlled disbursement, on-chain transparency, and a public status that remains pre-award until the canonical token source pack and related disclosures are approved. Use it alongside the community hub, Infinite Sandbox, developer tools, and the foundation governance surface.
NO PUBLIC AWARDS ANNOUNCED
Documented funding envelope
The published tokenomics allocates ecosystem capital for grants, developer adoption, partnerships, and broader network growth rather than one-off discretionary spending.
Governance before disbursement
Release is meant to flow through treasury controls, milestone review, and a governance path with multisig approval and timelock protection.
Pre-award public status
The structure is public, but no public grantees, cohorts, or published disbursements are listed on the current site yet.
Governed
Program sizing publishes only from approved canonical materials
Pre-Award
No public award amounts or grant cohorts are announced on the site today
Controlled
Disbursements follow governance, milestone review, and disclosure approval
Overview
Program structure grounded in the current tokenomics
The grants program is published as a controlled ecosystem layer, not an unbounded marketing budget. The public references describe governed programs, a conservative release posture, and treasury controls intended to keep awards accountable to measurable outcomes without publishing draft token metrics prematurely.
No public grant cohorts, award sizes, or recipient lists are announced on the site today.
Launch-specific token amounts and release metrics publish only after disclosure approval.
Governance and treasury approval sit in front of ecosystem disbursements.
POOL
Funding Basis
Capital is allocated for growth, but release is deliberately metered
The current tokenomics describes ecosystem and builder programs as governed coordination layers for adoption, tooling, partnerships, and network growth. It intentionally withholds launch-specific token amounts and release timing until those details are approved through the canonical token source pack rather than letting draft spreadsheets drift into public claims.
Published Use Cases
Developer grants, ecosystem growth, partnerships, tooling expansion, and network bootstrapping.
Release Posture
Initial capital exists for early activation, but downstream disbursement is expected to track milestones rather than flat one-time awards.
CTRL
Governance Controls
Ecosystem fund release is bounded by treasury and oversight rules
The whitepaper and tokenomics both frame ecosystem spending as a governed process. The current public references emphasize milestone review, treasury oversight, auditable release controls, and disciplined disclosure. That matters because a credible grants program is defined by its approval path, not by a headline allocation claim.
Approval Boundary
Multi-signature treasury governance rather than unilateral operator discretion.
Operational Guardrail
Governed disbursements create an auditable review window before capital moves.
Funding Tracks
Work streams that fit the current Aethelred surface
The most credible grant targets are the ones that strengthen the protocol surfaces already documented across the site. That means work that improves Proof-of-Useful-Work operations, Digital Seals, developer adoption, verification quality, and operational readiness.
APP
Track 01
Verifiable AI applications
Applications that make the protocol legible to end users: agent systems, regulated inference workflows, Digital Seal consumption layers, provenance-heavy enterprise tooling, and vertical products that need verifiable execution rather than generic smart contract hosting.
SDK
Track 02
Developer tooling and integrations
Libraries, framework bindings, deployment surfaces, explorers, verifiers, wallet flows, and CI automation that make it faster to build on Aethelred without introducing unsafe or undocumented shortcuts.
SEC
Track 03
Security, verification, and research
Audits, formal methods, verifier hardening, zkML proof tooling, TEE attestation research, key management improvements, and protocol research that reduces risk for builders and validators before the network scales.
OPS
Track 04
Infrastructure and ecosystem enablement
Operational systems that improve network readiness: testnet services, local devnet automation, indexing, observability, validator-facing utilities, and production support layers for ecosystem teams moving from rehearsal into public rollout.
Review Process
A serious grants program is a review system, not a form fill
The old reference page implied a simple funnel. The current documentation suggests a stricter path: technical fit, milestone definition, governance-controlled approval, and transparent release. That is the framework reflected here.
Submit an interest brief
Start with the problem, why it needs Aethelred specifically, the target protocol surface, and what exists today as code, research, or working prototype material.
Run technical fit review
Projects should map clearly to documented needs such as tooling, verification, wallets, security, infrastructure, or verifiable AI application delivery.
Define milestones and reporting
Before capital is committed, the work needs clear deliverables, release conditions, and an observable reporting path that can be checked by the foundation and the community.
Move through treasury controls
Any disbursement path should respect multisig approval and the timelock boundary described in the current whitepaper and tokenomics materials.
Publish progress and releases
The public program direction is transparency. That means funded work should resolve into visible milestones, disclosed grantees, and auditable disbursement records rather than private ecosystem spending.
Evaluation Criteria
What makes a proposal credible
The bar should be technical and operational. Good grants do not just sound aligned; they improve the network in ways that can be measured, shipped, and maintained.
Protocol relevance
The work should strengthen a real Aethelred surface rather than being chain-agnostic marketing dressed up as infrastructure.
Delivery credibility
Teams need a realistic build plan, owners, milestones, and enough evidence that the work can actually ship.
Ecosystem leverage
Priority should go to work that multiple builders or operators can reuse, extend, or audit rather than closed one-off integrations.
Security and compliance posture
Projects touching verification, custody, regulated data, or validator operations need to show that they understand the risk boundary from the start.
Program Status
No public awards, cohorts, or grantees have been announced yet
This is the section that needed the biggest correction from the old reference page. As of March 11, 2026, the current site does not publish any funded projects or past grant recipients, so this page reflects that directly instead of inventing portfolio history.
PRE-AWARD PUBLIC STATE
Program framework is visible; public disbursement history is not.
The ecosystem allocation and governance controls are documented, but the public website does not list any awarded teams, completed cohorts, or published on-chain grant disbursements yet. That means interested builders should treat this as a program framework and readiness page, not as a record of existing portfolio activity.
Not announced
No named grant batch or seasonal intake is published on the current site.
None listed
There are no project cards, award amounts, or recipient profiles currently disclosed.
Not published yet
No public grant disbursement ledger or awards archive is surfaced on the site at this time.
What to prepare now
Share an architecture summary, repository or demo, milestone plan, team context, and why the work depends on Aethelred rather than a generic L1 or middleware stack.
What happens later
Once a public cohort exists, awards should resolve into named grantees, milestone schedules, and disbursement records that can be audited against the published control framework.
Want to be considered once the first public cohort is formed?
Use the current pre-award period to harden the proposal. Teams that show protocol fit, working artifacts, and clear milestones are materially easier to evaluate than teams that lead with broad ecosystem language and no delivery surface.
FAQ
Common questions about the current grants framework
These answers are aligned to the current public docs and the present state of the site rather than the older mock page.
Is the grants program already funding public projects?
No public awards are listed on the site today. The program controls are documented, but the public portfolio history has not been announced yet.
How much capital is reserved for ecosystem and grants?
The public tokenomics confirms that ecosystem and builder programs exist, but exact public token amounts, unlock timing, and program sizing are withheld until the canonical token source pack is approved for release.
How are grant disbursements supposed to be controlled?
The current public references describe governance-led review, milestone-based approval, and auditable treasury-controlled disbursements. Exact signer thresholds and release metrics should publish only through approved canonical materials.
What kinds of projects are the best fit?
The strongest fit is work that improves real Aethelred surfaces: verifiable AI applications, developer tooling, wallets and signing, security research, zk and TEE verification, indexers, explorer layers, and operational infrastructure.
What should a serious initial outreach include?
Include the problem statement, protocol fit, repository or demo, milestone breakdown, delivery owners, expected open-source footprint, and any security or compliance assumptions that matter to the work.
Next step
Prepare the proposal before the cohort exists.
Use the Infinite Sandbox to prove the workflow, the toolchain stack to show implementation quality, and the community hub to make the work visible before formal awards are announced.