-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Create linkora-polkadot-dex.md #2581
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
Conversation
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
|
I have read and hereby sign the Contributor License Agreement. |
|
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:** |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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?
|
pinging @wku |
|
Closing due to inactivity. Let us know if we should re-open. |
Project Abstract
Grant level
Application Checklist
project_name.md).@_______:matrix.org(change the homeserver if you use a different one)