Summary
This proposal recommends allocating 0.5% of the Meteora token supply to community-built tools that have meaningfully contributed to the growth and usability of the Meteora ecosystem. These tools, created and maintained by long-term community members, serve as critical middleware and data layers that improve the DeFi user experience on Meteora. The allocation will be distributed with a one-year linear vesting schedule.
For context, I am one of the co-founders of MetEngine. We have made $ 7 M+ in LP Deposits on Meteora through our bot, and our users have made $130k+ in profits in just 2.5 weeks with Auto Lping.
The community tools list maintained by Meteora can be found here.
Motivation
The Meteora ecosystem has benefited from several community-driven tools that either:
- Act as middleware, simplifying user interaction with Meteora, or
- Provide read/data layers, enabling deeper insight and analytics on Meteora activity.
These tools have played a pivotal role in onboarding users, increasing TVL, and enhancing transparency. Recognizing and rewarding these contributors will incentivize innovation and long-term alignment with the protocol.
1. Middleware Tools
These tools facilitate actions like liquidity provisioning, strategy automation, and user onboarding.
Suggested Evaluation Metrics:
- LP deposit volume driven to Meteora via the tool
- Number of unique users utilizing the tool
Examples:
- MetEngine
- LpAgent
- Cleopetra
Verification should be done on-chain or through verifiable analytics dashboards.
2. Read/Data Layer Tools
These tools provide visibility, tracking, and analytics to the community, offering insight into the performance of positions and position analytics.
Suggested Evaluation Metrics:
- Weekly/monthly active users.
- Any unique metrics/data provided by them.
Examples:
- RPS AI
- Metalex Dashboard
- Honk Index
- Meteora AI
Metrics should be demonstrable through usage analytics or open dashboards.
- DBC Tools
The Dynamic Bonding Curve (DBC) program is a permissionless launch pool protocol that allows any launch partners to enable their users to launch tokens with customizable virtual curves directly on their platform (e.g. launchpad).
Suggested Evaluation Metrics:
- TVL is done by tokens launched by their platform.
- The number of users using their platform.
The number of tokens launched shall not be considered as it doesn’t add much value and can be botted.
Proposal
- Allocate 0.5% of the Meteora airdrop to be distributed among the qualifying community tools; the number 0.5% is negotiable and is for the Meteora team to decide.
- Distribution will occur via a 1-year linear vesting schedule.
- Eligibility will be determined based on transparent, verifiable data (either on-chain or via usage metrics).
- The list of eligible tools may expand or contract based on future community review and available data.
Conclusion
Supporting community tools with a meaningful airdrop allocation reinforces the value of open development and long-term alignment with the Meteora ecosystem. This proposal ensures that contributors who build and maintain infra receive fair recognition for their efforts.
I would love to hear thoughts of the community on this proposal and receive feedback on it.