dApp Staking Code of Conduct
This Code of Conduct outlines the rules and guidelines that all participants in Astar dApp Staking are expected to follow. Its purpose is to ensure fairness, transparency, and long-term sustainability for projects onboarded across the Astar ecosystem, including those deployed on external but compatible chains such as Soneium, Ethereum, Polkadot, and other parachains.
Overview
dApp Staking is available to projects that provide tangible value and real-world utility to the ASTR token and the broader Astar Ecosysyem. Eligible projects include applications, tools, services, and infrastructure across various blockchain ecosystems.
nota
Requirements to join dApp Staking may vary depending on the deployment chain. Projects on non-native chains (e.g., Soneium or Ethereum) must clearly demonstrate how they benefit the Astar ecosystem and meaningful ASTR token. This includes—but is not limited to—using ASTR as a payment method, in-app currency, staking mechanism, or any integration that creates real value for ASTR holders.
| # | Classification | Guidelines |
|---|---|---|
| 1 | Introduction | Participants must fully understand how dApp Staking works. Official documentation, blogs, and community resources should be consulted before participating. |
| 2 | Definitions and Terminology | dApp Staking is not a grant or charity program. Projects must be capable of sustaining themselves without relying solely on staking rewards. While staking can support early development, it should not be the primary business model. |
| 3 | Purpose | The main objective of dApp Staking is to support the growth of Astar by increasing adoption, engagement, and utility for the ASTR token. Projects should avoid making financial promises unless backed by measurable, on-chain metrics. Examples of measurable value include: DeFi: TVL, transaction volume, fees generated, active wallets, revenues, market cap. NFTs: Floor price, marketplace volume, % listed for sale, unique holders. |
| 4 | Compliance Requirements | Projects must not treat dApp Staking as a business model. Their sustainability should not rely exclusively on staking rewards. |
| 5 | Definitions and Scope | dApp Staking is not a traditional grant. Projects must be live (or have a working MVP) on a supported chain (e.g., Astar, Soneium) and offer sufficient documentation for token holders to make informed decisions. dApp Staking rewards are community-driven and performance-based. For early-stage, pre-MVP projects, refer to the Unstoppable Community Grants (UCG) program. It offers structured support with clear exit criteria tied to dApp Staking V3’s tier system. External projects must present a clear roadmap demonstrating long-term commitment to Astar. This includes sustained ASTR integration, development milestones, and a strategy for continued ecosystem contribution—even if not natively on Astar Network. |
| 6 | Reporting and Monitoring | Projects are strongly encouraged to submit regular progress reports via the Astar Forum (Governance -> dApp Staking Reports). At a minimum, reports should cover:
Tier 4 projects are expected to submit at least monthly updates. A lack of reporting for 3 consecutive months may trigger a delisting process. External projects (e.g., Soneium) must explicitly include how ASTR is used within their platform and report ASTR-related metrics (e.g., usage, transactions, liquidity). Reports can be monthly or quarterly but must be consistent and transparent. |
| 7 | Evaluating Negative Impacts | Any community member can raise concerns if a project is harming the ecosystem on the Astar Forum. If misconduct is confirmed, the project will receive a warning and 60 days to take corrective action. If issues persist, the Community Council may propose delisting. Examples of harmful behavior:
|
| 8 | dApp Categories | Projects must select a primary category for clarity and consistency. The current dApp categories include:
|
| 9 | Clarification of Endorsement | Inclusion in dApp Staking does not imply endorsement or automatic trust. Projects must earn and maintain credibility through transparent operations, strong community engagement, and consistent results. |
| 10 | Application Process | Projects that meet the requirements can apply via two routes: 1. Community Council Path: Submit a proposal on th Astar Forum. The Council will review and may whitelist the project within 2 weeks. 2. Token Holder Referendum: Propose directly on Subsquare. If passed by public vote, the project is whitelisted and can register on-chain. For submission templates and technical onboarding details, refer to the dApp Staking – For Devs section. All applications from external chains must include a section on ASTR token integration, community alignment, and measurable contribution to Astar Collective’s visibility or growth. |
Additional Notes for Cross-Ecosystem Projects (e.g., Soneium)
Projects deployed outside Astar Network (on chains like Soneium, Ethereum, or Polkadot) are welcome but must meet stricter eligibility criteria to reflect their indirect contribution to Astar’s core metrics.
Minimum expectations include:
- Demonstrated integration or utility for the ASTR token (e.g., as payment, staking collateral, access rights, or governance).
- Visible ASTR usage in-app or in UI, plus marketing mentions on social platforms or documentation.
- Clear contribution to Astar’s brand, visibility, or adoption.
- Concrete roadmap and reporting of ASTR-related KPIs (e.g., usage volume, liquidity, community engagement).
- Efforts to grow the visibility and adoption of ASTR, even if deployed outside Astar Network.