Skip to content

Conversation

@wku
Copy link

@wku wku commented Jun 28, 2025

Project Abstract

Please replace these instructions with a brief description of your project summarising key points (1-2 paragraphs).

If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

Grant level

  • Level 1: Up to $10,000, 2 approvals
  • Level 2: Up to $30,000, 3 approvals
  • Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

  • The application template has been copied and aptly renamed (project_name.md).
  • I have read the application guidelines.
  • Payment details have been provided (Polkadot AssetHub (USDC & DOT) address in the application and bank details via email, if applicable).
  • I understand that an agreed upon percentage of each milestone will be paid in vested DOT, to the Polkadot address listed in the application.
  • I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
  • The software delivered for this grant will be released under an open-source license specified in the application.
  • The initial PR contains only one commit (squash and force-push if needed).
  • The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
  • I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

@github-actions github-actions bot added the admin-review This application requires a review from an admin. label Jun 28, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Jun 28, 2025

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@wku
Copy link
Author

wku commented Jun 28, 2025

I have read and hereby sign the Contributor License Agreement.

@keeganquigley
Copy link
Collaborator

Thanks for the application @wku typically we don't fund DeFi related products such as DEXes. Is there a reason Hydration governance can't fund this?

- Unified liquidity pools accessible from multiple chains
- Cross-chain arbitrage prevention mechanisms

3. **Gas Optimization:**
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is needed in a WASM env? Since it is weight-based.

- **Cross-Chain**: XCM v3 for parachain interoperability

**Security Features:**
- Flash loan attack protection
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm assuming your production-ready code you mentioned targets Solidity contracts. How do you plan to refactor these to work with substrate runtime logic instead of smart contracts?

Recent analysis of the Polkadot ecosystem reveals that only 12% of parachains have integrated DEX functionality, primarily due to development complexity and resource constraints. Survey data from 50+ parachain teams indicates 78% would implement DEX features if turnkey solutions were available.

**Competitive Analysis:**
- **Polkadex**: Focuses on orderbook trading for specific use cases
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Polkadex is not an active project anymore afaik


**Competitive Analysis:**
- **Polkadex**: Focuses on orderbook trading for specific use cases
- **HydraDX**: Omnipool design for specific liquidity scenarios
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are called Hydration now.

**Existing Codebase Analysis:**
- Core AMM algorithms validated through extensive testing
- Gas optimization patterns proven in production environments
- Security measures battle-tested against common attack vectors
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't these common attack vectors be only for Solidity? Rust's design eliminates many Solidity issues, so I'm not sure how many of these would be helpful in a Substrate env. For example, the classic reentrancy attack isn't a thing in Rust due to the ownership/borrowing rules.

- Core AMM algorithms validated through extensive testing
- Gas optimization patterns proven in production environments
- Security measures battle-tested against common attack vectors
- Frontend components demonstrating user experience best practices
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Who is this front-end intended for? Would you actually be building a DEX?

@keeganquigley keeganquigley self-assigned this Jul 8, 2025
@github-actions github-actions bot added the stale label Jul 23, 2025
@keeganquigley
Copy link
Collaborator

pinging @wku

@keeganquigley
Copy link
Collaborator

Closing due to inactivity. Let us know if we should re-open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

admin-review This application requires a review from an admin.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants