-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
add queryweb3 #2458
add queryweb3 #2458
Conversation
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. 1 out of 2 committers have signed the CLA. |
I have read and hereby sign the Contributor License Agreement. |
The applicant has requested the discussion of the application to happen in a private chat room. |
Thanks for the application, @lechangxu. I will review it as soon as possible (we are rather busy at the moment) and leave questions and/or notes in the chat room linked above. |
recheck |
applications/queryWeb3.md
Outdated
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.** |
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.
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.** |
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.
Done
applications/queryWeb3.md
Outdated
### Team LinkedIn Profiles (if available) | ||
|
||
- https://www.linkedin.com/{person_1} | ||
- https://www.linkedin.com/{person_2} | ||
|
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.
### Team LinkedIn Profiles (if available) | |
- https://www.linkedin.com/{person_1} | |
- https://www.linkedin.com/{person_2} |
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.
Done
applications/queryWeb3.md
Outdated
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. | ||
|
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.
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. |
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.
Done
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.
@lechangxu good to see you again here, after e-meeting you on Dr Cao's X space the other day. 👍
I have one initial request: Could you please reply directly in the GitHub thread, rather than replying via email? Currently, your comments are very verbose, and they're difficult to understand for that reason.
In addition to that, could you provide additional clarification on a few points related to your data sources and API integration?
In particular:
1) Specific APIs and Endpoints
- While you mention Subscan, Hydration, and Bifrost APIs, could you provide a more comprehensive list of APIs and endpoints you plan to integrate? Ideally, this should be directly included as part of the milestone deliverables.
- Are there any specific considerations for rate limits, scalability, or handling data discrepancies for these APIs?
2) Integration Details
- How do you plan to technically integrate with these APIs? For example, will you use custom parsers, standard SDKs, or third-party middleware?
- Could you elaborate on the methods you’ll use to validate and normalize the data collected from these sources? Or is that something that is not needed to train your model?
3) Handling Other Data Categories
- In Use Case 1, you mention aggregating data such as document data, technical code, TG (Telegram) data, DC (Discord) data, X (Twitter) data, media data, and video data. Could you clarify the sources and methods for collecting this information?
applications/queryWeb3.md
Outdated
|
||
Use Case 2: Yield Query | ||
|
||
- Business Description:allows users to query snapshots of various chains within the Polkadot ecosystem (e.g., DOT, KSM, Hydration, Bifrost, etc.) on any given day. Users can search for all asset types (RWA or DeFi) and all yield types (staking, farming), including all tokens (DOT, KSM, HDT, vDOT, vKSM, BNC, etc.). The query results will list the TVL (Total Value Locked), 24-hour trading volume, and the number of transactions for each token or currency pair. Additionally, based on these query results, our platform can display the top 10 yield rates in the Polkadot ecosystem, the top 10 chains by TVL, and various visual representations such as line charts, pie charts, or other graphical formats. This information is designed to provide investors and operators with valuable insights for making informed investment and operational decisions. |
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.
- Business Description:allows users to query snapshots of various chains within the Polkadot ecosystem (e.g., DOT, KSM, Hydration, Bifrost, etc.) on any given day. Users can search for all asset types (RWA or DeFi) and all yield types (staking, farming), including all tokens (DOT, KSM, HDT, vDOT, vKSM, BNC, etc.). The query results will list the TVL (Total Value Locked), 24-hour trading volume, and the number of transactions for each token or currency pair. Additionally, based on these query results, our platform can display the top 10 yield rates in the Polkadot ecosystem, the top 10 chains by TVL, and various visual representations such as line charts, pie charts, or other graphical formats. This information is designed to provide investors and operators with valuable insights for making informed investment and operational decisions. | |
- Business Description:allows users to query snapshots of various chains within the Polkadot ecosystem (e.g., Polkadot, Kusama, Hydration, Bifrost, etc.) on any given day. Users can search for all asset types (RWA or DeFi) and all yield types (staking, farming), including all tokens (DOT, KSM, HDT, vDOT, vKSM, BNC, etc.). The query results will list the TVL (Total Value Locked), 24-hour trading volume, and the number of transactions for each token or currency pair. Additionally, based on these query results, our platform can display the top 10 yield rates in the Polkadot ecosystem, the top 10 chains by TVL, and various visual representations such as line charts, pie charts, or other graphical formats. This information is designed to provide investors and operators with valuable insights for making informed investment and operational decisions. |
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.
The query results will list the TVL
Does that include dApps developed on parachains, e.g. Moonbeam dApps?
display the top 10 yield rates in the Polkadot ecosystem
Which dApps or protocols are going to be supported? Could you provide a list here?
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.
1、Does that include dApps developed on parachains, e.g. Moonbeam dApps?
Yes, for Moonbeam, this phase will primarily implement StellaSwap, which currently has a TVL (Total Value Locked) of $16 million, accounting for the majority of the share.
2、Which dApps or protocols are going to be supported? Could you provide a list here?
Yes, this phase will primarily implement: Hydration, Bifrost, Acala, and Moonbeam. The data scope is as follows:
applications/queryWeb3.md
Outdated
|
||
- data process: Initially, extract data from APIs like Subscan, Hydration, Bifrost and so on for DOT, KSM, Hydration, and Bifrost, process it into multidimensional BI data, and save it to MySQL to form the data source. | ||
|
||
- Business folw : the same as use case2 |
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.
- Business folw : the same as use case2 | |
- Business flow: the same as use case 2 |
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.
Done
applications/queryWeb3.md
Outdated
|
||
![Yield query](https://github.com/Query-Web3/product/blob/main/UI/Yield%20query.webp) | ||
|
||
Use Case 3:Vol & Txns Query |
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.
Use Case 3:Vol & Txns Query | |
Use Case 3: Vol & Txns Query |
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.
Done
applications/queryWeb3.md
Outdated
|
||
- Business Description:allows users to query snapshots of various chains within the Polkadot ecosystem (e.g., DOT, KSM, Hydration, Bifrost, etc.) on any given day. Users can search for all asset types (RWA or DeFi) and all yield types (staking, farming), including all tokens (DOT, KSM, HDT, vDOT, vKSM, BNC, etc.). The query results will list the TVL (Total Value Locked), 24-hour trading volume, and the number of transactions for each token or currency pair. Additionally, based on these query results, our platform can display the top 10 yield rates in the Polkadot ecosystem, the top 10 chains by TVL, and various visual representations such as line charts, pie charts, or other graphical formats. This information is designed to provide investors and operators with valuable insights for making informed investment and operational decisions. | ||
|
||
- Data process: Extract DEFI yield data through the APIs of various blockchains into MySQL and other databases, then process and organize it into multidimensional data suitable for BI, and store it in MySQL. |
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.
- Data process: Extract DEFI yield data through the APIs of various blockchains into MySQL and other databases, then process and organize it into multidimensional data suitable for BI, and store it in MySQL. | |
- Data process: Extract DEFI yield data through the APIs of various blockchains into MySQL and other databases, then process and organize it into multidimensional data suitable for BI, and store it in MySQL. |
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.
Done
|
||
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? |
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.
Feel free to add a short answer here as well.
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.
We hope this BI+AI data service platform can provide a one-stop service for users in the Polkadot ecosystem by aggregating and analyzing data from different sources, offering various information and tools users need, and delivering unique value in the following aspects. Currently, there are no similar projects in the Polkadot ecosystem that offer the differentiated advantages we provide compared to other AI searches.
Positioning within the Ecosystem:
1、Polkadot and Kusama ecosystem's Data Aggregation and Integration
a) Aggregate data from channels such as X, Telegram, and DC into a single platform.
b) Provide real-time investment information to help users discover opportunities within the Polkadot ecosystem.
2、Intelligent Analysis and Recommendations
a) Analyze data using AI technology to offer personalized investment advice and decision support for users.
b)Help ecosystem project operators identify issues and optimize their operational strategies in a timely manner.
3、Learning and Community Interaction
a) Provide learning resources on Polkadot technology and updates on development trends.
b) Enable users to stay informed about the latest events and financing dynamics.
4、Problem Solving and Competitive Advantage
a) Address information asymmetry and data fragmentation issues within the Polkadot ecosystem.
b) Offer an efficient information retrieval and transaction platform for the Polkadot ecosystem, enhancing user experience and satisfaction.
- What need(s) does your project meet? | ||
QueryWeb3 meets the need for timely and integrated information from the Polkadot ecosystem, addressing issues such as finding high-yield financial products, getting timely feedback on information queries, tracking major wallet movements, and identifying airdrops and NFT rewards. | ||
|
||
- How did you identify these needs? Please provide evidence in the form of (scientific) articles, forum discussions, case studies, or raw data. |
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.
Feel free to add a short answer here as well.
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 have been closely following and studying the Polkadot ecosystem for the past few years and have been an early investor in Polkadot. Based on my experience, I have encountered some pain points within the Polkadot ecosystem, which have prompted me to create a product to address these issues. Here are the details:
Pain points
1、How to find the highest yielding financial products at present? Which chains are they on?
2、If we raise an information question in the Polkadot ecosystem, can we get timely and effective feedback?
3、What are the major movements in the Polkadot ecosystem wallets? What have they done?
4、What activities are there in each of the Polkadot and kusama ecosystem projects?
5、Can we still send some NFT benefits to target users?
6、What airdrops are there in the Polkadot ecosystem projects? Which airdrops can I participate in?
7、Based on the Polkadot and Kusama ecosystem, which projects are in the top 10 for on-chain transaction volume and transaction amount on a weekly, monthly, quarterly, semi-annual, and annual basis? Additionally, what are their year-over-year and month-over-month data?
Solution
1、Query the yield rates of financial products in various projects in the Polkadot ecosystem based on keyword conditions.
2、Analyze the data of any address in the Polkadot ecosystem including wallet data analysis 、 data dashboard and so on.
3、The abnormal situation of large whale transactions in the Polkadot ecosystem recently
4、Ranking of important financings in the Polkadot ecosystem.
5、NFT and peripheral merchandise mall
6、Customized airdrop solution for many polkadot projects in future.
7、AI powered information service.
8、Provide equivalent data for on-chain transaction volume and transaction amount on a weekly, monthly, quarterly, semi-annual, and annual basis, as well as year-over-year and month-over-month growth data.
Answersing 1) Specific APIs and Endpoints: Due to the workload considerations and the $30,000 budget limit, we will initially support data extraction from these specific chains to complete use case 2. In subsequent proposals, we will improve and extract data from other chains. If possible, could we increase the budget by several tens of thousands of dollars in this proposal? This would allow us to include data extraction from other chains in the Polkadot ecosystem and also complete use case 3. I believe this approach would be better. So, could the W3F team please consider supporting my suggestion? |
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.
@lechangxu thanks for your reply.
Due to the workload considerations and the $30,000 budget limit, we will initially support data extraction from these specific chains to complete use case 2.
In general I like the way you're choosing a lean approach by integrating a limited number of APIs initially.
However, would it be possible to specify that accordingly in the proposal? Please add a bit more details, on which APIs specific to these chains you're planning to support.
In subsequent proposals, we will improve and extract data from other chains. If possible, could we increase the budget by several tens of thousands of dollars in this proposal? This would allow us to include data extraction from other chains in the Polkadot ecosystem and also complete use case
It's up to you to request the amount you deem appropriate. But usually the committee is not keen of supporting level 3 grants for applicants that we haven't supported in the past. That said, you haven't answered the questions I've asked in my previous comment in 2) and 3).
Please wait a few days, our team is currently in discussions. We will respond after we have communicated the relevant issues. Thank you. |
3) Handling Other Data Categories |
|
Since you asked for private discussion, I will lock the conversation here for the moment. Let's continue this on Matrix. |
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.
@lechangxu sorry for the delay here and thanks for answering the questions. Happy to approve as well.
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.
Hi @lechangxu hopefully you're okay with accepting 50% of payment in vested DOT? If so feel free to accept my suggestion.
Additionally, we require all grantees to do KYC. Can you please use this verification link to complete it? Thanks and let me know if you run into any issues.
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.
Thanks for the changes, I'll approve now and we will merge it once KYC has passed.
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.
@lechangxu thanks for your answers. Happy to approve as well.
Project Abstract
QueryWeb3 aims to address the fragmentation of information and data across various projects within the Polkadot and Kusama ecosystem. By aggregating data, we improve information retrieval and transaction efficiency, enhance user experience, and increase user satisfaction.
Grant level
Application Checklist
project_name.md
).@lechangxu :matrix.org
(change the homeserver if you use a different one)