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
Bug on including multisig transactions into the Polkadot blockchain v0.9.11 and v0.9.12 #923
Comments
bkchr
pushed a commit
that referenced
this issue
Apr 10, 2024
* relay at least one header for every session * Update relays/bin-substrate/src/on_demand_headers.rs Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com> Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
I have been testing v0.9.11 and v0.9.12 and faced with a problem on sending
multisig.approveAsMulti
.Multisig address:
14LcP9A4o4zxBoB6KiS1cMXpkwhNBqn1MgwPJxugUgjgCwrm
Signers
Sometimes on sending 2
multisig.approveAsMulti
transactions:1.
The problem that these transactions cannot be found in the blockchain even after 30 blocks were generated.
In v0.9.10 there was no such problem.
Thank you!
The text was updated successfully, but these errors were encountered: