1. Executive Summary
This proposal establishes a structured framework for deploying Community Treasury ASTR into dApp staking activities.
The program aims to:
- Strengthen long-term staking stability
- Reinforce ASTR utility within the ecosystem
- Allocate capital using objective, onchain-verifiable criteria
- Mitigate systemic risks related to staking thresholds
The framework introduces a two-lane model:
- Lane A (Reactive): Short-term interventions under predefined conditions
- Lane B (Proactive): Periodic allocation based on performance metrics
All allocations are conditional, time-bound, and subject to continuous review.
This proposal introduces a new structural framework for how the Astar Community Council (ACC) may deploy Community Treasury ASTR into strategic dApp staking positions.
The initiative is designed as an evolution of treasury capital deployment, shifting from passive reserve management toward a disciplined, KPI-driven staking strategy that directly supports ecosystem resilience, ASTR utility, and long-term staking stability.
As the dApp Staking ecosystem matures, threshold dynamics, concentration risks, and treasury efficiency become increasingly important. A purely static treasury approach may leave the ecosystem exposed to:
- sudden threshold dislocations,
- strategic partner instability,
- loss of ASTR-denominated utility momentum,
- inefficient treasury capital utilization.
This framework addresses those risks through a structured two-lane model that separates:
- Reactive ecosystem protection mechanisms, and
- Proactive performance-based capital deployment
The design intentionally prioritizes:
- objective and onchain-verifiable triggers,
- capped and time-bound treasury exposure,
- transparent public reporting,
- measurable ecosystem ROI.
The program is built to ensure treasury capital acts as a strategic stabilizer and utility amplifier, rather than a passive subsidy mechanism.
2. Background and Rationale
The Astar ecosystem has entered a phase where capital efficiency and staking quality matter more than broad distribution alone.
Under the evolving dApp Staking landscape, treasury-owned ASTR can serve a more strategic role by:
- protecting critical ecosystem infrastructure during temporary threshold stress,
- reinforcing high-performing dApps that generate measurable ASTR utility,
- smoothing structural volatility caused by staking concentration shifts,
- improving treasury productivity through objective redeployment.
This proposal establishes a formal policy layer for that function.
Rather than relying on ad hoc treasury decisions, the ACC would operate within a predefined governance framework, reducing uncertainty, minimizing governance friction, and improving decision consistency.
The intent is to provide enough upfront clarity so that future allocation decisions generate fewer procedural debates and more KPI-focused discussions.
3. Objective
To strengthen long-term staking conviction, improve ASTR utility contribution, and deploy Community Treasury capital with discipline, transparency, and measurable ecosystem impact.
More specifically, the framework seeks to:
- protect ecosystem stability during quantifiable staking stress events,
- reward dApps that demonstrably strengthen ASTR utility,
- maintain treasury flexibility through capped exposure,
- create a repeatable strategic staking policy for ACC operations.
4. Scope and Limitations
This framework is intentionally narrow in scope.
It is not designed as a subsidy program, nor as a mechanism to permanently sustain weak protocols.
The program therefore does not:
- replace organic community staking demand,
- guarantee long-term support to any dApp,
- provide indefinite treasury-backed positions,
- override performance-based removal criteria.
Every position must:
- serve a predefined strategic purpose,
- remain fully measurable using onchain data,
- comply with exposure caps,
- remain subject to transparent removal conditions.
This ensures treasury deployment remains strategic, temporary, and ROI-oriented.
5. Program Structure
5.1 Lane A — Priority Staking (Reactive)
Lane A provides a rapid-response framework for quantifiable ecosystem risk events.
Its purpose is to protect ecosystem stability when predefined numerical thresholds create systemic or treasury-relevant exposure.
5.1.1 Activation Conditions
Lane A is activated when a qualifying dApp satisfies at least one of the following:
- Floor Condition:
Total staked ASTR falls below 28M ASTR - Tier Condition:
A strategic partner falls below 75M ASTR - Contractual Condition:
Documented obligations exist where a staking tier downgrade creates direct treasury exposure
All triggers are:
- numerical,
- onchain-verifiable,
- non-discretionary.
5.1.2 Constraints
- Maximum of 2 concurrent positions
- Maximum of 40M ASTR per position
- Allocation remains active only until the triggering condition is resolved
5.1.3 Decision Process
- Initiation by any ACC member
- Internal vote within 48 hours (simple majority)
- Immediate execution upon approval
- Public retrospective published within 7 days
5.2 Lane B — Performance-Based Strategic Staking (Proactive)
Lane B defines the standard treasury deployment framework for ecosystem growth optimization.
Its purpose is to allocate treasury capital toward dApps that demonstrate measurable contribution to ASTR demand, user growth, and ecosystem stickiness.
5.2.1 Allocation Cycle
- Conducted on a quarterly basis
- Includes a full ecosystem KPI review
- Produces a ranked list of eligible dApps
5.2.2 Constraints
- Maximum 35M ASTR per position
- Combined exposure (Lane A + Lane B): ≤ 80M ASTR
- Remaining treasury preserved as liquid reserve
5.2.3 Decision Process
- Public ACC proposal
- 7-day public comment period
- Approval by simple majority
- Execution within 48 hours
5.3 Lane Priority
Lane A always takes precedence over Lane B.
If systemic protection requires treasury reallocation:
- Lane B positions may be reduced,
- Lane B positions may be unwound intra-quarter,
- all reallocations must be publicly disclosed.
Lane B allocations are explicitly non-permanent and dynamically adjustable.
5. Eligibility Framework
5.1 Stage 1 — Eligibility Conditions (Binary)
A project must satisfy all conditions:
- Operational Continuity
Minimum of 6 months of continuous onchain activity - Active Deployment
Publicly accessible and functional product - Minimum Activity Threshold
At least 200 unique active wallets over the past 90 days
Failure in any condition results in ineligibility.
5.2 Stage 2 — Performance Evaluation (Lane B)
Eligible projects are ranked using:
ASTR Utility Contribution (Weight: 60%)
- Share of transaction volume denominated in ASTR
- Share of TVL denominated in ASTR
User Growth Trend (Weight: 40%)
- Change in unique active wallets (rolling 90-day comparison)
Top-ranked projects (typically 2–3 per cycle) receive allocations.
6. Eligibility Framework
6.1 Stage 1 — Binary Eligibility Filters
A project must satisfy all criteria:
- Operational Continuity
Minimum 6 months of uninterrupted onchain activity - Active Deployment
Publicly accessible and functional live product - Minimum Activity Threshold
At least 200 unique active wallets over the past 90 days
Failure in any single condition results in immediate ineligibility.
6.2 Stage 2 — Performance Ranking (Lane B)
Eligible dApps are ranked through a KPI framework.
1. ASTR Utility Contribution — 60%
- Share of transaction volume denominated in ASTR
- Share of TVL denominated in ASTR
2. User Growth Trend — 40%
- Rolling 90-day change in unique active wallets
The top-ranked dApps (typically 2–3 per quarter) receive allocations.
7. Removal Criteria
7.1 Lane B
Positions are removed if:
- activity falls below minimum threshold for 2 consecutive months
- ASTR utility contribution declines by >40% from baseline
- a material security incident remains unresolved for 30+ days
- Lane A intervention requires treasury redeployment
7.2 Lane A
Lane A positions close when:
- the triggering condition is resolved
- the condition remains resolved for 14 consecutive days
A 7-day post-resolution review period follows to assess potential Lane B eligibility.
8. Risk Considerations
| Risk | Mitigation |
|---|---|
| Capital inefficiency | Eligibility gates and ranking system |
| Governance subjectivity | Reliance on onchain metrics |
| Over-allocation | Hard caps on exposure |
| Liquidity constraints | Reserved treasury buffer |
| Metric manipulation | Use of rolling 90-day data |
9. Reporting and Transparency
The ACC will publish:
- quarterly ecosystem KPI reports,
- all allocation decisions,
- all reallocations and removals,
- Lane A post-action retrospectives,
- methodology updates when KPIs evolve.
All reporting must rely on publicly verifiable onchain data sources.
10. Success Evaluation
Program effectiveness will be evaluated using:
- growth in ASTR-denominated TVL,
- increase in active wallet participation,
- staking threshold stability,
- treasury ROI efficiency,
- concentration risk reduction.
11. Treasury Allocation Summary
The Community Treasury currently holds approximately 125 million ASTR. To balance ecosystem support with long-term treasury sustainability, the ACC proposes the following high-level allocation framework.
Maximum total deployed: 80M ASTR
Up to 80 million ASTR (~64% of the treasury) may be deployed strategically through the staking program. This allocation is divided into two operational lanes.
Maximum Lane A position: 40M ASTR
Lane A, which serves as the strategic reserve for priority or reactive interventions, may deploy up to 40 million ASTR. These allocations are intended to protect critical ecosystem infrastructure or address situations where important projects temporarily fall below key staking thresholds.
Maximum Lane B position: 35M ASTRT
Lane B, which focuses on performance-based strategic allocations, may also deploy up to 40 million ASTR. These positions are designed to reinforce high-impact dApps that demonstrate strong ecosystem contribution according to the established KPI framework.
Within the overall staking allocation, the ACC may maintain a rapid response buffer of approximately 10–15 million ASTR. This buffer allows the Council to react quickly to emerging ecosystem opportunities or urgent situations without requiring immediate rebalancing of existing positions.
Treasury reserve: maintained liquid at all times
The remaining ~45 million ASTR (~36% of the treasury) will remain as a liquid reserve. This reserve ensures that the treasury can continue supporting non-staking obligations such as community initiatives, ecosystem programs, operational needs, and future strategic opportunities.
| Category | ASTR Amount | % of Treasury |
|---|---|---|
| Total Community Treasury | ~125,490,556 ASTR | 100% |
| Maximum deployable for staking (both lanes) | ~80,000,000 ASTR | ~64% |
| Liquid reserve (non-staking obligations + Lane A capacity) | ~45,490,556 ASTR | ~36% |
| Lane A ceiling (per position, max 2 concurrent) | up to 40,000,000 ASTR | — |
| Lane B ceiling (per position, max 3 concurrent) | up to 35,000,000 ASTR | — |
This structure aims to provide a balance between capital efficiency, strategic flexibility, and long-term treasury sustainability, while ensuring that the majority of treasury resources remain available to strengthen the Astar ecosystem.
Astar Community Council 
@Community_Council
