Following are the recent discussions of XCQ
[XCM as a Standard for Reading And Interacting with Parachains - #19 by gavofyork,](https://forum.polkadot.network/t/xcm-as-a-standard-for-reading-and-interacting-with-parachains/266/19) and [Polkadot forum discussion of XCQ](https://forum.polkadot.network/t/cross-consensus-query-language-xcq/7583), 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](https://docs.google.com/document/d/11c0-t0S5WbVLpoonh24OgadcK4X35_I1Q0HKpxKxLBk/edit?usp=sharing)):

- 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](https://docs.google.com/document/d/11c0-t0S5WbVLpoonh24OgadcK4X35_I1Q0HKpxKxLBk/edit?usp=sharing)

- **Problem Statement:** Developing Cross-consensus Query Language (XCQ) to enhance utilities lacking with XCM alone, seeking treasury funding support.
- **Significance:** XCQ enables querying balances, fees, features, staking rewards, and market information across parachains and relaychains, improving user experience and expanding dApp functionalities.
- **Proposed Solution:** XCQ employs an extension-based design to add features without altering the core protocol, enhancing XCM bridge UIs, wallets, and universal dApps.
- **Expected Outcomes:** Improved user experience, increased functionality, and ecosystem growth through XCQ's queriable information and potential extensions.

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

No Active Proposals