-
Notifications
You must be signed in to change notification settings - Fork 8
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
Boson voucher owner should not be able to renounceOwnership #588
Comments
I agree with this, especially given that updating the assistant will always impact the ownership of the vouchers, probably worth just making this action do nothing for now. |
Good find |
zajck
added a commit
that referenced
this issue
Apr 19, 2023
anajuliabit
pushed a commit
that referenced
this issue
Apr 21, 2023
* Alternative tokenId * fix tests * move id handling to reserve range * fix integration * set min exchange id in constructor * fix deploy * fix unit tests * review fixes * remove extractExchageId + optimize vouchers * remove transferpremintedFrom * Fix #587 * rename seller -> rangeOwner * Change balance check * fix old test * Fix #588 * Refactor tests A-D * Refactor tests E-M * Refactor tests O-T * use util functions in upgrade tests * Refactor integration tests * Fix failing tests * Refactor client tests * added missing accountIds * simplify: no facetNames required anymore * Improved chunking algorithm * Cover uncovered branches * add missing tests + config * CI: coverage * set _committed in issueVoucher * uncomment line --------- Co-authored-by: Mischa <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
BosonVoucher
inheritsOwnableUpgradeable
which implements methodrenounceOwnership()
. If owner calls it, it loses its owner privileges, therefore it can no longer call methods withonlyOwner
modifier. Affected functions arepreMint
,burnPremintedVouchers
,setContractURI
,callExternalContract
andsetApprovalForAllToContract
.If that happens, seller is not totally broken, since updating assistant address in the protocol also sets it as a new contract owner. Therefore this is then merely an inconvenience that can happen. It is still better to prevent it.
Also, since
transferOwnership
is restricted (owner cannot call it directly) it does not make sense to leave a similar function unrestricted. Most likely renouncing ownership should be part of acount deactivation inside the protocol.Recommendation:
Override
renounceOwnership()
inBosonVoucher
and revert if it is called.The text was updated successfully, but these errors were encountered: