You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we've seen with pallet-xcm and xtokens, it's hard for onchain implementations to keep up with ecosystem cross-chain usage needs.
We should switch to 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.
These programs can then be simply run on-chain using pallet_xcm::execute() or pallet_xcm::send().
Description
As we've seen with
pallet-xcm
andxtokens
, it's hard for onchain implementations to keep up with ecosystem cross-chain usage needs.We should switch to 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.
These programs can then be simply run on-chain using
pallet_xcm::execute()
orpallet_xcm::send()
.Progress
The text was updated successfully, but these errors were encountered: