-
Notifications
You must be signed in to change notification settings - Fork 648
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
check max_supply before borrowing MPAs #1498
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about existing MPAs and their max_supply?
I think we need hardfork protection on the new FC_ASSERT and some logic to adapt max_supply of existing bitAssets at hardfork time, if necessary.
How do you see this working? My thought: At the hardfork, flip through all bitAssets, if current supply is greater than max supply, adjust max supply to equal current supply. What if that number is greater than GRAPHENE_MAX_SHARE_SUPPLY? |
Shouldn't happen due to softfork protection. If it does happen set max_supply to GRAPHENE_MAX_SHARE_SUPPLY. |
Test still failing because after |
Gee wiz. It passed for me. The problem must be on your end! :-D Fixed reference, tested in Ubuntu 18.10 in both Debug and Release mode. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
Fixes #1465