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
{{ message }}
This repository has been archived by the owner on Jul 29, 2022. It is now read-only.
By default, we'll bundle the Kusama wasm blob inside the extension.
Step 1. Users should be able to upload their own chainSpec via the UI.
start_client takes a chain_spec arg, we should make that arg take a JSON chainSpec. We'll just run in this case the kusama wasm blob with the inputted chainSpec.
Step 2. Users should be able to upload their own wasm blob via the UI.
Sometimes the chainSpec is not enough (e.g. when the custom chain implements custom BlockNumber type, Header etc, which happens at compile time), so the user needs to have a possibility to upload a wasm blob too, and let the extension run that custom wasm blob.
By default, we'll bundle the Kusama wasm blob inside the extension.
start_client
takes achain_spec
arg, we should make that arg take a JSON chainSpec. We'll just run in this case the kusama wasm blob with the inputted chainSpec.Sometimes the chainSpec is not enough (e.g. when the custom chain implements custom BlockNumber type, Header etc, which happens at compile time), so the user needs to have a possibility to upload a wasm blob too, and let the extension run that custom wasm blob.
reported by @expenses
The text was updated successfully, but these errors were encountered: