The Community Council is currently working on updating the guidelines and requirements for dApp Staking — specifically for projects that are part of the Astar ecosystem but deployed outside of Astar Network, such as on Soneium, Ethereum, Polkadot, or other parachains.
We’re opening up this thread to gather feedback and input from the community on how we should approach this.
Since these projects run on different chains and don’t directly contribute to Astar Network metrics (like TVL, tx volume, etc.), the conditions for them to qualify for dApp Staking will likely be different — and possibly stricter. They’ll need to demonstrate clear value to Astar or the ASTR token to be considered.
One key requirement that the Community Council is planning to include is a clear ASTR token integration — whether that’s as a payment method, in-app utility, or any other mechanism that provides real use cases or benefits for ASTR holders.
Looking forward to hearing your thoughts and suggestions as we work to refine these guidelines!
I think it depends more about what the app is doing..
All dapps are different so it’s hard to put a simple rule..
I hope we stay quite relaxed about this subject and let the community decide when someone crosses the line.
Also consider that “more rules = more bureaucracy”. This can deter people from wanting to build on ASTR. We should be welcoming to new/old dapps coming to astar.
Personally:
ASTR
SONEIUM / ETHEREUM / POLKADOT / ASTR EVM
Other networks with bridge
Other networks without bridge
Thank you for the proposal, I fully agree with it.
For projects in other chains, I think they need to specifically indicate the following
What contribution you can make to Astar Netwrok and ASTR (i.e., commitments)
Specific monthly reports (i.e. TVL, usage, etc.)
Given Astar’s current status, it is important to bring in the ecosystem of external chains, especially with Soneium, and it would make sense to target dApp Staking after ACS.
This sounds like a very interesting direction and a necessary evolution of the dApp Staking guidelines. That said, I believe it’s crucial that any project applying from outside Astar shows a real, long-term commitment to driving ASTR utility — not just through short-term integrations or marketing blitzes. There should be clear rules or milestones in place to ensure ongoing alignment with the growth of the Astar ecosystem and real benefits for ASTR holders. Looking forward to seeing how this develops!
Participation or contribution to Astar Network could happen in multiple ways. It is difficult to define what requirements are needed based on the product of the dApp itself. I believe that the use of the ASTR token is necessary to incentivize its visibility rather than the requirement of having the product on Astar EVM/Substrate. So yes, having projects from other chains that apply for dApp staking is a good idea.
Thank you so much for the proposal, yes, I totally agree that the project should bring value to Astar if they are supported by dApp staking, no matter it is about the token utility, or other type of value like TVL, volume. In particular, on Soneium or some other chains that will bridge the Astar to it, I would like to see the Astar token to be the main utility token in the eco!
I think it is essential to define clear requirements for external projects that want to access dApp Staking. The integration of the ASTR token should be an essential condition of course, demonstrating a real and tangible use as you said through payments, in-app utility, concrete benefits to holders.
We could evaluate for example an evaluation period to test the actual contribution of these projects to the Astar ecosystem (perhaps with easier and faster access to dApp staking but with shorter times on their delivery of reports).
I am happy with the changes just made and those that still need to be defined in the Astar ecosystem, let’s continue like this!
A project or dApp that is not native to Astar and therefore does not directly contribute to the activity of the L1 must still bring value to Astar in other ways. To access the benefits of dApp staking, it is essential that the project gives visibility to the ASTR token, increases its use, and integrates it meaningfully within its features. Only in this way can the project be considered for inclusion in the dappstaking program, showing it is contributing to the Astar ecosystem not just in terms of direct metrics, but also as a promoter and user of the ASTR token.
That being said, I believe it’s very important to include these dApps (deployed outside Astar L1) in the dApp staking program, because even though they may not bring on-chain activity, they would still provide visibility and utility to our token. Integrating ASTR into these projects, especially those on other blockchains, could amplify exposure and drive broader adoption, increasing interest in Astar and its token even outside of our direct ecosystem.
Some metrics that could be evaluated to determine a dApp’s contribution to the Astar ecosystem include:
Visibility of ASTR on the dApp
Utility of ASTR on the dApp (e.g., ASTR as a payment method, etc.)
Promotion of ASTR usage (e.g., incentives to use ASTR tokens with boosts, etc.)
References to the ASTR token or Astar on social media
These factors would help assess how the dApp is adding value to the Astar ecosystem, even if it’s not directly contributing to on-chain activity.
The $ASTR token should be the cornerstone here, the main requirement for listing new projects in our dApp Staking program, even if they’re not directly part of the Astar protocol but are within the Astar Collective.
The primary goal should be to increase the utility of the $ASTR token.
That’s why, in my view, any project not deployed directly on Astar Network should have a minimum of 60% usage of the $ASTR token. This could be implemented by using $ASTR as the gas token within the network, or by ensuring that most transactions within the project are carried out in $ASTR (or exclusively in this token).
The second requirement should be liquidity contribution to the token. For new projects, this might be a point of friction, but we aim to maintain tangible value for ASTR over time.
The third requirement will depend on the network the project is on, but a direct connection to Astar (if it’s on Polkadot) or to Soneium (if it’s on Ethereum) should be a key evaluation factor.
Thank you everyone for the thoughtful and constructive feedback.
Your input has highlighted several key priorities and considerations that we’ll be integrating into the updated dApp Staking guidelines for projects deployed outside the Astar Network.
Let me share a summary of the main points raised:
ASTR Token Integration : There is strong consensus that meaningful ASTR token utility must be a core requirement for any external project seeking dApp Staking eligibility. This can include use of ASTR as a payment method, in-app utility, or other features that provide tangible value to ASTR holders.
Commitment to Astar Ecosystem : Projects should show a long-term commitment to Astar’s growth and success. This includes sharing a clear roadmap, maintaining transparent communication, and providing regular reports (monthly or quarterly) on progress, contributions, and usage of ASTR within their platforms.
Flexibility with Accountability : While guidelines should accommodate a range of dApps with different models and deployments, there should still be measurable criteria and milestones to ensure ongoing alignment with Astar’s goals. Avoiding unnecessary bureaucracy while maintaining standards is a key balance.
Driving ASTR Utility and Adoption : Beyond on-chain metrics, there should be a demonstrated effort to increase the visibility, utility, and adoption of ASTR. This ensures that even if a dApp is not directly on Astar Network, it still plays a role in expanding the reach and relevance of our ecosystem.
Examples of meaningful contributions mentioned include:
Visibility of ASTR on the dApp interface or documentation
Utility of ASTR on the platform (e.g., payment method, gas token, in-app currency)
Incentives to use ASTR (e.g., discounts, rewards, staking boosts)
References to ASTR or Astar Network in marketing or social channels
Liquidity provision or TVL contribution involving ASTR
Direct or bridged integration with Astar or connected parachains (e.g., Polkadot, Soneium)
Community engagement initiatives that promote Astar or ASTR usage
I will now work to revise the guidelines accordingly. The Astar Community Council will review the new draft, and we will share the finalized version here for full community visibility and continued transparency.
I totally support this. Collaboration between the Astar brand and the projects that are part of Astar dApp Staking should exist and be driven by the community.
At this point, I’m not only thinking of X Spaces, AMAs, promotional flyers, and similar activities, but also of active campaigns to reward users, surveys, and expansion strategies that involve the Astar brand. This could be vital to identify those projects that are actively working to attract more users to their platforms.
Thanks for the summary, that’s great.
Regarding the reports, I think you should force the reporting of dApps on the blockchain outside of Astar Netwrok to be once a month. I think once a quarter is too little for these projects.
However, if significant and clear contributions are shown, the frequency could be reduced as a special exception, but at this time I think it would be better to limit the reporting to monthly.
absolutely agree.
In fact my previous comment saying that it would not be bad that the dApps initially in an evaluation period for external projects, I meant exactly this: Initially lower the delivery of reports to 1 time per month and if they meet the requirements increase it
Greetings, this is actually something I have wanted for a long time and I have mentioned it before.
I believe that other projects should be included in our dApp staking program. Nowadays some decentralized projects are bigger and more powerful than ecosystem projects (those with their own blockchain). By listing these projects, we can indirectly help ASTAR grow and make $ASTR a stronger collective through our unique product dApp Staking.
Of course there should be strict rules and strong filtering.
Our demands must be strict;
Projects must integrate Astar networks.
Projects should integrate the Astar Token or blockchain into their user-oriented campaigns or technical development-oriented events and competitions.
Integrate $ASTR into payment methods (this recommendation-technical compatibility may not work for some projects)
We should always give the opportunity to projects that have proven themselves before, that are known and strong. These should be projects that will bring us users, tvl, value, etc.
What Astar should focus on is enriching the Astar ecosystem. Otherwise, it risks losing gas fees that it would have otherwise received.
If there are great projects in other ecosystems, I believe the right approach is to replicate them within the Astar ecosystem.
Once a project in another ecosystem has been listed with Dapp Staking, reproducing it in the Astar ecosystem would be a betrayal of that project.
Ultimately, we need to address the shortage of developers, which requires fostering the developer community and enhancing the developer support capabilities of Dapp Staking.
However, we are currently discussing a proposal that may potentially reduce the developer support capabilities of Dapp Staking:
Therefore, I believe this proposal should be considered only after a decision has been made regarding Tokenomics 3.0.
I support this proposal; however, I believe that DAAPS STAKING should reclarify its original mission—to support developers and projects with unique decentralized applications—and redefine the eligibility criteria in a simpler and more transparent manner.
Eligibility Requirements
The project must offer its own original decentralized application (dApp).
The ASTR token must be used within the dApp either as a payment method or as a core utility function.
Additional Prohibitions
As a general rule, projects must not redistribute staking rewards directly to voting holders.
The following entities should be explicitly excluded from participation:
ASTR Core Contributors
Community Treasury
Rationale 1
Infrastructure development, community support, liquidity provision, and marketing are all vital and valuable activities. However, these should not be financed by DAAPS STAKING rewards.
Funding for initiatives that serve the broader ecosystem should come from the Treasury, in line with its intended function.
Rationale 2
When choosing where to stake, many holders tend to prioritize direct personal rewards over a project’s actual contribution to the ASTR ecosystem or its technical merit. In the absence of attractive DAPP candidates, holders often vote for entities such as Core Contributors or the Community Treasury, which are not DAPPs.
Redirecting these votes toward eligible DAPPs would raise their TIER ranking, increase their reward allocation, accelerate development, and enhance both the utility and market value of the ASTR token—creating a positive feedback loop for the ecosystem.
In summary, I recommend reinforcing the original intent of DAAPS STAKING—to grow the ecosystem by empowering real builders—and applying the above eligibility requirements and restrictions accordingly.
This topic is somewhat different from the current proposal (which focuses on whether to include dApps outside of the Astar Network, and if so, how to approach that), but I believe it’s still a subject worth discussing.
First, let me clarify the following two points (please correct me if anything is inaccurate):
Astar Core Contributors: Rewards generated here are used as market maker funding.
Community Treasury: Serves as the funding source for UCG, Agent compensation, etc.
While the funding source for UCG needs to be taken into consideration, both cases seem appropriate as DAO Treasury expenditures. Additionally, due to the name “Astar Core Contributors”, this option tends to attract more votes, which may unintentionally weaken the voting power allocated to individual dApps.
However, we should be careful not to simply remove these without proper alternatives. For example, Binance has designated the Community Treasury as its staking destination.
Exchange → Community Treasury → UCG → Individual dApps
Other exchanges may follow a similar model. As such, having delegators like exchanges select individual dApps directly is not a practical flow. Therefore, intermediary destinations like the Community Treasury are still necessary.
If needed, I suggest creating a separate thread to properly address this topic.
