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
I can see you have some XCM related work to handle relaychain encoding and we have the exact requirement at Acala. I image other parachains will have similar requirements. Should we collaborate to build some shared library in ORML?
There will probably more demand for features like this so it is definitely worthwhile to add support for this to ORML.
I think an ORML solution should provide a way to get bindings for a specific chain (like relaychain) the bigger challenge is then to make this work for multiple chains as we tried with PINT, since call encoding is chain specific.
I'm also not sure how this would be affected by future metadata changes or something like https://github.com/ascjones/chameleon
I also experimented with generating generic Call enums from the T:Config bound types the substrate macros generate: https://github.com/mattsse/substrate-pallet-call-extract
The metadata change won't be helping in this case. We have no way to fetch & parse the latest metadata from dest runtime. polkadot-fellows/xcm-format#22 is the long term solution.
I can see you have some XCM related work to handle relaychain encoding and we have the exact requirement at Acala. I image other parachains will have similar requirements. Should we collaborate to build some shared library in ORML?
For example, those two module does the same job in a slightly different way.
https://github.com/ChainSafe/PINT/tree/main/primitives/xcm-calls
https://github.com/AcalaNetwork/Acala/blob/feature/homa-lite-redeem/modules/relaychain/src/lib.rs
The text was updated successfully, but these errors were encountered: