• © Goverland Inc. 2026
  • v1.0.1
  • Privacy Policy
  • Terms of Use
SafeDAO 🌡️ CheckSafeDAO 🌡️ Checkby0x1C0Aa8cCD568d90d61659F060D1bFb1e6f855A20z0r0z.eth

unpause() Safe Token

Voting ended over 3 years agoSucceeded

Safe Token is currently paused().

This means that its EIP-20 compliant functions, transfer() and transferFrom() do not work, making Safe Token nontransferable.

This was the default setting on deployment.

Only the owner() of Safe Token can call the unpause() function.

Calling unpause() on Safe Token will make it transferable and fully enable its EIP-20 interface.

This owner() is currently the Safe Foundation multisig contract (0x8CF60B289f8d31F737049B590b5E4285Ff0Bd1D1)

This proposal seeks to produce a signal to the Safe Foundation and its key signers to call unpause() on Safe Token.

This will provide many benefits to Safe Token users, which include:

More Security: Enabling users to transfer Safe Token balances to multiple wallets will allow greater distribution of the risk of maintaining private keys and multisig roles.

More Utility: Safe Token can be integrated into other contracts if they can manage its balances using the EIP-20 interface for transfer functions.

Reduce Liability: Multisig key signers may not want the continued responsibility of possessing Safe Token balances, particularly where the key signers are acting on behalf of a greater association of users that want shared possession of Safe Token balances.

Whether the Safe Foundation should also permanently enable transfers by calling renounceOwnership() is beyond the scope of this signal proposal. It seems useful to take things one step at a time.

This author has not discussed this signal proposal with the Safe Foundation or any other Safe Token user. It is made out of interest as a Safe Token user.

Off-Chain Vote

👍
862.87K SAFE59.6%
👎
585.08K SAFE40.4%
Download mobile app to vote

Timeline

Oct 16, 2022Proposal created
Oct 16, 2022Proposal vote started
Oct 31, 2022Proposal vote ended
Jul 09, 2025Proposal updated