Track: Root
Proposer: ChaosDAO, JUST Ventures, Hydration
Date: March 2025
Requested allocation: 5,001,000 DOT
Short description: We proposed a structured approach for the Polkadot Treasury to obtain native USDT and USDC, for the purpose of diversification and enabling it to pay out expenses in a stable asset. Through this referendum, we aspire to renew the schedule presented in proposal #457 and convert 2,500,000 DOT into USDT and 2,500,000 DOT into USDC via the DCA mechanism described in detail below, where an additional 1000 DOT is reserved for transaction fees. This proposal presents a long-term solution to acquire different tokens in exchange for treasury DOT by Polkadot governance participants.
Context of the proposal:
Probably one of the most-requested features is the ability to make Treasury proposals in stablecoins like USDT and USDC. This is for many reasons, including less volatility around Treasury proposals and preserving the value of the Polkadot Treasury to ensure funds are available to support a given budget in the future.
With the latest upgrades to Substrate and the Polkadot runtime, the Treasury has a lot more tools available to it for its management, including proposals with non-DOT assets like stablecoins.
As was done in referendum 457, this proposal is to convert 5,000,000 DOT to USDT and USDC over the course of the next year, with 50% going to each. This uses Hydration's DCA feature to convert a little bit each day and ensure a steady flow of stablecoins into the Treasury.
Unlike 457, this referendum sells a fixed amount of DOT per trade rather than acquiring a fixed amount of USDT/C. For better capital efficiency, the full amount of DOT will be also initially converted into aDOT (yield-bearing collateral token) and supplied into the Hydration Borrow feature. By doing so, the Polkadot Treasury will accumulate yield on the dormant DOT, while substantially increasing the DOT supply available for borrowing, thus enabling more DeFi use cases. More details can be found in this post.
Moreover it newly utilizes the “Rolling DCA” feature, which enables renewing the schedule just by sending DOT to the proxy account. This in turn means other governance tracks with lower security assumptions, such as Treasurer, can be used for smaller topups if needed.
This amount accounts for about 22% of the new DOT expected to be minted into the Treasury over the next year (this could vary based on variables like the staking rate).
Proposal objective(s) or solution(s):
The central proposition entails the creation of a schedule that converts DOT into USDT and USDC via the DCA feature on Hydration, a parachain on Polkadot.
The attributes of this proposal are:
DCA schedule parameters: [USDT]
DCA schedule parameters: [USDC]
Fee estimation breakdown:
Note: Fees depend heavily on the schedule settings and are estimated based on parameters used. It is worth mentioning that the Hydration protocol also uses dynamic fees based on block space utilization ranging 0.15-5% to protect liquidity providers in times of volatility. All time average trade fees as of proposal submission are around 0.3%.
Description of steps utilizing XCM to achieve the solution:
Send 5,000,001DOT from the Polkadot treasury to the Pure Proxy account [7N4oFqXKgeTXo6CMSY9BVZdHP5J3RhQXY77Fe7qmQwjcxa1w] controlled exclusively by the relay chain sovereign account on Hydration [7KQx4f7yU3hqZHfvDVnSfe6mpgAT8Pxyr67LXHV6nsbZo3Tm]
After 1 block to process balance state changes on Hydration, schedule sending an XCM program to Transact on Hydration. This will initiate two DCA schedules, each with a total amount of 2,500,000 DOT, swapping 20 DOT to USDT and USDC every 20 blocks.
Once the first USDT chunk is accumulated, initiate a periodic schedule that sends cross-chain chunks of 5,000 USDT and 5,000 USDC from the Pure Proxy on Hydration to the General Treasury account on the Polkadot Asset Hub [14xmwinmCEz6oRrFdczHKqHgWNMiCysE2KrA4jXXAAM1Eogk], totaling to max. 27500 transactions.
Threshold
I have noticed that the current mechanism allows for circumventing the Treasury’s 1% burn every 24 days once again. Given this, have we ever considered increasing the burn rate to 2% or even higher to enhance efficiency?
Your insights on this matter would be greatly appreciated.
Thank you for your time and consideration.