Burve Protocol W3F Grant Application

[WenSwen199a]

Project Abstract

Burve Protocol is a cutting-edge AMM protocol designed to support a wide range of cryptocurrency use cases, from simple memecoin launches to sophisticated AMM solutions. Our protocol addresses the limitations of existing AMMs, such as initial liquidity challenges and potential manipulation, by integrating bonding curves inspired by S. De la Rouvier’s work. This allows for a more inclusive and efficient financial ecosystem, offering a seamless pathway for a token’s journey from creation and minting to exchange.

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 (DOT, USDC & USDT) address in the application and bank details via email, if applicable).
• I understand that 30% 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: @kari19says:matrix.org (change the homeserver if you use a different one)

[github-actions]

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. Please submit the following text as a separate comment:

---

I have read and hereby sign the Contributor License Agreement.

---

_{You can retrigger this bot by commenting recheck in this Pull Request}

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic High Entropy Secret	0d3bb35	applications/BurveProtocol	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[keeganquigley]

Thanks for the application @WenSwen199a

• It appears that the markdown table didn't work for milestone 2. Can you please fix this?
• We don't support the funding of audits. Therefore M1.6 can be removed.
• It appears that Burve Protocol is already live and well-established. What new components would you be building for Polkadot integration?
• Would the smart contracts need to be migrated or built from scratch?
• Would all code be open-source?

[PieWol]

Hey @WenSwen199a ,
there are some default deliverables that need to be included in your milestones. E.g. testing guide and license. Please check our website and FAQ.

[semuelle]

pinging @WenSwen199a

[WenSwen199a]

Thank you @keeganquigley @PieWol @semuelle !

• Milestone 2 table fixed
• Milestone 1.6 audit deliverable deleted
  [-] will add default deliverables to milestones tomorrow

[semuelle]

• will add default deliverables to milestones tomorrow

pinging @WenSwen199a

Also, please remember to sign the CLA.

[PieWol]

With the plans for smart contracts on AssetHub it will be possible to compile your Solidity code to PolkaVM so that you can simply port your project to Polkadot. See the roadmap here. Have you considered waiting for that moment? Given that Parity plans to achieve this until EOY it sounds like a wasted effort to me to now rewrite your whole tech to work on substrate. This way you could also conveniently integrate with all the assets already living on AssetHub so that you suffer no liquidity fragmentation which you raised as a concern yourself earlier in the application. Furthermore given that this transition towards enabling smart contracts on AssetHub will be iterative and starting on the testnet Westend, you could align your project with this strategy and do an experimental deployment on Westend or Kusama so that you can validate your project instead of having to deploy to Polkadot directly. What do you think?

[PieWol]

Hey @WenSwen199a ,
are there any updates you are able to share with us?

[Noc2]

I'm closing the application due to inactivity. Let me know if I should re-open it.