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):
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 is a new technology that will make it easier to use XCM. It will allow people to do things like check their account balance, see if a certain feature is available, and more. XCQ works by using extensions, which can be added later on without changing the core protocol. This will greatly enhance the user experience of XCM bridge UIs, wallets, and universal dApps in the ecosystem. The full proposal can be found at the link provided.
Firstly, I commend the Acala team for consistently delivering valuable tools that have greatly improved the developer experience within the Polkadot ecosystem. The deliverables, such as the XCQ protocol, extensions, and comprehensive documentation, promise to provide robust tools and references. This proposal addresses a critical need in our multi-chain environment. The lack of a standardized method for querying information across different chains creates unnecessary guesswork and operational inefficiencies.
The use cases you’ve outlined—from querying balances and asset prices to improving cross-chain treasury management and enhancing wallet functionality—highlight the vast potential of XCQ. This tool will streamline existing processes and open up new possibilities for cross-chain interactions and integrations. Including a 10% buffer to account for potential volatility is prudent, ensuring the project stays on track without further financial hiccups.
Given the extensive groundwork, including the previous discussions and the detailed milestones, I’m confident that the Acala team is well-equipped to bring XCQ to fruition. The commitment to transparency and progress updates is also reassuring. I’m eager to see the positive impact XCQ will have and fully support this.
Cheers, Jimmy