-
Notifications
You must be signed in to change notification settings - Fork 365
balances.LiquidityRestrictions on addProxy #3242
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
Comments
Sik reminded me that it's a bug where you need a larger than the self-bond balance. Not a big deal for me cause I have a small self-bond, but more of an issue for collators with larger bonds. |
Thanks for the report 👍 . We will have a look at it and report back once we have identifier the problem. |
Hi @ioannist, To give an update. We opened a PR upstream, if this is confirmed to be unexpected behaviour as we believe, a fix will be included in the next runtime release ( |
Another related issue, this is part of the migration from |
Hey team, stakebaby here..
I recently tried to addProxy (authormapping) on my collator and got this error: balances.LiquidityRestrictions
https://moonbeam.subscan.io/extrinsic/10202196-4
I then tried doing it via the precompile and it also reverted:
https://moonbeam.subscan.io/tx/0x804c0e23ae973ab75f67dd17778a135ac3958e1e4d69694049fe3e2f29afa8a4
this smells like a bug that affects collators only, or accounts with a self-bond
The text was updated successfully, but these errors were encountered: