KVORUM
lidoSource: Snapshot · #0x4dd947f5e73377b074fd393148b377558179f22ea923d584dd3c718f3bab0687

Conversion of Treasury Stablecoins into sUSDS or TMMFs

succeededDec 1, 2025, 04:00 PM UTCsignaling · non-bindingbyFF0xff64…1fceView on Snapshot ↗

01Summary

AISummary by Kvorum

An AI summary is not generated yet. Read the description →

02Description

608 words

TL;DR

This proposal requests the DAO’s approval to execute the TMC-6 strategy and handle the related operations to allow the DAO to generate returns on its stablecoin holdings.

Proposal details

The Treasury Management Committee (”TMC”) has approved the TMC-6 strategy to allow the DAO to generate returns on its stablecoin holdings (currently ~USD 30M in idle stablecoins). Under this strategy, stablecoin funds could be withdrawn from the DAO Treasury and subsequently converted into sUSDS or a tokenized USD money market fund of choice.

While the TMC is authorized to approve automated strategies that require further on-chain DAO confirmation and allow the DAO to object to execution, this particular strategy is not automated. This proposal seeks explicit DAO confirmation that the TMC and the Lido Labs Foundation and Lido Ecosystem Foundation (together the "Foundations") are authorized to execute the strategy and carry out the associated operational steps. This confirmation is limited to the specific strategy, parameters, and guardrails set out in TMC-6 and this proposal, and the TMC together with the Foundations will act solely as implementation agents within these predefined limits, without independent discretion to manage, reallocate, or otherwise deploy DAO assets beyond what tokenholders explicitly approve here.

It is proposed that the initial upfront conversion (via minting sUSDS from USDS at par, without slippage) will be manually handled by the multisig signers of wallets belonging to the Foundations, under the following token conversion mechanics:

  • DAI can be exchanged for USDS at 1:1;
  • USDC can be exchanged for USDS at 1:1 via the PSM (Peg Stability Mechanism), which currently has more than 3bn USDC in available liquidity;
  • USDT may need to be traded for USDC, with low expected slippage (likely < 10 bps).

The USDC/DAI/USDT balances to be converted to sUSDS can be gradually drawn by the Foundations under the existing Easy Track smart contract instances.

The received stablecoins could be used by the Foundations in one of the following ways:

  1. The resulting sUSDS may be returned to the DAO Treasury by a simple multi-sig transfer.
  2. Pursuant to the approved EGG budget request, the Foundations are allowed to retain stablecoins or sUSDS for the payment of expenses until the next Easy Track limit reset, without being required to return such amount of sUSDS or stablecoins back to the DAO Treasury.
  3. Where KYC/KYB restrictions apply, the Foundations, as agents and on behalf of the DAO, may also retain tokenized USD money market funds (e.g., BlackRock BUIDL, Fidelity Digital Treasury Fund, Circle USYC).

Operational implementation details

During the implementation of this strategy, the TMC and the Foundations will adhere to the operational principles and guardrails defined under TMC-6:

  1. Yield-bearing cap: sUSDS plus tokenized money market funds (TMMFs) at or below 15% of total Treasury, checked quarterly and rebalanced if needed.
  2. Liquidity floor: Total stablecoin liquidity, excluding whichever is greater of the sUSDS balance or the largest single TMMF position, must cover at least 2 months’ worth of DAO operating costs; if breached, liquid non-yield-bearing stables are rebuilt first before increasing sUSDS or TMMF allocations.
  3. TMMFs: The TMC decides which TMMFs to onboard based on risk and potential rewards, legal and operational considerations, and then splits the yield-bearing allocation equally across all approved sUSDS and TMMF assets, with positions held by the Foundations on behalf of the DAO.

For a detailed description of the operational rules and guardrails, please see the relevant post on the Lido Research forum.

TMC Rotation

To support the implementation of this strategy and ensure robust operational execution, it is proposed to rotate TMC membership composition.

03Mismatch analysis

AIMismatch analysis by Kvorum

A calldata-vs-description analysis is not generated yet. Review the decoded actions →

04Actions

0 total

This proposal carries no on-chain actions.

05Tally

Summed from votes

Voters61
VP participating0
Outcome (current)Approve
Current support100%

06Voters

61 total
Filter:
VoterChoice% of totalRationale
4A0x4af8…6a0bApprove023.39%—1y ago
420x42e6…3fb0Approve018.28%—11mo ago
810x8172…922eApprove09.79%—11mo ago
7E0x7ee0…bb6cApprove09.15%—1y ago
990x99e4…bea1Approve06.39%—11mo ago
LIlido.banteg.eth0x55bc…f0faApprove06.34%—1y ago
9C0x9ca8…36afApprove05.73%—11mo ago
510x510a…8d0eApprove05.10%—11mo ago
AE0xae09…256bApprove04.20%—11mo ago
6D0x6d8d…0cccApprove02.46%—11mo ago
6F0x6f9b…8a1dApprove02.20%—1y ago
B60xb664…f890Approve01.98%—11mo ago
A40xa418…b737Approve01.88%—11mo ago
1F0x1f76…5ed6Approve01.80%—1y ago
870x8787…ea52Approve00.45%—1y ago
E80xe80e…28e8Approve00.41%—11mo ago
060x06a9…bba0Approve00.11%—11mo ago
3D0x3ddc…05b0Approve00.10%—1y ago
290x29b5…2c2fApprove00.09%—11mo ago
5D0x5df9…1b53Approve00.07%—1y ago
B90xb933…8dd1Approve00.04%—1y ago
2F0x2f80…bfcfApprove00.02%—1y ago
880x8845…53f5Approve00.01%—11mo ago
8A0x8ab6…e0baApprove00.00%—11mo ago
7A0x7af3…8df3Approve00.00%—11mo ago
C50xc554…7759Approve00.00%—11mo ago
960x96e4…de1cApprove00.00%—11mo ago
3D0x3d5a…b97fApprove00.00%—11mo ago
050x0579…ca09Approve00.00%—1y ago
990x991e…0eafApprove00.00%—1y ago
EC0xecdf…be56Approve00.00%—11mo ago
4D0x4d63…cbb1Approve00.00%—1y ago
450x45fc…1c19Approve00.00%—1y ago
DE0xde91…b98aApprove00.00%—11mo ago
A10xa1ed…4bc4Approve00.00%—11mo ago
690x699a…80f9Approve00.00%—11mo ago
F60xf673…853aApprove00.00%—11mo ago
EC0xecc2…6ac9Approve00.00%—11mo ago
B70xb792…89d7Approve00.00%—11mo ago
170x1729…b879Approve00.00%—11mo ago
4D0x4d32…bbfaApprove00.00%—11mo ago
9D0x9d57…65a5Approve00.00%—1y ago
2F0x2f2f…f78aApprove00.00%—1y ago
B30xb3bf…6ce4Approve00.00%—1y ago
BF0xbfd1…4f66Approve00.00%—1y ago
3F0x3fb1…4c8aApprove00.00%—1y ago
650x659f…dadcApprove00.00%—1y ago
CE0xce57…70f0Approve00.00%—1y ago
010x0151…c3b9Approve00.00%—11mo ago
AF0xaf90…7b3bApprove00.00%—1y ago
Showing 50

07Forum

No forum thread is confidently linked to this proposal.

08Similar proposals

AI · embeddings

No semantically similar proposals found yet.