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
In order to use XCM::Transact, we need to know how to encode the call on destination chain. The best way should be just import the Call enum from runtime. But we cannot do it because last time we tried, it tries to import the whole Rococo runtime into our parachain runtime, which obviously wouldn't work.
We should have some way to allow others to import some generated types from runtime, without import the whole thing.
Not exactly sure how it can be implemented though, all the generic makes thing harder. One potential solution is reconstruct the enum from metadata and expose them.
The text was updated successfully, but these errors were encountered:
For something very similar, we used subxt-codegen library which has ability to generate runtime Call metadata at least (I am not sure about Storage), generated file looks like this.
E.g. you can generate metadata from live running node or from downloaded wasm file (maybe there are also other options), we integrated just these two options here.
Previous issue: paritytech/substrate#8158
In order to use XCM::Transact, we need to know how to encode the call on destination chain. The best way should be just import the Call enum from runtime. But we cannot do it because last time we tried, it tries to import the whole Rococo runtime into our parachain runtime, which obviously wouldn't work.
We should have some way to allow others to import some generated types from runtime, without import the whole thing.
Not exactly sure how it can be implemented though, all the generic makes thing harder. One potential solution is reconstruct the enum from metadata and expose them.
The text was updated successfully, but these errors were encountered: