# XCM Documentation Suggestions **URL:** \ **Category:** Ecosystem\ **Tags:** xcm\ **Created:** [May 10, 2023, 1:41pm UTC](https://forum.polkadot.network/t/xcm-documentation-suggestions/2816 "2023-05-10T13:41:51Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![vstam1](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/vstam1/32/1690_2.png) [@vstam1](https://forum.polkadot.network/u/vstam1)\ **Post date:** [May 10, 2023, 1:41pm UTC](https://forum.polkadot.network/t/xcm-documentation-suggestions/2816/1 "2023-05-10T13:41:51Z")
Hello everyone, Parity’s XCM team is working hard on writing documentation on XCM. As the XCM team, we would like to know from the ecosystem what they want to see covered. The following things are already on the schedule: - XCM - XCVM - MultiLocation - MultiAsset - Fees and Weight - All XCM instructions with examples. - The xcm-executor configuration - Testing XCM (xcm-simulator vs xcm-emulator vs Zombienet) - Common use cases Please let us know if we missed anything and which common use you would like to see. Thank you in advance! ---
**Author:** ![sourabhniyogi](https://avatars.discourse-cdn.com/v4/letter/s/35a633/32.png) [@sourabhniyogi](https://forum.polkadot.network/u/sourabhniyogi)\ **Post date:** [May 10, 2023, 9:10pm UTC](https://forum.polkadot.network/t/xcm-documentation-suggestions/2816/2 "2023-05-10T21:10:42Z")
- Keyless derived accounts - Remote Execution best practices using the above ---
**Author:** ![xlc](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/xlc/32/690_2.png) [@xlc](https://forum.polkadot.network/u/xlc)\ **Post date:** [May 10, 2023, 10:27pm UTC](https://forum.polkadot.network/t/xcm-documentation-suggestions/2816/3 "2023-05-10T22:27:29Z")
How to calculate the fees so UI can display them. ---
**Author:** ![rich](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/rich/32/159_2.png) [@rich](https://forum.polkadot.network/u/rich)\ **Post date:** [May 11, 2023, 8:17am UTC](https://forum.polkadot.network/t/xcm-documentation-suggestions/2816/4 "2023-05-11T08:17:25Z")
I find most helpful part of documentation is when it is supported by examples that give context for the capabilities and parameters of the technology behind documented. For example, I’ve been trying to find the right people inside (and outside of parity) to help our developers figure an innovative new model for using XCM related to funding parachains such as Kabocha - a purely on-chain developed and funded project (via Edgeware) with no lead team / legal entity. Imbue’s parachain has received a c.£250k grant from the treasury, but there is no direct upside for the treasury in this deal, nor voice in the network they are helping bootstrap. XCM can address this. The high level example: - Kabocha requests funding from Kusama treasury and pledges some KAB which is transferred to Statemine treasury account. - This KAB is currently illiquid, but grants the Kusama treasury the proportional right to future dividends in the form of fees from Kabocha. - The onchain terms within an NFT held in the treasury, and represents a new kind of collateral (with Kusama’s latest NFT upgrade this is now possible). - Kusama also now has the ability to leverage its voice in Kabocha governance via XCM, with the Kusama collective being representing as a collective (proxy) on the Kabocha chain. > [@An XCM3 experiment - Kusama treasury account taking stake in the Kabocha parachain](https://forum.polkadot.network/t/an-xcm3-experiment-kusama-treasury-account-taking-stake-in-the-kabocha-parachain/2127): > > There have been discussions for around a year about alternative approaches for incubating parachains, whilst also making use of relay treasuries and better aligning long term interests of voters and proposers. This in [discussion post for funding grass-roots teams](https://polkadot.polkassembly.io/post/1596) aims to create guidelines, but its off-chain structure means it will always be limited since funding will remain subjective and therefore prone to friction - per [this comment](https://polkadot.polkassembly.io/post/1596#db493114-a937-4394-8a5a-7233401a4b8b). we probably should have funding policy and programs that… ---
**Author:** ![AlexD10S](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/alexd10s/32/2921_2.png) [@AlexD10S](https://forum.polkadot.network/u/AlexD10S)\ **Post date:** [May 11, 2023, 1:28pm UTC](https://forum.polkadot.network/t/xcm-documentation-suggestions/2816/5 "2023-05-11T13:28:12Z")
Strongly agreed with the previous message from Rich about the importance of examples in the documentation. Also looking into the questions on StackExchange in the last year the number of questions related of XCM has increased and I have notice that it has gone from more theoretical to practical questions. So I’d like to suggest to have a **troubleshooting section** with some of the most common errors we can see there, for example: [`UnknownClaim` Error The ClaimAsset](https://substrate.stackexchange.com/questions/6796/how-to-use-claimassets-after-assets-got-trapped), [Untrusted Teleport Location](https://substrate.stackexchange.com/questions/6776/i-want-to-enable-teleport-asset-functionality-in-xcm-between-two-parachains-how) …