Proposals

/

Proposal

Executed

[TFIP-40.1] Timelock TRU allocation for rebranding and treasury recapitalization


User profile image

by

by

0x5D545DE6e81da180dBbb57926a0e49be7...

0x5D54...8Fb7

ID 549307...5275

ID 549307...5275

Proposed on: Mar 6th, 2026

Proposed on: Mar 6th, 2026

Votes

Actions

Type

Address

Details

Custom

transfer(..)

Custom

Account

0xA0b8...eB48

Method

transfer(..)

Custom

0x4C19...3784

transfer(..)

Custom

Account

0x4C19...3784

Method

transfer(..)

Proposal

After posting TFIP-40, we identified a technical issue with the execution parameters of the Tally proposal.

Specifically, the proposal did not leave enough tokens in the source wallet to cover the Tally execution fees required for the transaction. Because of this, the transaction fails in simulation and would fail during on-chain execution as well.

To resolve this, we are reposting the same proposal under TFIP-40.1, with slightly adjusted parameters so that enough tokens remain available to cover the execution fees.

The substance of the proposal remains unchanged.

Background

Following the approval and execution of TFIP-34 – Foundation Update: Wallet Recovery and Treasury Consolidation, the Foundation consolidated DAO-controlled assets under a unified operational structure.

Separately, under TFIP-37 – Authorization of TrueFi Rebrand and Treasury Recapitalization, the DAO approved the strategic direction for TrueFi’s rebranding and broader treasury recapitalization initiative.

TFIP-40 was introduced as an extension to authorize the allocation of assets held in a “timelock/public treasury” address to support execution of TFIP-37.


Correction Notice (Form, not Substance)

During the preparation of the on-chain Tally execution, we identified a parameter error in TFIP-40:

  • TFIP-40 referenced the Timelock smart contract address: 0x5Fe2F5F2Cc97887746C5cB44386A94061F35DcC4
  • However, the intended target for this action is the Public Treasury Timelock wallet0x4f4AC7a7032A14243aEbDa98Ee04a5D7Fe293d07

Because these are different addresses, the asset inventory is also different. This update is therefore a correction of form (address + assets), not of purpose: the DAO intent remains to allocate relevant public-treasury assets to support the execution of TFIP-37.


Updated Assets (Public Treasury Timelock)

The balances held at 0x4f4AC7a7032A14243aEbDa98Ee04a5D7Fe293d07 intended to be allocated under this revised proposal are:

  • 6,151.0529 USDC
  • 435,344.2321 TRU

Proposal

This proposal seeks DAO authorization to:

  1. Recognize 0x4f4AC7a7032A14243aEbDa98Ee04a5D7Fe293d07 as the correct Public Treasury Timelock address referenced in the proposal.
  2. Allocate the assets held in this wallet (6,151.0529 USDC and 435,344.2321 TRU) to support the execution of TrueFi Rebranding and Treasury Recapitalization, as outlined in TFIP-37.
  3. Transfer these assets to the Foundation-managed operational multisignature wallet: New Treasury - 0xC03151bAc97F692e5b71Eb49635A624141f7477b
  4. Ensure the assets remain fully visible and traceable on-chain, consistent with the treasury consolidation principles established under TFIP-34.

Rationale

This action aligns directly with the DAO-approved strategic direction under TFIP-37 and enables execution using existing DAO-owned resources, without requiring new minting, inflationary actions, or premature external fundraising.


Additional Context

The Foundation continues to work through legacy infrastructure and historical treasury arrangements. As part of that work, we will occasionally encounter discrepancies between historical labeling/assumptions and the on-chain reality. In this case, the goal remains unchanged, but the exact address and asset inventory required correction prior to any binding on-chain execution.


Next Governance Steps

As this proposal does not fall under simplified governance exemptions, it must follow the full governance process:

Tally Vote: If Snapshot passes (or the amendment period concludes), the proposal proceeds to Tally for a binding on-chain vote.

Votes
Status