Consider implementing two-step procedure for updating protocol addresses

[hats-bug-reporter]

Github username: @saidqayoumsadat
Submission hash (on-chain): 0x01084ca89022df2e567180e61d19471e12a796e4ee32eeda9c6cd4ed1cdac698
Severity: low

Description:
Description

A copy-paste error or a typo may end up bricking protocol functionality, or sending tokens to an address with no known private key. Consider implementing a two-step procedure for updating protocol addresses, where the recipient is set as pending, and must 'accept' the assignment by making an affirmative call. A straight forward way of doing this would be to have the target contracts implement EIP-165, and to have the 'set' functions ensure that the recipient is of the right

file: /contracts/tokenlock/TokenLockFactory.so

117    function setMasterCopy(address _masterCopy) external override onlyOwner {
        _setMasterCopy(_masterCopy);
119    }

https://github.com/hats-finance/hats-contracts/blob/0d6ebbde912bc272d9b310140d434ee2aacd36d3/contracts/tokenlock/TokenLockFactory.sol#L117-L119

[jellegerbrandy]

Seeting the master copy here in the factory will not "brick the protocol"