System chains should implement full XCM spec.
Conservative XCM filters should be removed and XCM generic power exposed.
System chains should allow secure execution of arbitrary XCMs, and allow sending arbitrary XCMs to other chains in a secure manner.
As we've seen with pallet-xcm and xtokens, it's hard for onchain implementations to keep up with ecosystem cross-chain usage needs.
I envision leaner XCM pallets and richer TS/JS/Rust libraries and tools that build/expose many more flavors of XCM programs.
Through allowing on-chain execution of arbitrary XCM programs, we can build these useful XCM programs offchain, vend them as libraries and they can be used on any chain.
Developing XCM programs off-chain allows orders of magnitude improvements on: developers who could contribute, number of helpful programs provided, iteration speed, etc.
System chains should implement full XCM spec.
Conservative XCM filters should be removed and XCM generic power exposed.
System chains should allow secure execution of arbitrary XCMs, and allow sending arbitrary XCMs to other chains in a secure manner.
As we've seen with
pallet-xcmandxtokens, it's hard for onchain implementations to keep up with ecosystem cross-chain usage needs.I envision leaner XCM pallets and richer TS/JS/Rust libraries and tools that build/expose many more flavors of XCM programs.
Through allowing on-chain execution of arbitrary XCM programs, we can build these useful XCM programs offchain, vend them as libraries and they can be used on any chain.
Developing XCM programs off-chain allows orders of magnitude improvements on: developers who could contribute, number of helpful programs provided, iteration speed, etc.