You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Opportunity: What are the needs of our target user groups?
dApp developers seek platforms where their efforts and contributions to the ecosystem are recognized and rewarded. There's a need for a sustainable model that incentivizes the creation of high-quality, engaging, and user-retaining dApps. Users benefit from a richer ecosystem of applications, driving platform growth and engagement.
Strategic alignment: How does this problem align with our core strategic pillars?
This initiative aligns with "Developer Empowerment" and "Ecosystem Growth" by creating a direct incentive for developers to build applications that genuinely engage users, contributing to a thriving and dynamic EOS EVM ecosystem.
Context
Competitors: Who are our top competitors and why? How do they solve this problem today?
Many competitors primarily rely on transaction fees for network security without directly incentivizing application engagement. This model provides a base level of functionality but doesn't directly reward developers for creating compelling user experiences.
One competitor that has created programs like this is Fantom more information on their program and qualified applications can be found here.
Product differentiation: What would make our solution different?
Our solution focuses on directly rewarding dApp developers for their role in ecosystem growth, using a novel approach to gas fee redistribution that aligns developer incentives with user engagement and retention, potentially setting a new standard for developer support in the blockchain space.
Solution
Solution name: dApp Developer Gas Fee Redistribution
Purpose: Define the product’s purpose briefly
To implement a gas fee redistribution model within EOS EVM that rewards dApp developers based on their applications' ability to attract and retain users, encouraging the creation of more engaging and valuable dApps.
Success definition: What are the top metrics for the product to define success?
Increase in the number of active users across dApps on EOS EVM.
Growth in the number of high-engagement dApps developed on EOS EVM.
Measurable increase in user retention rates within incentivized dApps.
A portion of gas fees can be effectively redirected to developers without compromising network security or operational sustainability.
Developers are motivated by financial incentives directly tied to user engagement metrics.
Risks: What risks should be considered?
Potential for gaming the system, where developers find ways to exploit the incentive model without contributing genuine value.
Balancing the gas fee distribution between necessary network operations and developer incentives.
Business Objectives/Functionality
Develop a transparent and fair metric system for measuring dApp engagement and user retention.
Implement a mechanism within EOS EVM for collecting, tracking, and redistributing a portion of gas fees to qualifying dApps based on engagement metrics.
Stretch: Create a developer portal for tracking performance and earnings from the incentive program.
User stories
As a dApp developer, I want to be rewarded for creating applications that users find valuable and engaging, encouraging me to prioritize user experience in my development efforts.
As a user, I benefit from a wider range of high-quality dApps that enhance my overall experience on the EOS EVM platform.
Open questions
What specific engagement and retention metrics will be used to evaluate dApp performance?
How will the redistribution mechanism ensure fairness and transparency, preventing potential exploitation?
Possible future tasks
Establish a pilot program with select dApps to refine and adjust the incentive model before a full rollout.
Develop educational materials and workshops to assist developers in understanding how to maximize their benefits from the program.
The text was updated successfully, but these errors were encountered:
Gas Fee Redistribution
Problem
Opportunity: What are the needs of our target user groups?
dApp developers seek platforms where their efforts and contributions to the ecosystem are recognized and rewarded. There's a need for a sustainable model that incentivizes the creation of high-quality, engaging, and user-retaining dApps. Users benefit from a richer ecosystem of applications, driving platform growth and engagement.
Strategic alignment: How does this problem align with our core strategic pillars?
This initiative aligns with "Developer Empowerment" and "Ecosystem Growth" by creating a direct incentive for developers to build applications that genuinely engage users, contributing to a thriving and dynamic EOS EVM ecosystem.
Context
Competitors: Who are our top competitors and why? How do they solve this problem today?
Many competitors primarily rely on transaction fees for network security without directly incentivizing application engagement. This model provides a base level of functionality but doesn't directly reward developers for creating compelling user experiences.
One competitor that has created programs like this is Fantom more information on their program and qualified applications can be found here.
Product differentiation: What would make our solution different?
Our solution focuses on directly rewarding dApp developers for their role in ecosystem growth, using a novel approach to gas fee redistribution that aligns developer incentives with user engagement and retention, potentially setting a new standard for developer support in the blockchain space.
Solution
Solution name: dApp Developer Gas Fee Redistribution
Purpose: Define the product’s purpose briefly
To implement a gas fee redistribution model within EOS EVM that rewards dApp developers based on their applications' ability to attract and retain users, encouraging the creation of more engaging and valuable dApps.
Success definition: What are the top metrics for the product to define success?
Assumptions
Risks: What risks should be considered?
Business Objectives/Functionality
User stories
Open questions
Possible future tasks
The text was updated successfully, but these errors were encountered: