Open Runtime Module Library, or ORML, originally created by Acala's co-founders in late 2019. It is a collection of modules that Acala team created to solve issues that we encountered, to produce features that we wish existed, at the same time making it not specific to our chain but generic, so we can share them with our fellow developers in the whole Polkadot/Kusama community and help in some way.

Fast forward to late 2022, ORML is widely used by many teams in the ecosystem, and is receiving contributions from different teams. Acala remains the biggest contributor in development and maintenance of ORML.

This proposal (link to doc [here](https://docs.google.com/document/d/1BGvDnc_fHgowSUXE83hhPGsDPBF7cHWMbA4a14k_AyM)) is seeking payment to cover development and maintenance of the widely used Open Runtime Module Library between Jan 2022 and Oct 2022.

Community members, please kindly review the proposal and ask questions you may have, we are happy to address questions before moving onto next step. You are also welcome to share how ORML is useful for your project(s). :)

Proposal: ORML development and maintenance

Chopsticks is a testing client that enables 1-step creation of a mainnet replica of substrate-based network, for safely testing action and reviewing outcome. Projects can test new runtime, proposal actions, XCM, different configurations, dry run transactions, etc, to discover and eliminate issues before they arrive to live network.

With Chopsticks, we are able to provide the tool needed to the community, and prevent issues that we see in the ecosystem. 

This submission is to propose a retroactive payment by Polkadot Treasury to cover development costs incurred.

You can find the details of the proposal [here](https://docs.google.com/document/d/1WnOxnZbQqsaWRh8X6R9oHbOoMonzE0U0_i4SFTS-Cv8/edit?usp=sharing).

Thank you for reading and questions are welcome. :)

Acala Proposal: Retroactive Funding for Chopsticks Development

This proposal (link to doc [here](https://docs.google.com/document/d/1ENh6IHUbcFjNR6Js0I7VzWV5xFQeepmqS4Eipz7gVio/edit?usp=sharing)) is seeking payment to cover development and maintenance of the widely used Open Runtime Module Library between Nov 2022 and Apr 2023.

Community members, please kindly review the proposal and ask questions you may have, we are happy to address questions before moving onto next step. 

**Context**: Open Runtime Module Library, or ORML, originally created by Acala's co-founders in late 2019. It is a collection of modules that Acala team created to solve issues that we encountered, to produce features that we wish existed, at the same time making it not specific to our chain but generic, so we can share them with our fellow developers in the whole Polkadot/Kusama community and help in some way.

Retroactive funding for ORML maintenance Nov 22 to Apr 23

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)