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.

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

[FRAME] Currency::transfer() can create locks if used incorrectly #3332

Open
Gioyik opened this issue Feb 15, 2024 · 1 comment
Open

[FRAME] Currency::transfer() can create locks if used incorrectly #3332

Gioyik opened this issue Feb 15, 2024 · 1 comment
Labels
I3-annoyance The node behaves within expectations, however this “expected behaviour” itself is at issue.

Comments

@Gioyik
Copy link

Gioyik commented Feb 15, 2024

currently if you try to transfer more than what you have without checking for balance, the result will be the account having a locked amount. You can lock more than you have, something that is not wrong per se but it would be good to document the behavior as someone could create locks on accounts unintentionally and get them stuck until more tokens are transfer, or have a pallet to blindly trust the locked amount.

it would be good during the documentation process to double check if there's any place today where the locked amount is being counted as voting power or as an unreal advantage, I am not aware of that being the case, but better double check to be safe.

@github-actions github-actions bot added the I10-unconfirmed Issue might be valid, but it's not yet known. label Feb 15, 2024
@bkchr bkchr added I3-annoyance The node behaves within expectations, however this “expected behaviour” itself is at issue. and removed I10-unconfirmed Issue might be valid, but it's not yet known. labels Feb 15, 2024
@kianenigma
Copy link
Contributor

kianenigma commented Feb 16, 2024

Something that can be addressed as a part of #2683 / paritytech/polkadot-sdk-docs#49 or similar PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I3-annoyance The node behaves within expectations, however this “expected behaviour” itself is at issue.
Projects
Status: Backlog
Development

No branches or pull requests

3 participants