# XCM as a Standard for Reading And Interacting with Parachains

**URL:** <https://forum.polkadot.network/t/xcm-as-a-standard-for-reading-and-interacting-with-parachains/266>\
**Category:** Tech Talk\
**Tags:** xcm\
**Created:** [September 1, 2022, 7:23pm UTC](https://forum.polkadot.network/t/xcm-as-a-standard-for-reading-and-interacting-with-parachains/266 "2022-09-01T19:23:04Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![kianenigma](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/kianenigma/32/6153_2.png) [@kianenigma](https://forum.polkadot.network/u/kianenigma)\
**Post date:** [February 21, 2023, 12:34pm UTC](https://forum.polkadot.network/t/xcm-as-a-standard-for-reading-and-interacting-with-parachains/266/5 "2023-02-21T12:34:56Z")

</div>

I brought this up again in a PR that I found to be solving something similar:

> <https://github.com/paritytech/substrate/pull/13352#pullrequestreview-1307305295>
>
> This method solves the problem of fetching the account's asset balances, now ins…tead of sending 100+ RPC requests it would be possible to send just one.
> 
> Cumulus Companion: https://github.com/paritytech/cumulus/pull/2180

> Currently, an account can have “value bearing assets” in balances/assets pallet, in a DEX pallet, in some liquid staking pool pallet, in a lending platform. A wallet in our ecosystem has no meaningful way to scrape all of this information as it stands now, unless if they go on and study each parachain/platform one by one.  
> The XCM-centric approach would solve all of this in one go, and moves the responsibility of implementing this API to each individual chain, which is where it should logically reside.

---

_[View the full topic](https://forum.polkadot.network/t/xcm-as-a-standard-for-reading-and-interacting-with-parachains/266)._
