XCM: What lies beyond the bridge?
Hosted by Matt and David (me and @dawufi) from OAK Network
How can we expand XCM adoption and establish Polkadot as the leader in cross-chain messaging?
Remote execution accomplishes both by enabling parachains to leverage extrinsics and contracts from foreign chains using XCM. Let’s discuss the current state of remote execution and share solutions for combining services from multiple parachains into a single Polkadot experience.
Topics proposed for this session:
Use cases - introduction to remote execution and examples of features that leverage services from multiple parachains.
Note: for the sake of advancing beyond this point, I’d propose we limit discussion to 2-3 cross-chain use cases that are relatively time-insensitive.
Security - OAK and partner (to be confirmed) will present and request feedback on our current solution to allow user-permitted remote execution using XCM, the proxy-pallet, and descendOrigin.
User experience - an overview of two scenarios to prompt discussion:
- An application (and its users) primarily interacts with a single network and includes XCM instructions to that chain when it seeks to leverage service(s) from another chain (assuming open HRMP channel, etc).
- An application (and its users) switches networks to sign each transaction on its native chain and includes XCM instructions primarily for transferring asset(s) between chains.
Note: this is only feasible for some use cases and introduces additional complexity to sufficient funding for fees.
- Fees - Open questions regarding cross-chain transaction fees:
- How can we ensure that the fees are in the right account(s)?
- What currencies would users already have or expect to pay using?
- How can we facilitate liquidity between what users have and what parachains want (their native or a stable)?