-
Notifications
You must be signed in to change notification settings - Fork 2
GS-004: MEV Resistance #32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
0af0d41
Add new RFP: Make It Make Sense: Build with Anti-MEV (GS-004)
gsmachado 427a24a
Update RFP GS-004: Revise title and details to focus on MEV resistanc…
gsmachado 24a1f21
Refactor RFP GS-004: Change note formatting to warning, update curren…
gsmachado 8fccdf9
Fix typo.
gsmachado 20c1e8f
Update RFP GS-004: Correct hyperlink formatting for MEV protection re…
gsmachado d791fee
Enhance RFP GS-004: Clarify evaluation criteria by adding submission …
gsmachado File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,94 @@ | ||
| --- | ||
| --- | ||
|
|
||
| # Make It Make Sense: Build with MEV Resistance Tech | ||
|
|
||
| <a id="general-info"></a> | ||
| **General Info:** | ||
|
|
||
| | Attribute | Value | | ||
| |-----------|-------| | ||
| | **RFP ID** | GS-004 | | ||
| | **Author(s)** | [AxLabs](https://axlabs.com) on behalf of BaneLabs and [Neo X](https://x.neo.org) | | ||
| | **Published Date** | 2025-10-08 | | ||
| | **Submissions by** | 2025-11-05 | | ||
|
|
||
| **Changelog:** | ||
|
|
||
| | Version | Date | Changes | | ||
| |---------|------|---------| | ||
| | 1.0 | 2025-10-05 | Initial Release | | ||
|
|
||
| --- | ||
|
|
||
| ## Description | ||
|
|
||
| We invite developers to create small, illustrative demo projects that showcase MEV resistance technology on the [Neo X](https://x.neo.org/) EVM-compatible sidechain. **The goal is to produce simple, easy-to-understand project examples, like games, token swap demos, or bidding mechanisms, that highlight how MEV resistance works and why it matters.** | ||
|
|
||
| :::warning[Note] | ||
| Unlike typical GrantShares proposals that **typically** fund work before it begins, this RFP is different. It operates on a retroactive basis. Developers are expected to **build their projects first**, and then submit completed work for evaluation and potential funding. | ||
| ::: | ||
|
|
||
|
|
||
| ## Why This RFP? | ||
|
|
||
| [Neo X introduces MEV protection](https://neo-blockchain.medium.com/neo-x-mainnet-v0-4-2-upgrade-anti-mev-now-live-b72e3d89e14b) (Maximum Extractable Value) to help secure transactions from [MEV-related risks](https://neo-blockchain.medium.com/how-neo-eliminates-toxic-mev-d0ecd3ff5717). We want to educate the community and provide real-world examples that other developers can reference. By keeping these projects small and focused, we aim to build a library of tutorial-like demos that illustrate the use of MEV resistance in the Neo ecosystem. | ||
|
|
||
| ## Scope and Eligibility | ||
|
|
||
| - **Who Can Apply**: Individual developers or small teams familiar with EVM-based development. | ||
| - **Project Scope**: Each project should be a small, standalone demo (not a large-scale app) that uses MEV resistance on Neo X MainNet. Examples could include a simple game, a token swap demo, or a basic bidding scenario. | ||
| - **Repo Structure**: If the project includes a back-end, front-end dApp, and smart contracts, we encourage using a single monorepo with a well-structured layout. This makes it easier for others to understand and reuse. | ||
|
|
||
| :::warning[Note] | ||
| This is a competitive RFP with a **limited number of rewards**. Up to 4 submissions will be selected for funding. Submitting a proposal does **not guarantee** that your project will be endorsed or funded, even if it meets all minimum KPIs. DAO Members will evaluate all proposals based on **quality**, **clarity**, **impact**, and **submission priority**. Earlier submissions demonstrating novelty and originality will be given higher consideration to discourage duplication of ideas or code. | ||
| ::: | ||
|
|
||
| ## Deliverables (Core KPIs) | ||
|
|
||
| 1. **Use of MEV Resistance**: The demo must utilize MEV-resistant envelope transactions on Neo X. | ||
| 2. **Comparative Example**: Show a scenario with and without MEV resistance to illustrate the difference. | ||
| 3. **On-Chain Deployment**: Must be deployed on Neo X MainNet and publicly accessible. | ||
| 4. **Open Source Code**: All code must be under a permissive open-source license (MIT or Apache 2.0). | ||
| 5. **Front-End Interface**: Include a simple front-end UI for demonstration. | ||
| 6. **README and Documentation**: Provide a README with build instructions, technical requirements, and an overview of the project structure. | ||
| 7. **Video Demo (3–5 Minutes)**: A short video walkthrough of the project and its use of MEV resistance. The video should be public. | ||
| 8. **Post-Mortem Report**: A brief (1 pager) summary of what was built, how MEV resistance was integrated, and any feedback from using the technology (this is important for us!). | ||
|
|
||
| ## Budget | ||
|
|
||
| - **Total Budget of this RFP**: \$8,000 USD in equivalent \$GAS tokens. | ||
| - **Per Project Grant**: \$2,000 USD in equivalent of \$GAS tokens, for up to 4 projects. | ||
| - **Expected Effort**: Each project should be something that could be completed in roughly max. 4 weeks. | ||
| - **Submission Process**: This is a **retroactive** grant. Build the project **first**, then submit a proposal on GrantShares requesting the \$2,000 grant upon completion. | ||
|
|
||
| ## Additional Incentives | ||
|
|
||
| Selected projects will be featured on our social media channels and other platforms, providing additional exposure to your work. | ||
|
|
||
| ## How to Apply? | ||
|
|
||
| 🚨 **Pay attention to the following when creating your proposal:** | ||
|
|
||
| - Submit a proposal via the GrantShares dApp under the category "Request For Funding". | ||
| - Include 'GS-004: Your Project Name' in the title. Example: `GS-004: Fair Tetris`. | ||
| - Write your proposal based on what this RFP requests. Describe what you built, how you built it, and include links to the deliverables/KPIs. | ||
| - **Be sure to request GAS tokens, not NEO tokens**. Your ‘Request for Funding’ proposal should be capped at \$2,000 USD in GAS token equivalent. Projects requesting more will not be considered. | ||
| - Provide as much detail as possible about your project so that the community and DAO Members can easily verify your work. | ||
|
|
||
| :::danger[Important] | ||
| Please, **do not** put the proposal on-chain BEFORE the RFP's [Submissions by](#general-info) deadline date. You can put it on-chain right after the deadline -- allowing all applicants to have the same amount of time to submit their proposals. | ||
| ::: | ||
|
|
||
| :::danger[Important] | ||
| We will not accept any applications via email, Discord, Telegram, or other channels. | ||
| ::: | ||
|
|
||
| ## Timeline | ||
|
|
||
| - Proposals must be submitted through the GrantShares dApp under "Request for Funding" by **5th November**. | ||
| - Proposals may only be put on-chain **on or after 5th November**. | ||
| - Any proposals submitted on-chain **before** 5th November will **not be considered**. | ||
| - DAO members will review all valid proposals shortly after they are submitted on-chain. | ||
|
|
||
| Questions? Connect with us through [Email](mailto:info@grantshares.io), [Discord](https://discord.gg/rvZFQ5382k), or [X](https://x.com/GrantShares). | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.