From 6bcef6f75075f2382f5368b42a0d7756fe6450ee Mon Sep 17 00:00:00 2001 From: mryings <110052573+mryings@users.noreply.github.com> Date: Fri, 27 Oct 2023 11:59:45 +0800 Subject: [PATCH] Demand Abstraction Based on Intent-centric and AI Agent.md --- ...on Based on Intent-centric and AI Agent.md | 182 ++++++++++++++++++ applications/application-template-research.md | 177 ----------------- 2 files changed, 182 insertions(+), 177 deletions(-) create mode 100644 applications/Demand Abstraction Based on Intent-centric and AI Agent.md delete mode 100644 applications/application-template-research.md diff --git a/applications/Demand Abstraction Based on Intent-centric and AI Agent.md b/applications/Demand Abstraction Based on Intent-centric and AI Agent.md new file mode 100644 index 00000000000..fd5e86261b4 --- /dev/null +++ b/applications/Demand Abstraction Based on Intent-centric and AI Agent.md @@ -0,0 +1,182 @@ +# Demand Abstraction Based on Intent-centric and AI Agent + +- **Team Name:** Demand abstraction +- **Payment Address:** 0x4a29F3f019b3A0E9C01b20d3922b5C4Fcb74B600 +- **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 2 + +## Project Overview :page_facing_up: + +With account abstraction (AA) and AI agent, we can upgrade intent-centric to demand abstraction as the ultimate way of user interaction on Web3, which is more natural, straightforward, and efficient than the current Web2 interaction based on Apps. + +With demand abstraction, users can directly express and meet their demands without going through specific accounts, DApps, and blockchains. After users specify their demands via user interface, text, or speech as inputs in our solution, our underlying AI agents will intelligently understand and analyze what users need, generate the best solution schemes to meet the demands of users and match the DApps and chains according to the solution scheme. After users check and approve the solution scheme, their AA account will automatically execute the solution scheme including running the corresponding DApps and operating multiple crypto assets to make transactions for users, and finally get what users want as execution results back to them. In this way, users can directly get what they need easily. + +Our demand abstraction solution will be fully open and decentralized. Although we will make a wallet as a sample to demonstrate and validate our demand abstraction, the demand abstraction functionality is open to all wallets to call and use. The third-party agents in AI and bundlers in AA are fully permissionless and decentralized, opening to all nodes to run and compete. After getting the execution results from third-party agents and bundlers, users can self-verify their correctness via the smart contract of AA as validation like zero-knowledge proofs. + +### Overview + +The high threshold, complexity and difficulty of user interactions and operations on blockchain are still too high to make Web3 usable for the ordinary users. For instance, if users want to convert USDT stablecoin in Ethereum into ARB token on Arbitrum, they need to find a suitable cross-chain bridge, connect to their account, then transfer their USDT and gas fee from Ethereum to Arbitrum, and then find a suitable DEX to exchange USDT for ARB with gas fee. It's so challenging, complicated, and troublesome for most users to understand and finish these steps by themselves. They have no way to simply express "I want to convert USDT into ARB", and then directly get ARB without taking all those actions above by themselves. In order to do so, Web3 should support AI agent to intelligently analyze user demands and automatically run Apps to perform the corresponding operations in Apps for users, so users don't need to manually do so by themselves. + +In our demand abstraction solution, after users express their specific demands via user interface, text, or speech as inputs, our underlying AI agent will intelligently understand them to analyze what users need, generate the best solution schemes to meet the demand of users, and then match the corresponding Apps according to the solution scheme. Based on the full inconnectuivity, interoperability and composability among Apps in Web3, our solution can automatically execute the solution scheme to run the corresponding Apps and perform the corresponding operations within Apps for users to get what they need. Finally we will get the execution results back to users to directly meet their demands in a highly efficient and intelligent way. + +### Project Details +Our experimental testing results show that with demand abstraction, we can attract 47% new crypto users to start making transactions on blockchain and exploring Web3 world. We also improve their trading efficiency by 62%, and increase their transaction volume by 1.8 times. For example, in the previous example, we can allow users to directly exchange their USDT for ARB without having to go through the tedious steps themselves. We can also transform various Web2 applications, such as helping users send their tweets to all social media accounts with one click, improving interaction efficiency and experience. + +Screenshot 2023-10-27 at 11 53 41 + +The process of demand abstraction would be users can put forward and clarify their needs through voice, text, and user interface, etc. Then the wallet will intelligently understand and analyze user needs, and then generate the best solution scheme to meet the needs of users. 
After confirmed by users, we will automatically connect, combine and run different crypto asset applications and services in Web3 to help users perform and complete all operations on their digital assets.Finally, we will return the running results to users to meet their needs. After verification and confirmation, users accept and directly obtain what they need. The whole process involves the following techniques: + +**Web3 and Blockchain:** Based on blockchain, Web3 can break the barriers and isolation of Web2 Apps for full interconnectivity, interoperatblity, and composablity among Web3 Apps. Web3 can also support automatic execution within Apps, so users don't need to manually operate each App by themselves. + +**AI Agent:** AI can intelligently understand the inputs of users via interface, text or speech to precisely analyze and get the demand of users. To meet user demands, AI will find, compare, choose, and combine all different Apps to generate the best solution schemes including what operations should be performed on which Apps. + +**Account Abstraction:** The decentralized bundlers enabled by account abstraction based on ERC-4337 can run their AI agent to generate the solution schemes for users. After getting users' authorization, they will execute the solution scheme to run and operate different Apps for users. Finally, they will get what users need back to users as the execution results. Different bunlders will compete with each other, so users can choose the best one to best meet their own demands. + +**Zero-knowledege Proofs:** Users can easily and quickly verify the correctness and effectiveness of both solution schemes and execution results provided by the bundlers. Users can also protect the privacy of their demands from being known or leaked by bundlers when getting and analyzing the demand of users. + +### Ecosystem Fit + +One major obstacle to the mass adoption of Polkadot is the relatively high threshold and unfriendly experience when users interact with Polkadot blockchain. The on-chain operations are still complicated, troublesome, and unfriendly especially for ordinary new users, impeding them from using DApps and exploring Web3 in the Polkadot ecosystem. Therefore we need to have a better way of Web3 interaction for users to directly meet their demands and omit the technical details of the underlying Polkadot blockchain and DApps. + +Therefore, our demand abstraction project can make the usage of Web3 not just as good as Web2, but even better than Web2 on Polkadot. Users can access and use Web3 in a more easy, natural, efficient, and convenient way. By providing a simpler and friendlier Web3 user experience, our demand abstraction can greatly lower the threshold, complexity, and difficulty of user interactions on Polkadot blockchain to onboard more users for the mass adoption of Web3. + +## Team :busts_in_silhouette: + +### Team members + +Blockchain Developer Myron Zhang +Blockchain Developer Emerson Dan +AI Developer Navein +AI developer Miguel Monares + +### Contact + +- **Contact Name:** Myron Zhang +- **Contact Email:** mryonzhang520@gmail.com +- **Website:** https://github.com/smarterwallet + +### Legal Structure + +- **Registered Address:** Tiantongyuan, Beijing, China +- **Registered Legal Entity:** Myron Zhang + +### Team's experience +We are a highly collaborative and productive team made up of talented developers, innovative researchers, and industry experts who graduated from UC Berkeley, UC San Diego, and CMU. We are all very interested and excel in blockchain, decentralized identity, crypto wallets, and account abstraction including their research, development, design, and business. We all have strong passion, great ambitions, and rich experiences in blockchain + AI innovation and Web3 entrepreneurship for a better future in the digital new cyberspace. + +Blockchain Developer **Myron Zhang** is the full stack developer of our project with strong capacity expertise in smart contracts and full stack development. He formerly worked in OKX where he led a team to develop a crypto wallet successfully there. He was also a solidity and backend developer in RCT AI. + +Polkadot Developer **Nathan Qiu** is the core developer of our project deployed on Polkadot. He is proficient in Rust and Polkadot development and had developed several blockchain projects in Rust. He was a senior Rust developer in Orderly Network and Bytedance. + +Blockchain Researcher **Emerson Dan** designs the decentralized AI automatic trading part of our project. He graduated from The Hong Kong University of Science and Technology (HKUST) with a major in Financial Mathematics. He had extraordinary expertise and hands-on experience in AI and DeFi trading. He was previously a crypto trader and analyst in Spectrum Lab - IKA Block, and an equity researcher in CMBI. + +AI Developer **Navein Suresh** majors in computer science and applied mathematics at UC Berkeley. He had strong programming skills in blockchain and AI with rich experiences in their research and development. He was the core AI developer in IcyTutors, and also the CaSGC Researcher in the Space Sciences Laboratory at UC Berkeley. + +AI developer **Miguel Monares** is an outstanding blockchain and AI developer majoring in Mathematics and Computer Science @ UC San Diego. He was an AI researcher and software engineer @ Intel Corporation and a blockchain research assistant @ National University of Singapore. + +We are all very thrilled about this project and fully devote ourselves to working on it. We hope to build our project based on Partisia because we all think Partisia is a very cutting-edge and promising blockchain, so we can not wait to develop our project with Partisia. We know each other well and we have worked together for a long time, so we will deliver our qualified and punctual outcomes in a highly reliable and efficient way. We also won the prize to attend Polkadot Blockchain Academy. + +### Team Code Repos + +https://github.com/zhangzhishun + +https://github.com/leidanwqq1 + +https://github.com/naveinsuresh + +https://github.com/miguelmonares + +https://github.com/fospring + +### Team LinkedIn Profiles (if available) + +https://www.linkedin.com/in/永春-丘-23a95213a + +https://www.linkedin.com/in/navein-suresh-b180a31b1/ + +https://www.linkedin.com/in/vtekriwal2211/ + +https://www.linkedin.com/in/miguelmonares/ + +## Development Status :open_book: + +Website: https://smarter.web3-idea.xyz/home + +Pitch deck: https://drive.google.com/file/d/1u0uONWl99sXoPNjWsGCtjUd8Es3-v6m3/view?usp=sharing + +Prototype: https://www.figma.com/proto/MfR5XzGUXiiWjE2heHJczK/User-Programmable-and-Self-Defined-AA-Wallet?node-id=0-3&scaling=scale-down&page-id=0:1&starting-point-node-id=0:3 + +Proposal: https://drive.google.com/file/d/1WiDDtx38q9hPDZ4TVYzjK8QOSI6ZTClI/view?usp=share_link + +## Development Roadmap :nut_and_bolt: + +### Overview + +- **Total Estimated Duration:** 5 months +- **Full-Time Equivalent (FTE):** 5 FTE +- **Total Costs:** 30,000 USD + +### Milestone 1 — Technical Research and Solution Design + +- **Estimated duration:** 2 months +- **FTE:** 4 +- **Costs:** 10,000 USD + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| **0a.** | Copyright and Licenses | CC0 | +| **0b.** | Documentation/Tutorial | We will provide both **artifacts documentation** of the deliverables and a basic **tutorial** that explains how a user can directly express and meet their demands via our demand abstraction. | +| **0c.** | Methodology | We will conduct technical testing and user evaluation to validate and improve our solution. | +| **0d.** | Infrastructure | We will provide the list of all infrastructure requirements that can be used to verify the deliveries with this milestone. We will use Overleaf for article production and Docker files for software execution. | +| **0e.** | Article | We will send an **article** with source code that explains the design thinking and technical specifications of our demand abstraction in the English language. For level 2 and 3 grants, The article will acknowledge that this work was supported by the research grant from the Web3 Foundation. | +| 1. | List of academic papers regarding demand abstraction | We will systematically search the literature about demand abstraction and deliver a list of papers to read with web links to them. | +| 2. | Data to be extracted from the papers | Data fields with the explanation of each that will be extracted from the papers related to demand abstraction | +| 3. | Analysis procedures | We gonna describe all the procedures planned for the analysis that will be conducted in the next milestone. | + + +### Milestone 2 — Sample Demo Development + +- **Estimated Duration:** 2 months +- **FTE:** 5 +- **Costs:** 10,000 USD + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| **0a.** | Copyright and Licenses | CC0 | +| **0b.** | Documentation/Tutorial | We will provide both **artifacts documentation** of the deliverables and a basic **tutorial** that explains how a user can use our sample wallet to directly express and meet their demands via demand abstraction. | +| **0c.** | Methodology | We will conduct technical testing and user evaluation to validate and improve our sample wallet. | +| **0d.** | Infrastructure | We will provide the list of all infrastructure requirements that can be used to verify the deliveries with this milestone. We will use Overleaf for article production and Docker files for software execution. | +| **0e.** | Article | We will send an **article** with source code that explains the interface design and technical configurations of our sample wallet with demand abstraction in the English language. For level 2 and 3 grants, The article will acknowledge that this work was supported by the research grant from the Web3 Foundation. | +| 1. | Source code | Finish the development of our demand abstraction sample wallet on Polkadot and provide its source code. | +| 2. | Prototype | Design the user interface and intereaction of our demand abstraction sample wallet as a mobile application. | +| 3. | Smart contract | Finish the development of our demand abstraction sample wallet on Polkadot and provide its !ink smart contract. | + + +### Milestone 3 — Demo Launch and Paper Publication + +- **Estimated Duration:** 1 months +- **FTE:** 5 +- **Costs:** 10,000 USD + +| Number | Deliverable | Specification | +| -----: | ----------- | ------------- | +| **0a.** | Copyright and Licenses | CC0 | +| **0b.** | Documentation/Tutorial | We will provide both **artifacts documentation** of the deliverables and a basic **tutorial** that explains how our demand abstraction runs and sample wallet demo works. | +| **0c.** | Methodology | We will conduct technical testing and user evaluation to validate and improve our demand abstraction and sample wallet as demo. | +| **0d.** | Infrastructure | We will provide the list of all infrastructure requirements that can be used to verify the deliveries with this milestone. We will use Overleaf for article production and Docker files for software execution. | +| **0e.** | Article | We will send an **article** with source code that explains the development and testing of our sample wallet and the design and research of our demand abstraction in the English language. For level 2 and 3 grants, The article will acknowledge that this work was supported by the research grant from the Web3 Foundation. | +| 1. | Testing report | Finish the technical testing and user evaluation of our demand abstraction demo wallet on test net including testing plan, specifications, and results. | +| 2. | Official launch | Release our demand abstraction demo wallet on main net and make it runnable and usable open to the Polkadot ecosystem and community. | +| 3. | Research publication | Write and publish our demand abstraction research paper on peer-reviewed academic journal or conference. | + + +## Future Plans + +1. Maintain and improve our demand abstraction consistently and upgrade the following new versions of our sample wallet demo +2. Design token economy, issue our token and distribute to seed users, early adopters, and core contributors to reward them +3. Design and implement our marketing strategies and promotion activities to have $15k+ trading volume and $2k+ transaction fees as revenue per month +4. Maintain and develop our demand abstraction research community to have 1k+ active members with corresponding returns as incentives + +## Additional Information :heavy_plus_sign: + +**How did you hear about the Grants Program?** Web3 Foundation Website + +We have finished the initial research and general design on the feasibility and value of our solution. We haven't started the offical research and development so we haven't dived deep into the technical details yet. We are looking for more talents to build together and we have received very positive feedback from our seed users and researchers in the community. After getting the grant we will begin the formal research, design and development. Therefore look forward to your constructive critiques, potential partnership and valuable support! diff --git a/applications/application-template-research.md b/applications/application-template-research.md deleted file mode 100644 index 21591ec65c0..00000000000 --- a/applications/application-template-research.md +++ /dev/null @@ -1,177 +0,0 @@ -# Name of your Research Project1 - -> 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 Address:** In the case of fiat payment, please share your bank account privately with grants@web3.foundation via your contact email (see below) and enter the date when you shared the information with us (e.g. Fiat 24.12.1971, 11:59) here. Otherwise, provide the Polkadot ( for USDC & USDT) or Bitcoin payment address. Please also specify the currency. (e.g. 0x8920... (USDC)) -- **[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 the said grant on the first line of this section. - -### Overview - -Please provide the following: - -- If the name of your project is not descriptive, a tag line (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. -- An indication if your project is academic research, i.e., intended to be published in an academic peer-reviewed venue, or a technical one, to be published as a technical report on the internet. - -### 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): - -- The problem(s) that you want to investigate, and why these are important. -- Research questions/hypothesis. -- The methodology that will be applied. -- The data collection and analysis procedures. -- The expected results and how they would be double-checked by the grants team (reproducibility of the data analysis). -- Relevant related work. -- Intended venue for results publication and the timeline for publication. -- 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 -- 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? -- Are there any other projects similar to yours in the Substrate / Polkadot / Kusama ecosystem? - - If so, how is your project different? - - If not, are there similar projects in related ecosystems? - -## Team :busts_in_silhouette: - -### 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. For research-related grants, references to past publications and projects in a related domain are helpful. - -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// -- https://github.com// - -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/ -- https://github.com/ - -### Team LinkedIn Profiles (if available) - -- https://www.linkedin.com/ -- https://www.linkedin.com/ - -### Google Scholar Profiles (Or other research indexer profile, ex. Researchgate) - -- https://scholar.google.com/citations?user= -- https://scholar.google.com/citations?user= - -## Development Status :open_book: - -If you've already started working on your project or it is part of a larger project, please provide a link and a description of the research 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. - -## Development Roadmap :nut_and_bolt: - -This section should break the research development roadmap down into milestones and deliverables. To assist you in defining it, we have created a document with examples for some grant categories, including research [here](../docs/Support%20Docs/grant_guidelines_per_category.md). Since these will be part of the agreement, it helps to describe *the deliverable we should expect in as much detail as possible*, plus how we can verify that deliverable. 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 is based on somebody else's work, make sure you cite it. If your research contains software artifacts in the same situation, 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! **Teams that submit others' work without attributing it 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. This and the costs for each milestone need to be provided in USD; if the grant is paid out in Bitcoin, the amount will be calculated according to the exchange rate at the time of payment. - -### Milestone 1 Example — Literature Review and Data Collection - -- **Estimated duration:** 1 month -- **FTE:** 1,5 -- **Costs:** 8,000 USD - -> :exclamation: **The default deliverables 0a-0e below are mandatory for all milestones**. - -| Number | Deliverable | Specification | -| -----: | ----------- | ------------- | -| **0a.** | Copyright and Licenses | CC0 / CC BY 4.0 / Apache 2.0 / GPLv3 / MIT / Unlicense | -| **0b.** | Documentation/Tutorial | We will provide both **artifacts documentation** of the deliverables and a basic **tutorial** that explains how a user can (for example) execute the code included or can visualize data or use any artifacts included. | -| **0c.** | Methodology | Detailed explanation of how the results were achieved and how to reproduce/verify the results. | -| **0d.** | Infrastructure | We will provide the list of all infrastructure requirements (text editors with proper versions, software packages, data packages, etc) that can be used to verify the deliveries with this milestone. Ideally, we recommend the usage of LaTeX/Overleaf for article production and Docker files for software execution. | -| **0e.** | Article | We will send an **article** or part of it (with source code) that explains in the English language [...] (what was done/achieved as part of the grant). (Content, language and medium should reflect your target audience described above.). For level 2 and 3 grants, the article must contain the following statement in an acknowledgments section: This work was supported by a research grant from the Web3 Foundation. | -| 1. | List of academic papers regarding X | We will systematically search the literature about X and deliver a list of papers to read with web links to them | -| 2. | Data to be extracted from the papers | Data fields with the explanation of each that will be extracted from the papers ... | -| 3. | Analysis procedures | We gonna describe all the procedures planned for the analysis that will be conducted in the next milestone ... | - - -### Milestone 2 Example — Data Analysis - -- **Estimated Duration:** 1 month -- **FTE:** 1,5 -- **Costs:** 8,000 USD - -... - - -## Future Plans - -Please include here - -- how you intend to use, enhance, promote and support 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:** BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) payment address. Please also specify the currency. (e.g. 0x8920... (DAI)) - -## 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.