Move Development Genesis Config to Runtime #2149
Assignees
Comments
enddynayn
added a commit
that referenced
this issue
Sep 5, 2024
Move the Development Genesis Config to the Runtime as a step towards decoupling the client and runtime dependencies. issue-2149 issue-2142 #2149
enddynayn
added a commit
that referenced
this issue
Sep 5, 2024
Move Development Genesis Config to the Runtime to
support decoupling of client and runtime dependencies.
When running `chain-spec-builder`, the following command:
```
chain-spec-builder list-presets –runtime-wasm-path ./target/debug/wbuild/frequency-runtime/frequency_runtime.wasm
```
outputs:
```
{“presets”:[“development”]}
```
issue-2149
issue-2142
#2149
enddynayn
added a commit
that referenced
this issue
Sep 5, 2024
Move Development Genesis Config to the Runtime to
support decoupling of client and runtime dependencies.
When running `chain-spec-builder`, the following command:
```
chain-spec-builder list-presets –runtime-wasm-path ./target/debug/wbuild/frequency-runtime/frequency_runtime.wasm
```
outputs:
```
{“presets”:[“development”]}
```
Additionally, when running:
```
chain-spec-builder display-preset --runtime-wasm-path ./target/debug/wbuild/frequency-runtime/frequency_runtime.wasm --preset-name development
```
it outputs the development genesis config:
```
{"aura":{"authorities":[]},"auraExt":{},"balances":{ ...} ... }
issue-2149
issue-2142
#2149
enddynayn
added a commit
that referenced
this issue
Oct 1, 2024
Move Development Genesis Config to the Runtime to
support decoupling of client and runtime dependencies.
When running `chain-spec-builder`, the following command:
```
chain-spec-builder list-presets –-runtime-wasm-path ./target/debug/wbuild/frequency-runtime/frequency_runtime.wasm
```
**Outputs:**
With feature flags _"frequency-no-relay", "frequency-local"_ enabled:
```
{“presets”:[“development”, "frequency-local", "frequency"]}
```
Additionally, when running:
```
chain-spec-builder display-preset --runtime-wasm-path ./target/debug/wbuild/frequency-runtime/frequency_runtime.wasm --preset-name development
```
it outputs the development genesis config:
```
{"aura":{"authorities":[]},"auraExt":{},"balances":{ ...} ... }
```
With feature flags _"frequency"_ only, mainnet presets show up:
```
{“presets”:["frequency"]}
```
Additionally, when running:
```
chain-spec-builder display-preset --runtime-wasm-path ./target/debug/wbuild/frequency-runtime/frequency_runtime.wasm --preset-name frequency
```
it outputs the frequency genesis config:
```
{"aura":{"authorities":[]},"auraExt":{},"balances":{ ...} ... }
```
#2149
#2142
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Move Development Genesis Config to Runtime
Acceptance Criteria
chain-spec-builder, the following command:outputs:
it outputs the development genesis config:
Subtask of Parent Issue
#2142
The text was updated successfully, but these errors were encountered: