Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Clients get BadProof after runtime upgrade #108

Open
jordy25519 opened this issue May 11, 2020 · 0 comments
Open

Clients get BadProof after runtime upgrade #108

jordy25519 opened this issue May 11, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@jordy25519
Copy link
Contributor

jordy25519 commented May 11, 2020 •
edited
Loading

After a runtime upgrade clients are still sending transactions with the old runtime version and getting:

submitAndWatchExtrinsic(extrinsic: Extrinsic): ExtrinsicStatus:: 1010: Invalid Transaction: BadProof

A restart will fix it.

We could provide a better UX here and allow the API session to re-query this info automatically as some kind of opt-in.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jordy25519