Clients get BadProof after runtime upgrade
Open
bug
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.