Proposal: Funding for Design and Development of XCQ, the Cross-Consensus Query Language

Following are the recent discussions of XCQ
XCM as a Standard for Reading And Interacting with Parachains - #19 by gavofyork, and Polkadot forum discussion of XCQ, with all the positive comments, we would like to move onto the next phase, to have treasury's funding support in making this happen.

Cross-consensus Query Language or XCQ, is the missing piece to enable a lot of utilities that currently lacks with XCM alone.

Example use cases (more in our full proposal here):

Query balances of an account
Query the weight and fee of a particular XCM
Query if a certain feature / pallet is available
Implement decentralized staking pool from a parachain
Use XCQ to query staking rewards from relaychain
Use XCQ to query weights and fees for related operations
Automatically purchase coretime from broker chain
Use XCQ to query market information
Use XCQ to query weights and fees for related operations

XCQ employs a extension based design, above features are developed as extensions and new features can be added later on as extensions too, all without changing to the core XCQ protocol.

With these XCQ queriable informaiton, it will greatly enhance UX of XCM bridge UIs, wallets, universal dApps in the ecosystem, and more as list of extensions grows.

We would like to open this discussion for other use cases (i.e. extensions) you would like to see, if it has enough support we will add them to the list too.

Link to full proposal https://docs.google.com/document/d/11c0-t0S5WbVLpoonh24OgadcK4X35_I1Q0HKpxKxLBk/edit?usp=sharing

XCQ stands for Cross-consensus Query Language, which helps improve how different blockchain systems work together.
It is meant to add more features and utilities that XCM alone cannot provide.
People can use XCQ to find out things like account balances, fees, and available features.
It can help make staking pools and query rewards from the blockchain.
XCQ allows the addition of new features as extensions without changing its core design.
The goal is to make the experience better for users of wallets and apps in the ecosystem.
The community is encouraged to suggest new uses or extensions for XCQ.

Source

Cross-consensus Query Language or XCQ, is the missing piece to enable a lot of utilities that currently lacks with XCM alone.

Example use cases (more in our full proposal here):

Query balances of an account
Query the weight and fee of a particular XCM
Query if a certain feature / pallet is available
Implement decentralized staking pool from a parachain
Use XCQ to query staking rewards from relaychain
Use XCQ to query weights and fees for related operations
Automatically purchase coretime from broker chain
Use XCQ to query market information
Use XCQ to query weights and fees for related operations

XCQ employs a extension based design, above features are developed as extensions and new features can be added later on as extensions too, all without changing to the core XCQ protocol.

With these XCQ queriable informaiton, it will greatly enhance UX of XCM bridge UIs, wallets, universal dApps in the ecosystem, and more as list of extensions grows.

We would like to open this discussion for other use cases (i.e. extensions) you would like to see, if it has enough support we will add them to the list too.

Link to full proposal https://docs.google.com/document/d/11c0-t0S5WbVLpoonh24OgadcK4X35_I1Q0HKpxKxLBk/edit?usp=sharing