What is the correct way to turn off upgradeability in a UUPSUpgradeable V5 contract?

[mrsalitre]

I've been pondering this issue for weeks because according to UUPSUpgradeable V5 documentation this is possible.

This is the only thing I've been able to find regarding the matter:

• UUPS Proxies: Tutorial (Solidity + JavaScript) - #10 by frangio
• UUPS Proxies: Tutorial (Solidity + JavaScript) - #36 by Phil

I know that I need to create a customized implementation of the original contract, but what modification should be made to safely turn off upgradeability in a UUPSUpgradeable V5 contract?

I have tried a couple of tests on the Sepolia network (attached contract because I can't attach any more links): 0x6a23937EA070f090d6a8eADdEE2B823C2b70fF7b
2 / 2

[0x_Taiga]

I think the easiest way it to overwrite the authorizeUpgrade function. You can just make it revert every time.

[mrsalitre]

also thought about this, but the final goal its to not display the ‘upgradeToAndCall’ function at all, and to modify the ‘_authorizeUpgrade’ in that way will probably cause an update error.

UUPS Proxies: Tutorial (Solidity + JavaScript)

Regarding killing the upgradeability: Can I kill it with only one upgrade by implementing an impossible check in the _authorizeUpgrade method? For example if I upgrade to a new implementation which contains this function: function _authorizeUpgrade(address) internal override { require(false, "no more upgrades allowed"); } Or does the upgrade then fail, because of the security checks in the function _upgradeToAndCallSecure and I should just override the UUPS functions to directly call t…

[0x_Taiga]

Well I guess the answer you are looking for is right underneath the message you linked. If you upgrade first to a version that does not conduct a rollback check and then upgrade that version to the version without any UUPS functionality, then that would probably work.