Embed metadata into the wasm binary #2745
Comments
|
This may or maynot be blocked by #1139 |
|
Can be done as part of #291, because there we will already need to fetch the metadata from the built runtime. |
|
Agree! That said, I would still leave this one opened until addressed. |
pepyakin
added a commit
to thrumdev/blobs
that referenced
this issue
Dec 21, 2023
This commit adds a new subcommand to the CLI that exports metadata from the compiled-in runtime, similar to the existing subcommands like `export-genesis-state` and `export-genesis-wasm`. A typical usage would be ```bash sugondat-node export-genesis-metadata --raw binary_metadata.scale subxt codegen --file binary_metadata.scale | \ rustfmt --edition=2021 --emit=stdout > src/metadata.rs ``` Ideally, it would be solved by [paritytech/polkadot-sdk#2745] and thus we could just take the wasm blob (either exported by `export-genesis-wasm`) and just get it from there via simple of the shelf tools. Until then, we will have this command. [paritytech/polkadot-sdk#2745]: paritytech/polkadot-sdk#2745
pepyakin
added a commit
to thrumdev/blobs
that referenced
this issue
Dec 21, 2023
This commit adds a new subcommand to the CLI that exports metadata from the compiled-in runtime, similar to the existing subcommands like `export-genesis-state` and `export-genesis-wasm`. A typical usage would be ```bash sugondat-node export-genesis-metadata --raw binary_metadata.scale subxt codegen --file binary_metadata.scale | \ rustfmt --edition=2021 --emit=stdout > src/metadata.rs ``` Ideally, it would be solved by [paritytech/polkadot-sdk#2745] and thus we could just take the wasm blob (either exported by `export-genesis-wasm`) and just get it from there via simple of the shelf tools. Until then, we will have this command. [paritytech/polkadot-sdk#2745]: paritytech/polkadot-sdk#2745
rphmeier
pushed a commit
to thrumdev/blobs
that referenced
this issue
Dec 22, 2023
This commit adds a new subcommand to the CLI that exports metadata from the compiled-in runtime, similar to the existing subcommands like `export-genesis-state` and `export-genesis-wasm`. A typical usage would be ```bash sugondat-node export-genesis-metadata --raw binary_metadata.scale subxt codegen --file binary_metadata.scale | \ rustfmt --edition=2021 --emit=stdout > src/metadata.rs ``` Ideally, it would be solved by [paritytech/polkadot-sdk#2745] and thus we could just take the wasm blob (either exported by `export-genesis-wasm`) and just get it from there via simple of the shelf tools. Until then, we will have this command. [paritytech/polkadot-sdk#2745]: paritytech/polkadot-sdk#2745
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Note
This is a copy of paritytech/substrate#8870 that was not copied over, but I still believe is worthwhile to persue.
paritytech/substrate#7327 and paritytech/substrate#8688 were about embedding the version information into the wasm binary. We can leverage the same technique for the metadata.
That would enable a simpler way to get the metadata. The user will need to only obtain the wasm binary and then fetch a specific section. No instantiation of the wasm runtime is required.
The text was updated successfully, but these errors were encountered: