Kudos of this proposal, I believe it is the right way to enable the ecosystem-wide potential of XCM.
Couple of considerations:
- Should the
execute()approach replace all the ad-hoc extrinsics in pallet_XCM or xTokens pallet in the long term? In terms of runtime maintenance/cleanliness this makes sense, but it may be a considerable pain for APIs and wallets supporting the current interfaces. - Is this proposal limited to transfers for any specific reason? I think more complex interactions (like remote locking) can flow naturally from such a tool.
- is the role of the upper layer (asset-transfer-library) limited to provide the context (ecosystem stateful)? How would it interact with the builder? Would it mainly assign values to the context variables in the examples?
That being said, looking forward to supporting this proposal and collaborating in the development of the builder tool and the asset-transfer-library.