Quorum not reached

TFIP-36.1: Proposal to Update Signer on TrueFi Multisig Wallets Reposted


ID 671822...3656

ID 671822...3656

Proposed on: Jan 8th, 2026

Proposed on: Jan 8th, 2026

Votes

Actions

Type

Address

Details

Custom

0x4C19...3784

transfer(..)

Custom

Account

0x4C19...3784

Method

transfer(..)

Proposal

Due to the holiday period, community participation in this proposal was limited. 

Accordingly, we have decided to resubmit TFIP-36.1 under the same terms as the original proposal.

Summary

This proposal seeks to update one of the signers on three TrueFi multisig wallets:

  • Foundation Payroll multisig - 0xC2636A948a730D4578E07c36aFc6f8A8Fef59Df1
  • Plume multisig - 0xCd130E5833a7A30BcADBDB57DFc7aC88d2F8b572
  • New Treasury multisig - 0xC03151bAc97F692e5b71Eb49635A624141f7477b for operational continuity and to reflect the current availability of participants. Specifically, we propose replacing the current signer Vivek at address 0x622a48841fC326C4C60d3008bACc1a13011Af624 with Goblin at a new address 0x2ac4a7daD1eE2eACfA3E90dd6C69466CC66Df7B2.

Motivation

TrueFi DAO relies on a multisig for executing DAO-approved transactions and maintaining control over treasury assets. To ensure the multisig continues to function securely and efficiently, it’s important to keep signer addresses up to date. This change ensures that all participants remain active and reachable at their signing address.

Specification

Replace the existing signer on the TrueFi DAO Treasury Gnosis Safe, TrueFi Foundation Payroll Gnosis Safe, and TrueFi DAO Plume Gnosis Safe:

Remove: Vivek – 0x622a48841fC326C4C60d3008bACc1a13011Af624, 0xA8a9c3CB60dc5EE59464883Af56Ae8511B13C9F6

Add: Goblin – 0x2ac4a7daD1eE2eACfA3E90dd6C69466CC66Df7B2

There will be no change to the total number of signers or the signing threshold.

Next Steps

  1. Tally vote: The proposal will be posted on Tally for the final vote.
  2. To memorialize the proposal on Tally, 1 TRU will be transferred from Timelock contract to the TrueFi Foundation New Treasury.
  3. The replacement will be handled on the SAFE level.
Votes
Status