-
Notifications
You must be signed in to change notification settings - Fork 646
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rpc: Enable ChainSpec for polkadot-parachain #5205
Changes from 3 commits
2675d44
cc90001
236ee3a
2469101
cf14833
6c11c15
f705a93
86177bd
70f03e6
6a00f91
1cc7f2f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
title: Enable ChainSpec API for polkadot-parachain | ||
|
||
doc: | ||
- audience: | ||
- Runtime Dev | ||
- Node Dev | ||
description: | | ||
Enables the `chainSpec_v1` rpc-v2 API for polkadot-parachains. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would like to re-phrase this as:
|
||
This RPC is needed to provide extra information about the specification of the chain. | ||
At the same time, this paves the way for implementing in the future a `chainSpec_v1_getSpec` | ||
method that can extract the chainSpec of any chain (including parachains) for the use with lightclients. | ||
For more info about the `chainSpec`, please see the specification: https://github.com/paritytech/json-rpc-interface-spec/blob/main/src/api/chainSpec.md. | ||
|
||
crates: | ||
- name: polkadot-parachain-bin | ||
bump: minor |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is the type needed now in contrast to before?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I've hit the autocomplete by mistake :D No longer needed since I was able to obtain the same by moving the initialization to the substrate builder