From e388302ceed8f26f0af4b7e86c48ac082edff82f Mon Sep 17 00:00:00 2001 From: KariSaysWen <104957504+WenSwen199a@users.noreply.github.com> Date: Tue, 2 Jul 2024 15:12:55 +0800 Subject: [PATCH 1/5] Create BurveProtocol --- applications/BurveProtocol | 183 +++++++++++++++++++++++++++++++++++++ 1 file changed, 183 insertions(+) create mode 100644 applications/BurveProtocol diff --git a/applications/BurveProtocol b/applications/BurveProtocol new file mode 100644 index 00000000000..b102b4cec52 --- /dev/null +++ b/applications/BurveProtocol @@ -0,0 +1,183 @@ +# Name of your Project + +> This document will be part of the terms and conditions of your agreement and, therefore, needs to contain all the required information about the project. Don't remove any of the mandatory parts presented in bold letters or as headlines (except for the title)! Lines starting with a `>` (such as this one) should be removed. Please use markdown instead of HTML (e.g., `![](image.png)` instead of ``). +> +> See the [Grants Program Process](https://github.com/w3f/Grants-Program/#pencil-process) on how to submit a proposal. + +- **Team Name:** Legal name of your team (e.g. JsonCorp) +- **Payment Details:** + - **DOT**: For the **DOT** compensation, please provide a Polkadot address (e.g. 15oF4...). + - **Payment**: In case of payment in **USDC or USDT**, please provide a Polkadot AssetHub address and the currency (e.g. 15oF4... (USDC)). In the case of **fiat** payment, please share your bank account privately with grants@web3.foundation via your contact email (see below) and list here the date and time of your email (e.g. Fiat 24.12.1971, 11:59). +- **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 1, 2 or 3 + +> :exclamation: *The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the program. Please keep them safe.* + +## Project Overview :page_facing_up: + +If this application is in response to an RFP, please indicate this on the first line of this section. + +If this is an application for a follow-up grant (the continuation of an earlier, successful W3F grant), please provide the name and/or pull request of said grant on the first line of this section. + +### Overview + +Please provide the following: + +- If the name of your project is not descriptive, a tagline (one sentence summary). +- A brief description of your project. +- An indication of how your project relates to / integrates into Substrate / Polkadot / Kusama. +- An indication of why your team is interested in creating this project. + +### Project Details + +We expect the teams to already have a solid idea about your project's expected final state. Therefore, we ask the teams to submit (where relevant): + +- Mockups/designs of any UI components +- Data models / API specifications of the core functionality +- An overview of the technology stack to be used +- Documentation of core components, protocols, architecture, etc. to be deployed +- PoC/MVP or other relevant prior work or research on the topic +- What your project is *not* or will *not* provide or implement + - This is a place for you to manage expectations and clarify any limitations that might not be obvious + + +Things that shouldn’t be part of the application (see also our [FAQ](../docs/faq.md)): + +- The (future) tokenomics of your project +- For non-infrastructure projects—deployment and hosting costs, maintenance or audits +- Business-oriented activities (marketing, business planning), events or outreach + +### Ecosystem Fit + +Help us locate your project in the Polkadot/Substrate/Kusama landscape and what problems it tries to solve by answering each of these questions: + +- Where and how does your project fit into the ecosystem? +- Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? +- What need(s) does your project meet? +- How did you identify these needs? Please provide evidence in the form of (scientific) articles, forum discussions, case studies, or raw data. +- Are there any other projects similar to yours in the Substrate / Polkadot / Kusama ecosystem? + - If so, how is your project different? Please identify and assess any projects addressing the same need and explain how your project is distinct. Feel free to include applicable research data, statistics, or metrics. + - If not, please indicate why such a project might not have been possible, successful, or attempted. +- Are there any projects similar to yours in related ecosystems? + +## Team :busts_in_silhouette: + +> Please note that the data provided in this section is for administrative and informational purposes only. All beneficiaries of a grant must also be listed in the KYC/KYB process during the application phase. See our [FAQ](https://grants.web3.foundation/docs/faq#what-is-kyckyb-and-why-do-i-have-to-provide-this-data) for more info. + +### Team members + +- Name of team leader +- Names of team members + +### Contact + +- **Contact Name:** Full name of the contact person in your team +- **Contact Email:** Contact email (e.g. john@duo.com) +- **Website:** Your website + +### Legal Structure + +- **Registered Address:** Address of your registered legal entity, if available. Please keep it in a single line. (e.g. High Street 1, London LK1 234, UK) +- **Registered Legal Entity:** Name of your registered legal entity, if available. (e.g. Duo Ltd.) + +### Team's experience + +Please describe the team's relevant experience. If your project involves development work, we would appreciate it if you singled out a few interesting projects or contributions made by team members in the past. + +If anyone on your team has applied for a grant at the Web3 Foundation previously, please list the name of the project and legal entity here. + +### Team Code Repos + +- https://github.com/{your_organisation}/{project_1} +- https://github.com/{your_organisation}/{project_2} + +Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. + +- https://github.com/{team_member_1} +- https://github.com/{team_member_2} + +### Team LinkedIn Profiles (if available) + +- https://www.linkedin.com/{person_1} +- https://www.linkedin.com/{person_2} + + +## Development Status :open_book: + +If you've already started implementing your project or it is part of a larger repository, please provide a link and a description of the code here. In any case, please provide some documentation on the research and other work you have conducted before applying. This could be: + +- links to improvement proposals or [RFPs](https://github.com/w3f/Grants-Program/tree/master/docs/RFPs) (requests for proposal), +- academic publications relevant to the problem, +- links to your research diary, blog posts, articles, forum discussions or open GitHub issues, +- references to conversations you might have had related to this project with anyone from the Web3 Foundation, +- previous interface iterations, such as mock-ups and wireframes. + +## Development Roadmap :nut_and_bolt: + +This section should break the development roadmap down into milestones and deliverables. To assist you in defining it, we have created a document with examples for some grant categories [here](../docs/Support%20Docs/grant_guidelines_per_category.md). Since these will be part of the agreement, it helps to describe *the functionality we should expect in as much detail as possible*, plus how we can verify and test that functionality. Whenever milestones are delivered, we refer to this document to ensure that everything has been delivered as expected. + +Below we provide an **example roadmap**. In the descriptions, it should be clear how your project is related to Substrate, Kusama or Polkadot. We *recommend* that teams structure their roadmap as 1 milestone ≈ 1 month. + +> :exclamation: If any of your deliverables are based on somebody else's work, make sure you work and publish *under the terms of the license* of the respective project and that you **highlight this fact in your milestone documentation** and in the source code if applicable! **Projects that submit other people's work without proper attribution will be immediately terminated.** + +### Overview + +- **Total Estimated Duration:** Duration of the whole project (e.g. 2 months) +- **Full-Time Equivalent (FTE):** Average number of full-time employees working on the project throughout its duration (see [Wikipedia](https://en.wikipedia.org/wiki/Full-time_equivalent), e.g. 2 FTE) +- **Total Costs:** Requested amount in USD for the whole project (e.g. 12,000 USD). Note that the acceptance criteria and additional benefits vary depending on the [level](../README.md#level_slider-levels) of funding requested. + +### Milestone 1 Example — Basic functionality + +- **Estimated duration:** 1 month +- **FTE:** 1,5 +- **Costs:** 8,000 USD + +> :exclamation: **The default deliverables 0a-0d below are mandatory for all milestones**, and deliverable 0e at least for the last one. + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| **0a.** | License | Apache 2.0 / GPLv3 / MIT / Unlicense. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#license) for details. | +| **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Substrate nodes and send test transactions, which will show how the new functionality works. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#documentation) for details. | +| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#testing-guide) for details. | +| **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | +| 0e. | Article | We will publish an **article**/workshop that explains [...] (what was done/achieved as part of the grant). (Content, language, and medium should reflect your target audience described above.) | +| 1. | Substrate module: X | We will create a Substrate module that will... (Please list the functionality that will be implemented for the first milestone. You can refer to details provided in previous sections.) | +| 2. | Substrate module: Y | The Y Substrate module will... | +| 3. | Substrate module: Z | The Z Substrate module will... | +| 4. | Substrate chain | Modules X, Y & Z of our custom chain will interact in such a way... (Please describe the deliverable here as detailed as possible) | +| 5. | Library: ABC | We will deliver a JS library that will implement the functionality described under "ABC Library" | +| 6. | Smart contracts: ... | We will deliver a set of ink! smart contracts that will... + + +### Milestone 2 Example — Additional features + +- **Estimated Duration:** 1 month +- **FTE:** 1,5 +- **Costs:** 8,000 USD + +... + + +## Future Plans + +Please include here + +- how you intend to finance the project's long-term maintenance and development, +- how you intend to use, enhance, and promote your project in the short term, and +- the team's long-term plans and intentions in relation to it. + +## Referral Program (optional) :moneybag: + +You can find more information about the program [here](../README.md#moneybag-referral-program). + +- **Referrer:** Name of the Polkadot Ambassador or GitHub account of the Web3 Foundation grantee +- **Payment Address:** Polkadot/Kusama (USDT/USDC) payment address. Please also specify the currency. (e.g. 15oF4... (USDT)) + +## Additional Information :heavy_plus_sign: + +**How did you hear about the Grants Program?** Web3 Foundation Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. + +Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as: + +- Work you have already done. +- If there are any other teams who have already contributed (financially) to the project. +- Previous grants you may have applied for. From 0d3bb35fb81d385dbcbe1e48f19ad41aa26a6950 Mon Sep 17 00:00:00 2001 From: KariSaysWen <104957504+WenSwen199a@users.noreply.github.com> Date: Wed, 3 Jul 2024 15:50:22 +0800 Subject: [PATCH 2/5] Update BurveProtocol --- applications/BurveProtocol | 270 ++++++++++++++++++++++--------------- 1 file changed, 165 insertions(+), 105 deletions(-) diff --git a/applications/BurveProtocol b/applications/BurveProtocol index b102b4cec52..b796c517d59 100644 --- a/applications/BurveProtocol +++ b/applications/BurveProtocol @@ -1,116 +1,158 @@ -# Name of your Project +# Burve Protocol > This document will be part of the terms and conditions of your agreement and, therefore, needs to contain all the required information about the project. Don't remove any of the mandatory parts presented in bold letters or as headlines (except for the title)! Lines starting with a `>` (such as this one) should be removed. Please use markdown instead of HTML (e.g., `![](image.png)` instead of ``). > > See the [Grants Program Process](https://github.com/w3f/Grants-Program/#pencil-process) on how to submit a proposal. -- **Team Name:** Legal name of your team (e.g. JsonCorp) +- **Team Name:** Launch Labs Co., Ltd. - **Payment Details:** - - **DOT**: For the **DOT** compensation, please provide a Polkadot address (e.g. 15oF4...). - - **Payment**: In case of payment in **USDC or USDT**, please provide a Polkadot AssetHub address and the currency (e.g. 15oF4... (USDC)). In the case of **fiat** payment, please share your bank account privately with grants@web3.foundation via your contact email (see below) and list here the date and time of your email (e.g. Fiat 24.12.1971, 11:59). -- **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 1, 2 or 3 + - **DOT**: 1KxfCMkbZz2ueY3mkFGHzC55LgW6PuhqVGfJVPmhPdKWUEi + - **Payment**: 1KxfCMkbZz2ueY3mkFGHzC55LgW6PuhqVGfJVPmhPdKWUEi (USDC) +- **Level 2** -> :exclamation: *The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the program. Please keep them safe.* ## Project Overview :page_facing_up: +### Overview +- Project Name: Burve Protocol +- Tagline: The AMM 3.0 that innovates bonding curves for fair, LP-less, unruggable, and instantly tradable token launches, flexible and streamlined unilateral liquidity management, and a more efficient DeFi ecosystem. -If this application is in response to an RFP, please indicate this on the first line of this section. +#### Brief Description +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. -If this is an application for a follow-up grant (the continuation of an earlier, successful W3F grant), please provide the name and/or pull request of said grant on the first line of this section. +#### Integration with Substrate / Polkadot / Kusama +Burve Protocol leverages Substrate to build a robust, scalable, and interoperable solution within the Polkadot and Kusama ecosystems. By utilizing Substrate, we ensure that our protocol benefits from the security, scalability, and interoperability inherent in the Polkadot network. This integration allows Burve Protocol to connect with other parachains, fostering a more cohesive and efficient DeFi landscape. -### Overview +#### Team's Motivation +Our team comprises strong believers in innovation, DeFi, and the power of mathematics. We trust that combining mathematical principles with blockchain technology can lead to greater and more efficient financial freedom. While AMM solutions like Uniswap and order book AMMs have advanced the DeFi revolution, they also have significant drawbacks. Issues such as initial liquidity challenges, liquidity depletion, and potential manipulation by vested entities have highlighted the need for improvement. -Please provide the following: +Inspired by the potential of bonding curves, as discussed in [S. De la Rouvier's blog post](https://medium.com/@simondlr/a-bonded-curation-community-247f14a6de04), our researchers saw an opportunity to create a more inclusive financial future. We aim to integrate bonding curves into a wider range of applications, providing a holistic solution for token creation, minting, and exchange. This vision led to the creation of Burve Protocol, where we strive to offer innovative solutions to the current limitations of AMMs, thereby fostering a more inclusive and efficient DeFi economy. -- If the name of your project is not descriptive, a tagline (one sentence summary). -- A brief description of your project. -- An indication of how your project relates to / integrates into Substrate / Polkadot / Kusama. -- An indication of why your team is interested in creating this project. +Currently, there is no similar solution in the Polkadot ecosystem. As an indispensable infrastructure for the ecosystem, we believe that the services we provide are necessary, efficient, and essential for users. We can genuinely bring more interactions, transactions, smart contract deployments, and more users to Polkadot. ### Project Details +#### UI +Our MVP is based on Solidity and is already live, and the Polkadot version will be developed based on the Substrate tech stack and Polkadot structure with the same UI. [Check UI here](https://app.burve.io/). +#### Core API +**Launch**: +- Call the factory contract's `deployTokenWithHooks`. +#### Swap: +1. **Buy:** `mint` via the router contract. +2. **Sell:** `burn` via the token contract. +3. **Swap:** `swap` via the router contract. +**Update Token**: +1. **Info:** `setMetadata` via the token contract. +2. **Taxes, etc.:** `setProjectTaxRateAndTreasury` via the token contract. +#### Data Model +- Token Model +- Transaction Model +- User Model +#### Tech Stack: EVM Parallel Chain +- [Substrate](https://substrate.io/vision/substrate-and-polkadot/) Framework +- Parachain +**Contracts**: +- **Solidity**: Implementation of smart contracts on the chain. +**GraphQL**: +- **GraphQL**: Data query and statistical services. +**Frontend**: +- **React + SDK**: Data display and interaction between users and contract +#### Core components to be deployed +- **Connect Web3 Wallet**: Users link their Web3 wallet. +- **Interact with Contracts via Frontend**: Users interact with contracts through the front end. +- **Launch Various Types of Tokens**: Users can launch multiple types of tokens. +- **Buy or Sell Tokens**: Users can buy or sell tokens. +- **Update Token Information**: Users can update token information. +- **Request Token and Statistical Data via GraphQL**: Users can request token data and statistics through the front end using GraphQL. +#### Our research +- Our research paper on Bonding Curve and Burve Protocol was first presented at the EBES Conference, April 18-20, 2024, Berlin, Germany. Read [the Whitepaper here](https://burve.io/papers/Whitepaper_BurveLabs.pdf). +#### Expectation +- We will not limit users to use the app except those in OFAC countries. -We expect the teams to already have a solid idea about your project's expected final state. Therefore, we ask the teams to submit (where relevant): +### Ecosystem Fit +**Where and how does your project fit into the ecosystem?** +Burve Protocol fits into the Polkadot/Substrate/Kusama ecosystem as a versatile automated market maker (AMM) protocol designed to support a broad range of crypto use cases. Our protocol is open to all users, allowing anyone to create tokens and freely exchange them with anchor tokens. Specifically, we target blockchain projects, communities, key opinion leaders (KOLs), and general crypto users within the ecosystem. -- Mockups/designs of any UI components -- Data models / API specifications of the core functionality -- An overview of the technology stack to be used -- Documentation of core components, protocols, architecture, etc. to be deployed -- PoC/MVP or other relevant prior work or research on the topic -- What your project is *not* or will *not* provide or implement - - This is a place for you to manage expectations and clarify any limitations that might not be obvious +**Who is your target audience?** +Our target audience includes: +- Blockchain projects seeking efficient token creation and exchange solutions. +- Crypto communities aiming to grow and empower themselves through fair token launches. +- Key Opinion Leaders (KOLs) who want to engage their followers with unique token offerings. +- General crypto users looking for easy token creation and trading opportunities. +- Parachains in the Polkadot ecosystem need services to maximize their use cases, enabling more users to onboard, interact with their chains, and increase on-chain transaction volume. +**What need(s) does your project meet?** +Burve Protocol addresses several key needs: +- Easy creation of memecoins and any governance tokens. +- LP-less (liquidity pool-less), unruggable, fair, and instantly tradable token launches. +- Empowerment of community growth through token launches. +- Enhancement of Polkadot ecosystem DOT utility. +**How did you identify these needs?** +The need for fair token launches and community empowerment is evident from recent trends in the crypto market. The success of Bitcoin ordinals and Solana memes, both achieving over 100 times user growth, highlights the demand for fair launch platforms. -Things that shouldn’t be part of the application (see also our [FAQ](../docs/faq.md)): +For small projects, token launches are crucial for securing basic funding and growing their communities. Traditional ICOs are often out of reach due to size and volume requirements, and IDOs require initial liquidity, which small projects cannot afford. Thus, they need an alternative funding method that Burve Protocol provides. -- The (future) tokenomics of your project -- For non-infrastructure projects—deployment and hosting costs, maintenance or audits -- Business-oriented activities (marketing, business planning), events or outreach +For larger projects, enhancing token utility is a persistent challenge. Despite commercial success, such as Uniswap's revenue reaching $3.602 billion in April 2024, token prices may not reflect this success (e.g., Uniswap's UNI token price is around $9 now, down from over $42 in 2021). This gap underscores the need for better utility enhancement mechanisms, which Burve Protocol aims to address. -### Ecosystem Fit +Communities can also benefit by launching their memecoins or governance tokens to facilitate growth and transition to DAOs. +**Are there any other projects similar to yours in the Substrate / Polkadot / Kusama ecosystem?** +While there are launchpad projects in the Polkadot ecosystem, none offer the unique features of Burve Protocol. Our innovative use of bonding curve theory provides a fair, LP-less, unruggable, and effective token launch solution, alongside a unilateral liquidity management DEX solution. -Help us locate your project in the Polkadot/Substrate/Kusama landscape and what problems it tries to solve by answering each of these questions: +**Are there any projects similar to yours in related ecosystems?** +In related ecosystems, similar needs are partially addressed by projects like Uniswap and Balancer, which focus on providing liquidity pools and decentralized exchanges. However, these projects do not fully tackle the initial liquidity challenges and manipulation risks that Burve Protocol aims to solve with its unique approach to bonding curves and fair token launches. -- Where and how does your project fit into the ecosystem? -- Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? -- What need(s) does your project meet? -- How did you identify these needs? Please provide evidence in the form of (scientific) articles, forum discussions, case studies, or raw data. -- Are there any other projects similar to yours in the Substrate / Polkadot / Kusama ecosystem? - - If so, how is your project different? Please identify and assess any projects addressing the same need and explain how your project is distinct. Feel free to include applicable research data, statistics, or metrics. - - If not, please indicate why such a project might not have been possible, successful, or attempted. -- Are there any projects similar to yours in related ecosystems? ## Team :busts_in_silhouette: > Please note that the data provided in this section is for administrative and informational purposes only. All beneficiaries of a grant must also be listed in the KYC/KYB process during the application phase. See our [FAQ](https://grants.web3.foundation/docs/faq#what-is-kyckyb-and-why-do-i-have-to-provide-this-data) for more info. ### Team members - -- Name of team leader -- Names of team members +- Patrick (Co-Founder) +- AK (Co-Founder) +- Carl, Wurst, Kari, and other core-Contributors ### Contact - -- **Contact Name:** Full name of the contact person in your team -- **Contact Email:** Contact email (e.g. john@duo.com) -- **Website:** Your website +- **Contact Name:** Burve Help +- **Contact Email:** info@burve.io +- **Website:** https://burve.io/ ### Legal Structure - -- **Registered Address:** Address of your registered legal entity, if available. Please keep it in a single line. (e.g. High Street 1, London LK1 234, UK) -- **Registered Legal Entity:** Name of your registered legal entity, if available. (e.g. Duo Ltd.) +- **Registered Address:** Sea Meadow House, P.O. Box 116, Road Town, Tortola, British Virgin Islands +- **Registered Legal Entity:** Launch Labs Co, Ltd. ### Team's experience - -Please describe the team's relevant experience. If your project involves development work, we would appreciate it if you singled out a few interesting projects or contributions made by team members in the past. - -If anyone on your team has applied for a grant at the Web3 Foundation previously, please list the name of the project and legal entity here. +Our team comprises seasoned professionals with extensive backgrounds in both Web2 tech and Web3 blockchain sectors. Below, we highlight the key team members and their relevant experiences, alongside some noteworthy projects they have contributed to: +**Patrick (Co-Founder)** +- Former core-team member of a Binance-listed Project. +- Formerly worked at Meta and then at Litentry +- Alumnus of the University of Alberta. +**AK (Co-Founder)** +- Former core-team member of a Binance-listed Project. +- Co-founder of DIN, a BinanceLabs-invested Project +- Holds a PhD in Economics and a Master's Degree in IT. +- Experiences in Google and UC Berkeley. +**Carl, Wurst, and more (Core Contributors)** +- Former core developers in Binance-listed Projects. +- Experience from Tencent, Audi, and Hong Kong University. + +**Previous Grant Applications** +Both Web3Go and Litentry have applied for Web3 Foundation Grants, DIN (prev. Web3Go and Litentry, with [Web3Go Technology PTE. LTD](https://sg.linkedin.com/company/web3go-technology-pte-ltd) and [Litentry Technology Gmbh](https://www.linkedin.com/company/litentry/) respectively. No current Burve Protocol team members have individually applied for a Web3 Foundation grant, so this is our first time filling out Web3 Foundation Grants. Still, we have valuable insights from our involvement in similar projects. ### Team Code Repos - -- https://github.com/{your_organisation}/{project_1} -- https://github.com/{your_organisation}/{project_2} +- https://github.com/BurveProtocol/burve-contracts +- https://github.com/BurveProtocol/burve-graph Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. - -- https://github.com/{team_member_1} -- https://github.com/{team_member_2} +- Patrick: https://github.com/pxc23 +- AK: https://github.com/akburve ### Team LinkedIn Profiles (if available) - -- https://www.linkedin.com/{person_1} -- https://www.linkedin.com/{person_2} +- Patrick: https://www.linkedin.com/in/patrickcajinacortez/ +- AK: https://www.linkedin.com/in/alvis-kaiser-69952341/ ## Development Status :open_book: - -If you've already started implementing your project or it is part of a larger repository, please provide a link and a description of the code here. In any case, please provide some documentation on the research and other work you have conducted before applying. This could be: - -- links to improvement proposals or [RFPs](https://github.com/w3f/Grants-Program/tree/master/docs/RFPs) (requests for proposal), -- academic publications relevant to the problem, -- links to your research diary, blog posts, articles, forum discussions or open GitHub issues, -- references to conversations you might have had related to this project with anyone from the Web3 Foundation, -- previous interface iterations, such as mock-ups and wireframes. - +- Our research paper on Bonding Curve and Burve Protocol was first presented at the EBES Conference, April 18-20, 2024, Berlin, Germany. Read [the Whitepaper here](https://1657845912-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6RiyXfoC1Jp6FAmPYnBh%2Fuploads%2FfKqzixWxk15OgcKC8Glo%2FWhitepaper_BurveLabs.pdf?alt=media&token=93679f85-4e5b-490c-a2ed-ebecb6e46385). +- [Burve Version 1.0](https://burve.medium.com/unlock-fairness-burve-protocol-version-1-0-launching-in-february-2024-c6f9666f28ae) and [Burve Version 2.0](https://medium.com/@burve/burve-protocol-v1-1-unveiled-expanding-horizons-with-fomo-voting-and-enhanced-token-flexibility-98ddbaa4b9ec) +- [Burve Version 1.0 interface](https://v1-app.burve.io/) ## Development Roadmap :nut_and_bolt: This section should break the development roadmap down into milestones and deliverables. To assist you in defining it, we have created a document with examples for some grant categories [here](../docs/Support%20Docs/grant_guidelines_per_category.md). Since these will be part of the agreement, it helps to describe *the functionality we should expect in as much detail as possible*, plus how we can verify and test that functionality. Whenever milestones are delivered, we refer to this document to ensure that everything has been delivered as expected. @@ -121,49 +163,71 @@ Below we provide an **example roadmap**. In the descriptions, it should be clear ### Overview -- **Total Estimated Duration:** Duration of the whole project (e.g. 2 months) -- **Full-Time Equivalent (FTE):** Average number of full-time employees working on the project throughout its duration (see [Wikipedia](https://en.wikipedia.org/wiki/Full-time_equivalent), e.g. 2 FTE) -- **Total Costs:** Requested amount in USD for the whole project (e.g. 12,000 USD). Note that the acceptance criteria and additional benefits vary depending on the [level](../README.md#level_slider-levels) of funding requested. +- **Total Estimated Duration:** 4 months +- **Full-Time Equivalent (FTE):** 2,5 +- **Total Costs:** 30,000 USD -### Milestone 1 Example — Basic functionality - -- **Estimated duration:** 1 month -- **FTE:** 1,5 -- **Costs:** 8,000 USD - -> :exclamation: **The default deliverables 0a-0d below are mandatory for all milestones**, and deliverable 0e at least for the last one. +### Milestone 1 Example — Smart Contract Implementation and Product Launch +- **Estimated duration:** 2.5 month +- **FTE:** 2,5 +- **Costs:** 18,000 USD | Number | Deliverable | Specification | | -----: | ----------- | ------------- | -| **0a.** | License | Apache 2.0 / GPLv3 / MIT / Unlicense. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#license) for details. | -| **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Substrate nodes and send test transactions, which will show how the new functionality works. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#documentation) for details. | -| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#testing-guide) for details. | -| **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | -| 0e. | Article | We will publish an **article**/workshop that explains [...] (what was done/achieved as part of the grant). (Content, language, and medium should reflect your target audience described above.) | -| 1. | Substrate module: X | We will create a Substrate module that will... (Please list the functionality that will be implemented for the first milestone. You can refer to details provided in previous sections.) | -| 2. | Substrate module: Y | The Y Substrate module will... | -| 3. | Substrate module: Z | The Z Substrate module will... | -| 4. | Substrate chain | Modules X, Y & Z of our custom chain will interact in such a way... (Please describe the deliverable here as detailed as possible) | -| 5. | Library: ABC | We will deliver a JS library that will implement the functionality described under "ABC Library" | -| 6. | Smart contracts: ... | We will deliver a set of ink! smart contracts that will... +| 1.| Smart Contract Implementation | Complete the development and deployment of a smart contract using Polkadot and Substrate frameworks. The smart contract is available for access within the provided GitHub repository. | +| 2. | Product Launch | Deploy and launch the smart contract on Acala and Statemine Parachains using Substrate.| +| 3. | HODL Mode Support | Implement HODL mode allowing users to set tokens’ linear or exponential curve parameters for token launch. | +| 4. | Features Implementation | Integrate key features into the smart contract, including pre-mint, scheduled trading option, selectable anchor tokens (DOT, USDT, and proposed anchor tokens by Polkadot users), community FOMO or FUD vote, and fixed/adaptive max supply setting option. | +| 5. | Factory and Bonding Curve Smart Contracts | Develop factory smart contract and bonding curve smart contract for Polkadot's parachain.| +| 6. | Security Audits | Conduct 2x third-party security audits to ensure the smart contract's reliability and security.| -### Milestone 2 Example — Additional features +### Milestone 2 Product Feature Enhancement and Growth -- **Estimated Duration:** 1 month -- **FTE:** 1,5 -- **Costs:** 8,000 USD - -... +- **Estimated Duration:** 1.5 month +- **FTE:** 2,5 +- **Costs:** 12,000 USD +| Number | Deliverable | Specification | +| -----: | ----------| ----------------| +| 1 | Burve API for Trading Routing| Launch the Burve API for trading routing on Polkadot. | +| 2 | LOL Mode Support | Implement LOL mode where users do not need to set parameters; once a $33k market cap is reached, the token will automatically migrate to popular DEX(s) on Polkadot to create an LP and achieve a 3x to 5x price increase. | +| 3 | TG Bot Integration | Develop a TG bot for tracking and managing token launches, sales, and purchases in Polkadot. | ## Future Plans +### Long-Term Maintenance and Development Financing + +To ensure the long-term sustainability and continuous development of our project, we have established a robust financial strategy based on multiple revenue streams: + +- **Protocol Fees from Burve Launchpad:** Our primary source of revenue will be the protocol fees charged on transactions. For the HODL Token, we will collect 1% of the transaction volume, while for the LOL Token, we will collect between 1% and 2% of the transaction volume. These fees will provide a steady income stream, directly tied to the platform’s usage and success. +- **Liquidity Fees:** By providing liquidity in decentralized exchanges and liquidity pools, we will earn liquidity fees. This not only supports the platform’s financial health but also contributes to the stability and efficiency of the token ecosystem. +- **SDK Fees:** We will monetize our Software Development Kit (SDK) by charging a 5% fee on the revenue generated by users who integrate our SDK into their applications. This incentivizes widespread adoption and integration of our technology while generating additional revenue. + +This diversified approach to revenue generation ensures that we have the necessary financial resources to maintain and enhance our platform over the long term. + +### Short-Term Plans: Use, Enhancement, and Promotion -Please include here +**Project Outreach:** +- We plan to enhance project outreach through strategic collaborations with the Polkadot Foundation and the Polkadot Ecosystem. +- Engaging key opinion leaders (KOLs) and influencers to promote our project within the crypto community. +- Implementing community education programs to raise awareness and understanding of our platform’s unique features and benefits. + +### Long-Term Plans and Intentions + +**Continuous Feature Updates:** +- We are committed to continuous feature updates to ensure a smooth user experience and to foster innovation in DeFi within our platform. +- Regularly incorporating user feedback to improve and expand our platform's functionality. + +**Collaboration and Integration:** +- Collaborating with other projects within the Polkadot ecosystem to ensure interoperability and enhance our platform’s capabilities. +- Exploring partnerships with emerging projects to integrate new technologies and features that align with our vision. + +**Sustained Innovation and User Engagement:** +- Maintaining a focus on sustained innovation to keep our platform at the forefront of the crypto space. +- Implementing long-term user engagement strategies to build a loyal and active community around our platform. + +By leveraging these strategies, we aim to ensure the long-term success and sustainability of our project, continually enhancing its value proposition for all stakeholders involved. -- how you intend to finance the project's long-term maintenance and development, -- how you intend to use, enhance, and promote your project in the short term, and -- the team's long-term plans and intentions in relation to it. ## Referral Program (optional) :moneybag: @@ -175,9 +239,5 @@ You can find more information about the program [here](../README.md#moneybag-ref ## Additional Information :heavy_plus_sign: **How did you hear about the Grants Program?** Web3 Foundation Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. - -Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as: - -- Work you have already done. -- If there are any other teams who have already contributed (financially) to the project. -- Previous grants you may have applied for. +- Our co-founders have experience in Web3 Foundation funded projects, one is a core member of Litentry, and another is the ex-co-founder of DIN (ex-Web3Go), so they know of the program. +- Burve Protocol is based on Burve team's [academic research](https://burve.io/papers/Whitepaper_BurveLabs.pdf) on bonding curve theories and then implemented in the crypto space, so as a launchpad, it is innovation-driven with a user-friendly interface. From 7ee07a03ebe668df5a5550c0eca689cc690e08f6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebastian=20M=C3=BCller?= Date: Wed, 17 Jul 2024 08:50:30 +0200 Subject: [PATCH 3/5] Rename BurveProtocol to BurveProtocol.md --- applications/{BurveProtocol => BurveProtocol.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename applications/{BurveProtocol => BurveProtocol.md} (100%) diff --git a/applications/BurveProtocol b/applications/BurveProtocol.md similarity index 100% rename from applications/BurveProtocol rename to applications/BurveProtocol.md From 5c44d127db78c0242eee5601867c196f8d41bdd3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebastian=20M=C3=BCller?= Date: Fri, 26 Jul 2024 10:24:24 +0200 Subject: [PATCH 4/5] Update applications/BurveProtocol.md Fix markdown --- applications/BurveProtocol.md | 1 + 1 file changed, 1 insertion(+) diff --git a/applications/BurveProtocol.md b/applications/BurveProtocol.md index b796c517d59..ecf0e52bbc9 100644 --- a/applications/BurveProtocol.md +++ b/applications/BurveProtocol.md @@ -187,6 +187,7 @@ Below we provide an **example roadmap**. In the descriptions, it should be clear - **Estimated Duration:** 1.5 month - **FTE:** 2,5 - **Costs:** 12,000 USD + | Number | Deliverable | Specification | | -----: | ----------| ----------------| | 1 | Burve API for Trading Routing| Launch the Burve API for trading routing on Polkadot. | From 435b8fbf156560a04ae7fa921425d1f30183ba31 Mon Sep 17 00:00:00 2001 From: KariSaysWen <104957504+WenSwen199a@users.noreply.github.com> Date: Fri, 2 Aug 2024 14:49:17 +0900 Subject: [PATCH 5/5] Update BurveProtocol.md - Milestone 2 markdown table format fixed - Milestone 1 audit deliverable deleted --- applications/BurveProtocol.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/applications/BurveProtocol.md b/applications/BurveProtocol.md index ecf0e52bbc9..305bda93525 100644 --- a/applications/BurveProtocol.md +++ b/applications/BurveProtocol.md @@ -179,7 +179,6 @@ Below we provide an **example roadmap**. In the descriptions, it should be clear | 3. | HODL Mode Support | Implement HODL mode allowing users to set tokens’ linear or exponential curve parameters for token launch. | | 4. | Features Implementation | Integrate key features into the smart contract, including pre-mint, scheduled trading option, selectable anchor tokens (DOT, USDT, and proposed anchor tokens by Polkadot users), community FOMO or FUD vote, and fixed/adaptive max supply setting option. | | 5. | Factory and Bonding Curve Smart Contracts | Develop factory smart contract and bonding curve smart contract for Polkadot's parachain.| -| 6. | Security Audits | Conduct 2x third-party security audits to ensure the smart contract's reliability and security.| ### Milestone 2 Product Feature Enhancement and Growth @@ -190,9 +189,9 @@ Below we provide an **example roadmap**. In the descriptions, it should be clear | Number | Deliverable | Specification | | -----: | ----------| ----------------| -| 1 | Burve API for Trading Routing| Launch the Burve API for trading routing on Polkadot. | -| 2 | LOL Mode Support | Implement LOL mode where users do not need to set parameters; once a $33k market cap is reached, the token will automatically migrate to popular DEX(s) on Polkadot to create an LP and achieve a 3x to 5x price increase. | -| 3 | TG Bot Integration | Develop a TG bot for tracking and managing token launches, sales, and purchases in Polkadot. | +| 1. | Burve API for Trading Routing| Launch the Burve API for trading routing on Polkadot. | +| 2. | LOL Mode Support | Implement LOL mode where users do not need to set parameters; once a $33k market cap is reached, the token will automatically migrate to popular DEX(s) on Polkadot to create an LP and achieve a 3x to 5x price increase. | +| 3. | TG Bot Integration | Develop a TG bot for tracking and managing token launches, sales, and purchases in Polkadot. | ## Future Plans