-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
feat(protocol,supplementary-contracts): relocate & allow TokenUnlock to deploy and own ProverSets #17251
Conversation
feat(protocol,supplementary-contracts): relocate & allow TokenUnlock to deploy and own ProverSets
🚨 Report Summary
For more details view the full report in OpenZeppelin Code Inspector |
Wouldn't this allow people to withdraw a big chunk of their tokens by getting slashed and then getting the reward? I guess would have to think about the specifics and some protocol details, but for example if you can prove a block wrongly and directly also contest and prove it correctly in the same tx you would be able to extract a big chunk without any risks of anybody else getting the tokens. So sure you still lose a big chunk, but you also don't have to wait 4 years to get your tokens. |
…to deploy ProverSet (#17252)
Good points. I believe technically it is possible. However, I think practically this won't happen for two reasons:
|
Yeah true that if SGX is required for each block it shouldn't be possible, so should be good. |
I'm not 100% sure about the behavior for this in the protocol right now, but the liveness bond slashing could also be a potential way to avoid the locking. But that one is probably a lot trickier to pull off risk free. |
As of now liveness bond is the smallest bond compared with all other bonds. When liveness bond is returned, another larger bond must be placed. I think in the future, the liveness bond shall alway be smaller than validity/contestation bond. |
Allow Taiko's investors to use their locked tokens as bonds.