-
Notifications
You must be signed in to change notification settings - Fork 47
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
chore: polkadot-0.9.43 #541
Conversation
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.
A couple of minor questions, before I can approve the PR!
…node into chore/polkadot-0.9.43
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.
LGTM
Was the http based RPC port removed? Is there no RPC over HTTP anymore? only websockets?
@weichweich the RPC server supports websocket and HTTP on the same socket. The HTTP was kept for backwards compatibility so yes in the future there should be only WS. Source |
fixes KILTProtocol/ticket#513
RemoveInsecureRandomnessPallet
even if it is no longer useful 👻