-
Notifications
You must be signed in to change notification settings - Fork 68
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
Add WrappedToken.sol #1095
base: feature/1.5.0.0-interflux
Are you sure you want to change the base?
Add WrappedToken.sol #1095
Conversation
…ms-fees-ort Add activation height for multisig fee sorting
// When the tokens are burnt we need to know where to credit the equivalent value on the Stratis chain. | ||
// Currently it is only possible to assign a single address here, so if multiple recipients are required | ||
// the burner will have to wait until each burn is processed before proceeding with the next. | ||
withdrawalAddresses[msg.sender] = address; |
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.
maybe add additional method with onlyOwner modifier that removes value withdrawalAddresses[address].
And in burn method if address is set- revert.
That will prevent users sending requests with multiple recepients in a row before prev requests are processed and subsequently loosing money
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.
@noescape00 , I've made the following change:
string memory key = string(abi.encodePacked(msg.sender, " ", burnId));
withdrawalAddresses[key] = tokenAddress;
Trying to clean-up the dictionary may not be worth the additional costs for each multisig node.
No description provided.