Opportunity Cost and Past Performance
At present, over 10,000 ETH sits idle in the treasury, generating no yield and contributing minimally to the growth of the ecosystem. Allocating a portion of this to yield-generating strategies is in line with treasury management best practices.
Since May, the ATMC ETH-denominated strategies have generated 43.4 ETH, utilizing AAVE, Fluid, Camelot, and Lido. Performance and a detailed breakdown of the ETH allocations, as well as other treasury strategies, can be seen here.
Assuming a prospective allocation of 8500 ETH and a conservative ETH-denominated yield of ~2.4% (illustrative figure based on the 30-day average annualized yield for existing ATMC strategies), the DAO is foregoing approximately 204 ETH annually, which is $891k at current market prices. Even at the lowest 30-day average annualized yield rate of 2.04% (recorded July 15th), the projected opportunity cost of letting this ETH sit unallocated is 173 ETH, or $756k at current market prices.
From a treasury management perspective, maintaining a large passive ETH position without a corresponding yield strategy is suboptimal, especially when there exists a variety of deployments that would be appropriate to allocate it to, including but not limited to native staking, restaking, DEX liquidity provision, and lending market supply.
DeFi Ecosystem Support
This proposal is in direct strategic alignment with the current DRIP campaign, fulfilling treasury management’s dual mandate of:
A major goal of the Arbitrum DRIP program is to spur activity within the broader Arbitrum DeFi ecosystem, initially focusing on boosting leveraged looping strategies within DeFi utilizing yield-bearing collateral. Decisions regarding these funds will prioritize supporting these initiatives where possible, deploying productive capital across various venues, though this will not take absolute precedent over existing considerations regarding risk, liquidity, partnership opportunities, sustainable yields, etc.
Some indicative examples of DRIP-aligned treasury strategies would be supplying unstaked ETH to lending markets, or staking ETH with LST/LRT providers, and exploring adding DEX liquidity across native ETH and LST/LRTs pools. With some of these strategies, we can ensure that users who are looking to participate in DRIP have ample liquidity, and we can even make an impact by stabilizing lending market utilization rates, reducing borrowing costs or slippage.
As with prior deployments, we intend to communicate with prospective partner protocols to negotiate terms beneficial to the DAO or reduced costs on any deployments when possible or appropriate.
Entropy proposes that the new tranche of 8500 ETH be used in a variety of generally lower-risk, ecosystem-supporting protocols, including but not limited to
The 8500 ETH is not intended to mirror the existing treasury strategy deployments, unless extenuating circumstances indicate these to be undoubtedly the best option to support the ecosystem and generate risk-adjusted returns. The DAO’s wallets will be blacklisted from receiving any possible DRIP incentives.
For this proposal, we will not be conducting an open RFP process for protocols to apply for funding. Entropy will proactively engage with protocols providing services that align with our strategic goals. To have full confidence in the deployment of this capital, evaluations of various strategies will heavily take into account criteria such as protocol maturity, ecosystem impact, yield sustainability, and economic and smart contract risk.
As structured in the ATMC proposal, the elected OAT body will maintain full ability to approve or deny granular selection decisions. No allocation can be made unilaterally by Entropy. Funds will be sent to and custodied by the Arbitrum Foundation. Rebalancing needs will be examined as part of our normal treasury management reporting cadence, considering liquidity constraints, yield conditions, or shifts in ecosystem needs.
Given that the 8500 ETH requested represents a material portion of the non-ARB, unallocated treasury funds, capital preservation and long-term impact remain primary priorities. The following benchmarks guide Entropy’s allocation strategy:
Entropy recognizes and agrees with delegates that at certain times a deployment to support ecosystem growth should be prioritized over a pure yield strategy. Our team weighs growth opportunities against foregone yield based on a few factors:
Opportunity Cost and Past Performance
At present, over 10,000 ETH sits idle in the treasury, generating no yield and contributing minimally to the growth of the ecosystem. Allocating a portion of this to yield-generating strategies is in line with treasury management best practices.
Since May, the ATMC ETH-denominated strategies have generated 43.4 ETH, utilizing AAVE, Fluid, Camelot, and Lido. Performance and a detailed breakdown of the ETH allocations, as well as other treasury strategies, can be seen here.
Assuming a prospective allocation of 8500 ETH and a conservative ETH-denominated yield of ~2.4% (illustrative figure based on the 30-day average annualized yield for existing ATMC strategies), the DAO is foregoing approximately 204 ETH annually, which is $891k at current market prices. Even at the lowest 30-day average annualized yield rate of 2.04% (recorded July 15th), the projected opportunity cost of letting this ETH sit unallocated is 173 ETH, or $756k at current market prices.
From a treasury management perspective, maintaining a large passive ETH position without a corresponding yield strategy is suboptimal, especially when there exists a variety of deployments that would be appropriate to allocate it to, including but not limited to native staking, restaking, DEX liquidity provision, and lending market supply.
DeFi Ecosystem Support
This proposal is in direct strategic alignment with the current DRIP campaign, fulfilling treasury management’s dual mandate of:
A major goal of the Arbitrum DRIP program is to spur activity within the broader Arbitrum DeFi ecosystem, initially focusing on boosting leveraged looping strategies within DeFi utilizing yield-bearing collateral. Decisions regarding these funds will prioritize supporting these initiatives where possible, deploying productive capital across various venues, though this will not take absolute precedent over existing considerations regarding risk, liquidity, partnership opportunities, sustainable yields, etc.
Some indicative examples of DRIP-aligned treasury strategies would be supplying unstaked ETH to lending markets, or staking ETH with LST/LRT providers, and exploring adding DEX liquidity across native ETH and LST/LRTs pools. With some of these strategies, we can ensure that users who are looking to participate in DRIP have ample liquidity, and we can even make an impact by stabilizing lending market utilization rates, reducing borrowing costs or slippage.
As with prior deployments, we intend to communicate with prospective partner protocols to negotiate terms beneficial to the DAO or reduced costs on any deployments when possible or appropriate.
Entropy proposes that the new tranche of 8500 ETH be used in a variety of generally lower-risk, ecosystem-supporting protocols, including but not limited to
The 8500 ETH is not intended to mirror the existing treasury strategy deployments, unless extenuating circumstances indicate these to be undoubtedly the best option to support the ecosystem and generate risk-adjusted returns. The DAO’s wallets will be blacklisted from receiving any possible DRIP incentives.
For this proposal, we will not be conducting an open RFP process for protocols to apply for funding. Entropy will proactively engage with protocols providing services that align with our strategic goals. To have full confidence in the deployment of this capital, evaluations of various strategies will heavily take into account criteria such as protocol maturity, ecosystem impact, yield sustainability, and economic and smart contract risk.
As structured in the ATMC proposal, the elected OAT body will maintain full ability to approve or deny granular selection decisions. No allocation can be made unilaterally by Entropy. Funds will be sent to and custodied by the Arbitrum Foundation. Rebalancing needs will be examined as part of our normal treasury management reporting cadence, considering liquidity constraints, yield conditions, or shifts in ecosystem needs.
Given that the 8500 ETH requested represents a material portion of the non-ARB, unallocated treasury funds, capital preservation and long-term impact remain primary priorities. The following benchmarks guide Entropy’s allocation strategy:
Entropy recognizes and agrees with delegates that at certain times a deployment to support ecosystem growth should be prioritized over a pure yield strategy. Our team weighs growth opportunities against foregone yield based on a few factors:
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/51
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/50?u=maxlomu
The Event Horizon Community voted AGAINST on this Proposal (ehARB-134): EventHorizon.vote/vote/arbitrum/ehARB-134
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/48
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/48?u=blockful
https://forum.arbitrum.foundation/t/the-dao-incentive-program-dip-2-0/30080/39?u=euphoria
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/51
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/50?u=maxlomu
The Event Horizon Community voted AGAINST on this Proposal (ehARB-134): EventHorizon.vote/vote/arbitrum/ehARB-134
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/48
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/48?u=blockful
https://forum.arbitrum.foundation/t/the-dao-incentive-program-dip-2-0/30080/39?u=euphoria
past yield is not enough to justify this much money being put outside the control of tokenholders and the transparency guarantees of the shared IPS framework are also not enough.
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/17?u=possumlabs
https://forum.arbitrum.foundation/t/gfx-labs-delegate-communication-thread/13794
https://forum.arbitrum.foundation/t/tekr0x-eth-delegate-communication-thread/24804/23
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/14
As ITU Blockchain, we voted FOR this proposal. We share the authors’ view that putting idle ETH to work via the ATMC is timely and beneficial—preserving principal, earning conservative yield, and easing DRIP-era liquidity without selling ARB. Our support rests on prudent diversification and using mature venues to reduce utilization spikes and slippage. We also encourage clear position limits, provider diversification, and simple reporting against benchmarks to keep execution disciplined.
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/28
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/4?u=0xdonpepe
past yield is not enough to justify this much money being put outside the control of tokenholders.
The Event Horizon Community voted on this proposal (ehARB-131): EventHorizon.vote/vote/arbitrum/ehARB-131
The Event Horizon Community voted FOR on this proposal (ehARB-131): EventHorizon.vote/vote/arbitrum/ehARB-131
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/26?u=euphoria
For, Supporting this proposal unlocks idle assets, bolstering the Arbitrum DeFi landscape with sustainable yield generation, while ATMC's proven success ensures effective risk mitigation and ecosystem support.
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/22
https://forum.arbitrum.foundation/t/tekr0x-eth-delegate-communication-thread/24804/23?u=tekr0x.eth
Voting for because the opportunity cost of not deploying the unallocated ETH is high and the ATMC has been performant, but why add additional risk layers by using lending markets and DEXs when wstETH the same or higher yield of ~2.6%?
https://forum.arbitrum.foundation/t/gfx-labs-delegate-communication-thread/13794
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/14
In our opinion, putting this amount of value at any risk for a meager 2.4% APY - before expenses - isn't justified.
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/15?u=griff
past yield is not enough to justify this much money being put outside the control of tokenholders and the transparency guarantees of the shared IPS framework are also not enough.
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/17?u=possumlabs
https://forum.arbitrum.foundation/t/gfx-labs-delegate-communication-thread/13794
https://forum.arbitrum.foundation/t/tekr0x-eth-delegate-communication-thread/24804/23
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/14
As ITU Blockchain, we voted FOR this proposal. We share the authors’ view that putting idle ETH to work via the ATMC is timely and beneficial—preserving principal, earning conservative yield, and easing DRIP-era liquidity without selling ARB. Our support rests on prudent diversification and using mature venues to reduce utilization spikes and slippage. We also encourage clear position limits, provider diversification, and simple reporting against benchmarks to keep execution disciplined.
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/28
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/4?u=0xdonpepe
past yield is not enough to justify this much money being put outside the control of tokenholders.
The Event Horizon Community voted on this proposal (ehARB-131): EventHorizon.vote/vote/arbitrum/ehARB-131
The Event Horizon Community voted FOR on this proposal (ehARB-131): EventHorizon.vote/vote/arbitrum/ehARB-131
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/26?u=euphoria
For, Supporting this proposal unlocks idle assets, bolstering the Arbitrum DeFi landscape with sustainable yield generation, while ATMC's proven success ensures effective risk mitigation and ecosystem support.
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/22
https://forum.arbitrum.foundation/t/tekr0x-eth-delegate-communication-thread/24804/23?u=tekr0x.eth
Voting for because the opportunity cost of not deploying the unallocated ETH is high and the ATMC has been performant, but why add additional risk layers by using lending markets and DEXs when wstETH the same or higher yield of ~2.6%?
https://forum.arbitrum.foundation/t/gfx-labs-delegate-communication-thread/13794
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/14
In our opinion, putting this amount of value at any risk for a meager 2.4% APY - before expenses - isn't justified.
https://forum.arbitrum.foundation/t/transfer-8-500-eth-from-the-treasury-to-atmc-s-eth-treasury-strategies/29983/15?u=griff
Although I agree with the plan of not letting idle ETH sit, this didn’t really share what mechanism we would pursue in terms of yield. Therefore against until we can at least where this will get parked or what strategies we are pursuing.
Although I agree with the plan of not letting idle ETH sit, this didn’t really share what mechanism we would pursue in terms of yield. Therefore against until we can at least where this will get parked or what strategies we are pursuing.
Hi all,
Confirming the AF address as 0x5CE3C2BDd8fe4D35a20a18CbAFab22447DE68aBe for receiving the funds.
Hey folks just wanted to give everyone a quick update that Tally experienced a temporary indexer error yesterday and the ‘Transfer 8,500 ETH from the Treasury to ATMC’s ETH Treasury Strategies’ proposal was briefly unavailable when it was created onchain. The root cause was trying to generate the timelock topic ID for tracking the proposal status across L2 & L1 - this has now been resolved, and the proposal can now be accessed on Tally here.
We will be sharing a more detailed incident report once it is ready, and we apologize for the minor inconvenience caused yesterday.
Hi all,
Confirming the AF address as 0x5CE3C2BDd8fe4D35a20a18CbAFab22447DE68aBe for receiving the funds.
Hey folks just wanted to give everyone a quick update that Tally experienced a temporary indexer error yesterday and the ‘Transfer 8,500 ETH from the Treasury to ATMC’s ETH Treasury Strategies’ proposal was briefly unavailable when it was created onchain. The root cause was trying to generate the timelock topic ID for tracking the proposal status across L2 & L1 - this has now been resolved, and the proposal can now be accessed on Tally here.
We will be sharing a more detailed incident report once it is ready, and we apologize for the minor inconvenience caused yesterday.
There is a lot of underestimation about the second-order effects of making the DAO the first customers of Arbitrum protocols. Any 0.x% more yield we could get on the Ethereum we have will greatly be outpaced by any positive mindshare that changes how the ecosystem is perceived..
I want to highlight this quote from Jojo, because I think it touches on a crucial aspect that deserves more consideration.
There is a lot of underestimation about the second-order effects of making the DAO the first customers of Arbitrum protocols. Any 0.x% more yield we could get on the Ethereum we have will greatly be outpaced by any positive mindshare that changes how the ecosystem is perceived..
I want to highlight this quote from Jojo, because I think it touches on a crucial aspect that deserves more consideration.
Agreed, I was wondering the same.
Also wondering why, of the DAO Treasury’s ~10.5K ETH unallocated, this proposal is for just 8500?
Agreed, I was wondering the same.
Also wondering why, of the DAO Treasury’s ~10.5K ETH unallocated, this proposal is for just 8500?
Thank you for the answer, I'm looking forward to it.
Could you please also refer to the second part of my question?
Can we expect that, for each allocation you make, we’ll be able to see your assumptions regarding these three factors? This would allow the DAO to retain and build on the learnings from those decisions.
Thank you for the answer, I'm looking forward to it.
Could you please also refer to the second part of my question?
Can we expect that, for each allocation you make, we’ll be able to see your assumptions regarding these three factors? This would allow the DAO to retain and build on the learnings from those decisions.
I would like to understand the practical implications of having those assessment factors.
The IPS is now posted in the forum. The proposal here contains all the information needed to make an informed decision. It outlines the rationale, opportunity cost, structure, safeguards, and deployment process in detail. The IPS is a supporting document designed to provide deeper ongoing insight into how the ATMC operates. We’ll continue to share performance data and allocation breakdowns through our normal reporting cadence, and of course incorporate delegate feedback as we go. But the core decision here is whether to activate 8,500 idle ETH. https://forum.arbitrum.foundation/t/arbitrum-treasury-management-investment-policy-statement-q4-2025/30117?u=entropy
The default state of the ATMC, through its monthly and quarterly updates, is full transparency. That said certains elements of deployments (especially in strategic growth allocations) will remain confidential only when necessary, for greater DAO interests. This is outlined in section 7.5.2. of the IPS.
gm, I voted FOR on this proposal. The priority right now is putting the idle ETH to work in a way that benefits the Arbitrum ecosystem.
I still believe clearer communication on the actual strategy and future allocation of the deployed ETH would be beneficial.
gm, I voted FOR on this proposal. The priority right now is putting the idle ETH to work in a way that benefits the Arbitrum ecosystem.
I still believe clearer communication on the actual strategy and future allocation of the deployed ETH would be beneficial.
However, I understand the perspective of the Entropy team expressed in their IPS (thanks for publishing it). I hope that in the future we can find a middle ground to better understand (and possibly influence) how the actual allocation will work.

Thanks
We are voting FOR this proposal.
From our perspective, it would be beneficial for the DAO to consider a model that functions on a recurring basis rather than relying on a single transfer, as @karpatkey suggested.
We are voting FOR this proposal.
From our perspective, it would be beneficial for the DAO to consider a model that functions on a recurring basis rather than relying on a single transfer, as @karpatkey suggested.
In fact, we would encourage the DAO to make this a recurring practice rather than a one-off transfer. Regularly channelling the ETH generated from Sequencer fees and Timeboost into ATMC would ensure that capital doesn’t accumulate unused and instead becomes part of a structured treasury management approach. Over time, this could both improve the DAO’s yield and align our treasury strategy more closely with ecosystem development goals.
To make this effective, it is essential that any investment or treasury strategy be presented with full clarity on both risks and associated costs. This transparency is necessary not only for accountability but also for allowing delegates and tokenholders to understand what is being implemented and why. It would be helpful to know whether the team already has a structured plan for these funds.
Regarding yield, we agree with @0xDonPepe. The DAO should aim for returns that are competitive while still maintaining low risk exposure.
From a governance and security standpoint, we share cp0x’s concern:
DAO Loses Control
There’s no real role for the DAO in this scheme.
All decisions are approved solely by the OAT committee.
I don’t see how the DAO can influence these decisions in any meaningful way, which is why it’s so important to first know which strategies these funds will be allocated to, before transferring them. That’s a governance gap for such a large sum.
We understand that full DAO level approval for every operational step can slow execution. However, there must be a balance so the process does not become closed off or almost self referential. For this proposal to move forward in a final form, we believe it requires a more explicit description of responsibilities, oversight, and safeguards.
We remain positive about the overall direction.
Hey @krst thank you very much for the comment. The IPS document will be posted by the end of the week and will be linked under this proposal.
voting Against on this onchain vote because past yield is not enough to justify this much money being put outside the control of tokenholders and the transparency guarantees of the shared IPS framework are also not enough.
Thank you very much @Entropy for hosting the call - the presented vision for IPS is promising.
Do you have any updates on the document? During the call, you mentioned that you expected to present it to OAT for approval at the beginning of last week. If that’s the case, will the DAO be able to review the document sometime this week?
Thank you very much @Entropy for hosting the call - the presented vision for IPS is promising.
Do you have any updates on the document? During the call, you mentioned that you expected to present it to OAT for approval at the beginning of last week. If that’s the case, will the DAO be able to review the document sometime this week?
Our team weighs growth opportunities against foregone yield based on a few factors: ...
Can we expect that, for each allocation you make, we’ll be able to see your assumptions regarding these three factors? This would allow the DAO to retain and build on the learnings from those decisions.
voted Against on this offchain vote because past yield is not enough to justify this much money being put outside the control of tokenholders.
Thanks (again) for the proposal.
After my comment and the Snapshot vote, I didn’t see any response. Of course, I don’t necessarily mean a direct reply to me, I have no such expectations!! However, I carefully read through the entire discussion that followed my comment, and still couldn’t find any point that could help me address my concerns. On the contrary, I noticed even more concerns being raised by a lot of delegates, like @Euphoria’s rationale, which also increased my anxiety over this proposal.
The following reflects the views of the Lampros DAO governance team, composed of Chain_L (@Blueweb) and @Euphoria, based on our combined research, analysis, and ideation.
We are voting AGAINST this proposal in the Tally voting.
The following reflects the views of the Lampros DAO governance team, composed of Chain_L (@Blueweb) and @Euphoria, based on our combined research, analysis, and ideation.
We are voting AGAINST this proposal in the Tally voting.
We appreciate that the team published an Investment Policy Statement. The IPS adds structure and explains how the ATMC will think about benchmarks, opportunity cost, and growth versus yield decisions. Still, the IPS does not resolve the two core reasons we opposed the proposal on Snapshot: underperformance and no clear implementation plan.
The current and historic allocations have not shown that they beat simple staking once fees and costs are included. We need a clear, side-by-side net yield comparison that shows expected returns after custody fees, management fees, gas, bridge costs, and any other expenses. Without that net comparison, we cannot judge the true opportunity cost of moving 8,500 ETH.
The proposal still lacks a concrete allocation plan. We expect a detailed list of target protocols or a phased tranche plan with checkpoints and OAT sign-offs. We will not support transferring a material sum first and deciding specific allocations later.
As ITU Blockchain, we voted FOR this proposal, and we share the authors’ view that putting idle ETH to work via the ATMC is the right move now. It helps protect principal, earn conservative yield, and improve DRIP-period liquidity without selling ARB. We support a diversified approach using mature venues to reduce utilization spikes and slippage. We also encourage clear position limits, provider diversification, and simple benchmark-based reporting to keep execution disciplined.
Thank you to the delegates who took time to join the Treasury Management call earlier today. The recording of the call can be accessed here. The proposal has been updated with the following langauge:
The following reflects the views of L2BEAT’s governance team, composed of @krst and @Manugotsuka, and it’s based on their combined research, fact-checking, and ideation.
We are voting FOR.
The following reflects the views of L2BEAT’s governance team, composed of @krst and @Manugotsuka, and it’s based on their combined research, fact-checking, and ideation.
We are voting FOR.
We want to start by thanking Entropy for introducing and implementing the Investment Policy Statement (IPS). This addition marks a significant improvement in the DAO’s treasury management framework, bringing more structure, transparency, and accountability to how funds are managed.
The IPS establishes clear standards for reporting and performance evaluation that the ATMC must now fulfill. It addresses many of the concerns previously raised about the lack of visibility and reporting , providing a well-defined foundation for responsible asset management.
We also believe this IPS should become a standard requirement for any future initiative involving DAO-managed funds. A consistent framework like this will help ensure accountability, comparability, and clarity across all treasury-related programs, ultimately strengthening DAO-wide governance practices.
With IPS in place we feel comfortable with approving the transfer of DAO funds for management.
Thank you for the answer, I'm looking forward to it.
Could you please also refer to the second part of my question?
Can we expect that, for each allocation you make, we’ll be able to see your assumptions regarding these three factors? This would allow the DAO to retain and build on the learnings from those decisions.
Thank you for the answer, I'm looking forward to it.
Could you please also refer to the second part of my question?
Can we expect that, for each allocation you make, we’ll be able to see your assumptions regarding these three factors? This would allow the DAO to retain and build on the learnings from those decisions.
I would like to understand the practical implications of having those assessment factors.
The IPS is now posted in the forum. The proposal here contains all the information needed to make an informed decision. It outlines the rationale, opportunity cost, structure, safeguards, and deployment process in detail. The IPS is a supporting document designed to provide deeper ongoing insight into how the ATMC operates. We’ll continue to share performance data and allocation breakdowns through our normal reporting cadence, and of course incorporate delegate feedback as we go. But the core decision here is whether to activate 8,500 idle ETH. https://forum.arbitrum.foundation/t/arbitrum-treasury-management-investment-policy-statement-q4-2025/30117?u=entropy
The default state of the ATMC, through its monthly and quarterly updates, is full transparency. That said certains elements of deployments (especially in strategic growth allocations) will remain confidential only when necessary, for greater DAO interests. This is outlined in section 7.5.2. of the IPS.
gm, I voted FOR on this proposal. The priority right now is putting the idle ETH to work in a way that benefits the Arbitrum ecosystem.
I still believe clearer communication on the actual strategy and future allocation of the deployed ETH would be beneficial.
gm, I voted FOR on this proposal. The priority right now is putting the idle ETH to work in a way that benefits the Arbitrum ecosystem.
I still believe clearer communication on the actual strategy and future allocation of the deployed ETH would be beneficial.
However, I understand the perspective of the Entropy team expressed in their IPS (thanks for publishing it). I hope that in the future we can find a middle ground to better understand (and possibly influence) how the actual allocation will work.

Thanks
We are voting FOR this proposal.
From our perspective, it would be beneficial for the DAO to consider a model that functions on a recurring basis rather than relying on a single transfer, as @karpatkey suggested.
We are voting FOR this proposal.
From our perspective, it would be beneficial for the DAO to consider a model that functions on a recurring basis rather than relying on a single transfer, as @karpatkey suggested.
In fact, we would encourage the DAO to make this a recurring practice rather than a one-off transfer. Regularly channelling the ETH generated from Sequencer fees and Timeboost into ATMC would ensure that capital doesn’t accumulate unused and instead becomes part of a structured treasury management approach. Over time, this could both improve the DAO’s yield and align our treasury strategy more closely with ecosystem development goals.
To make this effective, it is essential that any investment or treasury strategy be presented with full clarity on both risks and associated costs. This transparency is necessary not only for accountability but also for allowing delegates and tokenholders to understand what is being implemented and why. It would be helpful to know whether the team already has a structured plan for these funds.
Regarding yield, we agree with @0xDonPepe. The DAO should aim for returns that are competitive while still maintaining low risk exposure.
From a governance and security standpoint, we share cp0x’s concern:
DAO Loses Control
There’s no real role for the DAO in this scheme.
All decisions are approved solely by the OAT committee.
I don’t see how the DAO can influence these decisions in any meaningful way, which is why it’s so important to first know which strategies these funds will be allocated to, before transferring them. That’s a governance gap for such a large sum.
We understand that full DAO level approval for every operational step can slow execution. However, there must be a balance so the process does not become closed off or almost self referential. For this proposal to move forward in a final form, we believe it requires a more explicit description of responsibilities, oversight, and safeguards.
We remain positive about the overall direction.
Hey @krst thank you very much for the comment. The IPS document will be posted by the end of the week and will be linked under this proposal.
voting Against on this onchain vote because past yield is not enough to justify this much money being put outside the control of tokenholders and the transparency guarantees of the shared IPS framework are also not enough.
Thank you very much @Entropy for hosting the call - the presented vision for IPS is promising.
Do you have any updates on the document? During the call, you mentioned that you expected to present it to OAT for approval at the beginning of last week. If that’s the case, will the DAO be able to review the document sometime this week?
Thank you very much @Entropy for hosting the call - the presented vision for IPS is promising.
Do you have any updates on the document? During the call, you mentioned that you expected to present it to OAT for approval at the beginning of last week. If that’s the case, will the DAO be able to review the document sometime this week?
Our team weighs growth opportunities against foregone yield based on a few factors: ...
Can we expect that, for each allocation you make, we’ll be able to see your assumptions regarding these three factors? This would allow the DAO to retain and build on the learnings from those decisions.
voted Against on this offchain vote because past yield is not enough to justify this much money being put outside the control of tokenholders.
Thanks (again) for the proposal.
After my comment and the Snapshot vote, I didn’t see any response. Of course, I don’t necessarily mean a direct reply to me, I have no such expectations!! However, I carefully read through the entire discussion that followed my comment, and still couldn’t find any point that could help me address my concerns. On the contrary, I noticed even more concerns being raised by a lot of delegates, like @Euphoria’s rationale, which also increased my anxiety over this proposal.
The following reflects the views of the Lampros DAO governance team, composed of Chain_L (@Blueweb) and @Euphoria, based on our combined research, analysis, and ideation.
We are voting AGAINST this proposal in the Tally voting.
The following reflects the views of the Lampros DAO governance team, composed of Chain_L (@Blueweb) and @Euphoria, based on our combined research, analysis, and ideation.
We are voting AGAINST this proposal in the Tally voting.
We appreciate that the team published an Investment Policy Statement. The IPS adds structure and explains how the ATMC will think about benchmarks, opportunity cost, and growth versus yield decisions. Still, the IPS does not resolve the two core reasons we opposed the proposal on Snapshot: underperformance and no clear implementation plan.
The current and historic allocations have not shown that they beat simple staking once fees and costs are included. We need a clear, side-by-side net yield comparison that shows expected returns after custody fees, management fees, gas, bridge costs, and any other expenses. Without that net comparison, we cannot judge the true opportunity cost of moving 8,500 ETH.
The proposal still lacks a concrete allocation plan. We expect a detailed list of target protocols or a phased tranche plan with checkpoints and OAT sign-offs. We will not support transferring a material sum first and deciding specific allocations later.
As ITU Blockchain, we voted FOR this proposal, and we share the authors’ view that putting idle ETH to work via the ATMC is the right move now. It helps protect principal, earn conservative yield, and improve DRIP-period liquidity without selling ARB. We support a diversified approach using mature venues to reduce utilization spikes and slippage. We also encourage clear position limits, provider diversification, and simple benchmark-based reporting to keep execution disciplined.
Thank you to the delegates who took time to join the Treasury Management call earlier today. The recording of the call can be accessed here. The proposal has been updated with the following langauge:
The following reflects the views of L2BEAT’s governance team, composed of @krst and @Manugotsuka, and it’s based on their combined research, fact-checking, and ideation.
We are voting FOR.
The following reflects the views of L2BEAT’s governance team, composed of @krst and @Manugotsuka, and it’s based on their combined research, fact-checking, and ideation.
We are voting FOR.
We want to start by thanking Entropy for introducing and implementing the Investment Policy Statement (IPS). This addition marks a significant improvement in the DAO’s treasury management framework, bringing more structure, transparency, and accountability to how funds are managed.
The IPS establishes clear standards for reporting and performance evaluation that the ATMC must now fulfill. It addresses many of the concerns previously raised about the lack of visibility and reporting , providing a well-defined foundation for responsible asset management.
We also believe this IPS should become a standard requirement for any future initiative involving DAO-managed funds. A consistent framework like this will help ensure accountability, comparability, and clarity across all treasury-related programs, ultimately strengthening DAO-wide governance practices.
With IPS in place we feel comfortable with approving the transfer of DAO funds for management.
Thanks (again) for the proposal.
After my comment and the Snapshot vote, I didn’t see any response. Of course, I don’t necessarily mean a direct reply to me, I have no such expectations!! However, I carefully read through the entire discussion that followed my comment, and still couldn’t find any point that could help me address my concerns. On the contrary, I noticed even more concerns being raised by a lot of delegates, like @Euphoria’s rationale, which also increased my anxiety over this proposal.
This personally leads me not to support this proposal, and since Abstain (which was my initial choice) votes count, I’ll be voting Against in the Tally vote. It’s not that I overlook the positive aspects of the proposal, but compared to the available alternatives, I personally believe it’s not the best option.
Thank you to the delegates who took time to join the Treasury Management call earlier today. The recording of the call can be accessed here. The proposal has been updated with the following langauge:
Entropy recognizes and agrees with delegates that at certain times a deployment to support ecosystem growth should be prioritized over a pure yield strategy. Our team weighs growth opportunities against foregone yield based on a few factors:
The timeline has also been updated to reflect the delayed pushed to Tally.
The following reflects the views of GMX’s Governance Committee, and is based on the combined research, evaluation, consensus, and ideation of various committee members.
We have voted in favour of the proposal. The L2 race is becoming very competitive, and utilising the idle ETH from the Treasury is a productive use of resources.
The following reflects the views of GMX’s Governance Committee, and is based on the combined research, evaluation, consensus, and ideation of various committee members.
We have voted in favour of the proposal. The L2 race is becoming very competitive, and utilising the idle ETH from the Treasury is a productive use of resources.
There were some differences and a lack of communication during the first Treasury management proposal, but Entropy has worked on addressing those issues and is now doing a fantastic job.
GMX contributors had a conversation with the OpCo lead a few days ago, discussing how the drip incentives have proven to be beneficial for GMX and deploying the ETH within the ecosystem will provide a significant liquidity boost.
Entropy is again acknowledging its COI as a member of the ATMC. We will be voting FOR the Transfer of 8500 ETH on Tally as it is our belief that it’s of the utmost importance for the DAO to begin deploying these funds and earning yield.
gm, I voted against this proposal on snapshot echoing the concerns of L2Beat, Camelot, cp0x and other delegates.
Absolutely in favor to allocate idle funds into productive pools.
Against a DAO stripped of the ability to even review and influence strategy pre-allocation, with its role reduced to passively viewing a dashboard after allocation, in the name of efficiency.
gm, I voted against this proposal on snapshot echoing the concerns of L2Beat, Camelot, cp0x and other delegates.
Absolutely in favor to allocate idle funds into productive pools.
Against a DAO stripped of the ability to even review and influence strategy pre-allocation, with its role reduced to passively viewing a dashboard after allocation, in the name of efficiency.
We were hoping to have more clarity beforehand for this round. This doesn’t necessarily mean having a granular list at this moment, before the voting, but instead understanding what the outcome will be and what we can reasonably expect for our chains and protocols.
Voting “For”, as I believe it’s important to move idle treasury assets into a yield bearing system.
I agree with @Michigan_Blockchain that discussion should be had about a minimum threshold that automatically triggers a transfer - whether that is a ETH amount, $ amount, or recurring % of ETH.
Voting “For”, as I believe it’s important to move idle treasury assets into a yield bearing system.
I agree with @Michigan_Blockchain that discussion should be had about a minimum threshold that automatically triggers a transfer - whether that is a ETH amount, $ amount, or recurring % of ETH.
I believe earning a lower yield in exchange of supporting the ecosystem is better than just maximizing yield (i.e., buying a staking token). We’ve seen a similar idea with the stablecoin funds for example.
I also will point out that this project has the OAT, which to my understanding is reviewing & approving / rejecting investments to avoid buearocratic issues like this - DAO members wanting to re-assess the program with every vote. If there is concerns they should catch and address them with the DAO, and if the DAO is unsatisfied with that I think it’s a separate issue to discuss and put to vote.
will be moved to Tally on October 6th, with voting active from October 9th to ~23rd
maybe not a good idea just yet, since it didn't achieve the current 3% quorum of 141.5m ARB on the offchain vote, since 113.2m + 18.6m = 131.8m ARB

As a reminder there is not a quorum requirement for a Snapshot vote unless it is otherwise self-imposed by the author. Given this is a proposal that requires an onchain vote for the transfer of funds, no such requirement was outlined. While Entropy is confident that this proposal can meet the non-constitutional quorum in an onchain vote, we recognize the criticism and feedback from delegates. At this stage we feel it is best to get everyone on the same page, and will be delaying the Tally vote until after we give everyone more insight into the allocation strategy on our call next Thursday at 1 pm UTC. During this we will share the first high-level draft of our Investment Policy Statement.
Thank you for the proposal!
As always, I support solutions that increase revenue and reduce costs. However, what happens if a choice increases revenue but not in the most efficient way?
Thank you for the proposal!
As always, I support solutions that increase revenue and reduce costs. However, what happens if a choice increases revenue but not in the most efficient way?
I recognize the importance of activating idle treasury assets, and this proposal presents a solid opportunity. This opportunity is the alignment of the treasury management with ecosystem support during DRIP, generating a sustainable yield (around 2% and maybe slightly higher), and diversifying beyond ARB. The governance safeguards (OAT approval, DAO wallets excluded from rewards) also inspire confidence.
That said, two factors are keeping me from being totally in favor of this proposal:
For these reasons, I will vote ABSTAIN at this stage. If clearer allocation plans and concrete KPIs are provided, I would have no reason not to support the proposal in future rounds. Otherwise, I will unfortunately have to vote against.
While acknowledging that Entropy has a COI as a member of the ATMC, our belief that it’s of the utmost importance to get this 8,500 ETH to work immediately has led us to vote FOR on Snapshot. For the wider community, if we assume just 2% of yield on 8,500 ETH ($4,100/ETH), the DAO is foregoing almost ~$58,000 every month as these funds sit idle in the treasury. This is obviously not in the best interest of the DAO and ARB token holders.
On Arbitrum DAO, we don’t use the snapshot native quorum, we follow the Arbitrum DAO constitution definition of quorum, which in the case of non-constitutional, Arbitrum Treasury Governor onchain proposals like this one, is 3% of votable tokens casting their voting power on For + Abstain, not on Against.
https://docs.arbitrum.foundation/dao-constitution#section-2-dao-proposals-and-voting-procedures

Camelot is voting Abstain for this proposal.
We agree the treasury should be put to work: assets sitting idle are a missed opportunity for the DAO. That said, an approach that is exclusively yield-oriented is, in our view, myopic. We were one of the few recipients of the last treasury allocation, which testifies to Camelot’s key role in the ecosystem. We were the only Arbitrum exclusive protocol to receive funds. While the other choices make sense on paper, they don’t necessarily favor the specific development of the chain or the teams that have been investing more heavily, in the past or currently, in our ecosystem with a particular focus on Arbitrum.
Camelot is voting Abstain for this proposal.
We agree the treasury should be put to work: assets sitting idle are a missed opportunity for the DAO. That said, an approach that is exclusively yield-oriented is, in our view, myopic. We were one of the few recipients of the last treasury allocation, which testifies to Camelot’s key role in the ecosystem. We were the only Arbitrum exclusive protocol to receive funds. While the other choices make sense on paper, they don’t necessarily favor the specific development of the chain or the teams that have been investing more heavily, in the past or currently, in our ecosystem with a particular focus on Arbitrum.
We also see a lot of confusion in how ATMC has evolved. In the first round the process was open (protocols could submit proposals, though few were selected). The process was fairly long with an open approach to proposals in terms of submission, but not in terms of discussion; the risk parameters the commission was looking for to decide on an allocation were not clear enough, and the end result was that we only had allocations in Lido-staked ETH, AAVE, Fluid, and Camelot, with our protocol being effectively 100% focused on Arbitrum. Note that this doesn’t mean that allocations can’t go to multi-chain ones, because we do understand how, for example, AAVE is the leading lending market on our chain, to name just one of the chosen protocols. But the end result of the previous round was quite underwhelming compared to the initial set of expectations.
We were hoping to have more clarity beforehand for this round. This doesn’t necessarily mean having a granular list at this moment, before the voting, but instead understanding what the outcome will be and what we can reasonably expect for our chains and protocols.
We think the goal of the DAO with its treasury should be to produce yield and foster growth. It doesn’t necessarily have to happen in this round, but setting a clear path ahead is necessary to avoid what seems like a partial plan, with some key decisions potentially taken at the last minute.
We’ll be voting Abstain.
We’re supportive of putting idle ETH from the treasury to work, but the goals here aren’t clearly defined. Past ATMC deployments underperformed staking, and while the focus on ecosystem growth over yield maximization makes sense, the requirements for selecting Arbitrum protocols are unclear.
We’ll be voting Abstain.
We’re supportive of putting idle ETH from the treasury to work, but the goals here aren’t clearly defined. Past ATMC deployments underperformed staking, and while the focus on ecosystem growth over yield maximization makes sense, the requirements for selecting Arbitrum protocols are unclear.
We agree that deploying ETH into onchain protocols on Arbitrum can strengthen the L2, but we’re wary of effectively kingmaking certain protocols over others, as it risks distorting market dynamics and alienating projects not chosen. If yield strategies continue to trail staking, this looks more like an ecosystem subsidy than treasury management. That’s fine if framed explicitly as growth, but without guardrails, it risks encouraging projects to lobby for allocations instead of focusing on product-market fit.
A suggestion would be to split treasury deployments into two tracks: one for maximizing risk-adjusted yield (benchmarked against staking), and another for ecosystem growth (explicitly framed as strategic subsidies with transparent criteria and guardrails). This would let the DAO evaluate treasury management and growth spending more clearly.
The answer that we got, so far, is that previous iteration was more oriented toward growth of the ecosystem, and this one will be more oriented toward pure yield for the DAO.
Gauntlet supports the transfer of ETH to the ATMC, but we'd prefer to see performance benchmarks and/or strategies the DAO intends to utilize. This ETH should be used, but we'd prefer to see the DAO take a less conservative approach toward yield. Entropy appears capable; however, we'd like to see them either propose or work with external parties to propose new strategies to deliver, or at least explore, more sophisticated returns than just staking.
A number of the critiques raised here seem to focus on two points:
We believe both criticisms miss the mark and, in fact, run counter to the operational efficiency benefits that the ATMC structure was designed to deliver.
The following reflects the views of the Lampros DAO governance team, composed of Chain_L (@Blueweb) and @Euphoria, based on our combined research, analysis, and ideation.
We are voting AGAINST this proposal in the Snapshot voting.
The following reflects the views of the Lampros DAO governance team, composed of Chain_L (@Blueweb) and @Euphoria, based on our combined research, analysis, and ideation.
We are voting AGAINST this proposal in the Snapshot voting.
We support the idea of putting idle ETH to work, but we cannot approve a large transfer now because the ATMC’s recent ETH allocations have underperformed simple staking, and there is no clear implementation plan for how the 8,500 ETH will be used.
The proposal mentions a blended 30-day APY near 2.4% and roughly 43.4 ETH generated since May. For a transfer of this size, those headline numbers are not enough; we need a side-by-side comparison of net APY after fees and costs against passive staking options (wstETH / Lido / Rocket Pool) and against high-quality DVT/validator options.
Equally important, the proposal does not lay out a concrete allocation plan. Moving 8,500 ETH without clear per-protocol allocations, caps, or documented selection rationale is premature. As other delegates mentioned, it is “premature to transfer ETH before a concrete and approved plan exists,” and we agree that funds should not be transferred first and decided upon later.
If part of the goal is ecosystem support, the proposal should also include measurable KPIs for those growth allocations and a timeline to reassess impact.
For these reasons, we are voting against it at this moment.
I'm voting AGAINST
No Approved Strategy It’s premature to transfer ETH before a concrete and approved plan exists. I believe it’s not the right approach to transfer funds first and only then decide how to use them. Why not approve or at least outline the strategies beforehand, and only then move the funds?
Yield Is Low, Delay Isn't Costly Expected yield is only ≈2.4% annually. A short delay to approve a strategy won’t materially affect returns but would improve transparency.
Transfer Alone Creates No Value Moving funds from one wallet to another, without clear execution plans, does not increase efficiency or benefit the ecosystem.
DAO Loses Control There’s no real role for the DAO in this scheme. All decisions are approved solely by the OAT committee. I don’t see how the DAO can influence these decisions in any meaningful way, which is why it’s so important to first know which strategies these funds will be allocated to, before transferring them. That’s a governance gap for such a large sum.
We support this proposal. While the projected yields may fall below those of simply staking ETH, we believe this trade-off is rational and aligned with the DAO’s broader objectives. The treasury is not designed to chase the highest numerical return; it is meant to preserve capital while also acting as a catalyst for ecosystem growth. Deploying idle ETH into strategies that deepen liquidity and reduce friction for participation directly strengthens DRIP and the wider Arbitrum DeFi economy in ways that passive staking cannot.
The true value here lies in the structural impact. By directing ETH into protocols that enhance liquidity, stabilize borrowing costs, and improve capital efficiency, we create conditions for long-term resilience and growth across the ecosystem. These outcomes, such as stickier TVL, more accessible leverage, and healthier market infrastructure, represent a form of return that is not captured in APY figures but is essential to Arbitrum’s success.
The following reflects the views of L2BEAT’s governance team, composed of @kaereste, @Sinkas, and @Manugotsuka, and is based on their combined research, fact-checking, and ideation.
We voted AGAINST.
The following reflects the views of L2BEAT’s governance team, composed of @kaereste, @Sinkas, and @Manugotsuka, and is based on their combined research, fact-checking, and ideation.
We voted AGAINST.
First, we agree that treasury assets should be allocated to generate yield and/or support ecosystem growth. However, we share other delegates’ view that the strategy remains unclear and that it is not evident how Entropy plans to utilize these assets. It is also surprising to see the underperformance of the allocations justified as “ecosystem support,” especially given that the opposite was emphasized during discussions around the previous allocation.
Furthermore, we echo other delegates’ concerns about Entropy’s lack of clear communication regarding allocations and the underlying strategy —both retrospectively and for this request. Even direct requests for additional information have gone unanswered (1, 2).
This lack of communication is concerning: the DAO lacks insight into the rationale behind key decisions. Entropy is not investing private assets; it is allocating DAO assets as a service provider to the DAO. The DAO should have full visibility into decision-making and strategy - both to provide feedback and to ensure continuity if responsibility is ever transferred to another provider. Currently, the DAO observes outcomes but not the strategy that produced them; if a new manager is appointed, we risk repeating the same mistakes.
In the past, we tentatively supported several programs and requested additional details after approval, but those details never materialized. Therefore, we are voting against this proposal.
However, we want to reiterate that this is not a vote against the idea of allocating idle funds, but rather a vote against this particular implementation proposal in the current context. We are happy to revisit our position and support similar proposals once communication with the DAO improves and more details on the strategy are provided.
We are supportive of the transfer of 8,500 ETH from the treasury to the ATMC ETH strategies. Echoing @karpatkey, we would like to see transfers of this nature become a recurring activity, rather than a one-off occurence. Perhaps the ATMC could identify a transfer-triggering threshold.
That said, we would like to understand whether the ATMC has internally implemented any guardrails to manage and reduce concentration risk and/or platform/smart contract risk. If not, it may be worth introducing a soft Investment Policy Statement (IPS) to set upper-bound risk parameters for each allocation, especially as more strategies are deployed.
Overall, this is a useful initiative, however:
At the very least, this proposal should be accompanied by several options for how these funds could be allocated. Right now, there are no options provided, and simply moving money from one place to another makes little sense. It only becomes meaningful when there are concrete strategies.
I also agree with @0xDonPepe regarding yield. I believe we should not settle for the minimum available return, but aim higher while keeping risks minimal, and in addition to interest, gain equity in other projects. This is, for example, what the Sky Ecosystem does: by investing in different protocols, it secures significant profits from project tokens, and those equity stakes can always be sold later.
Thanks (again) for the proposal.
After my comment and the Snapshot vote, I didn’t see any response. Of course, I don’t necessarily mean a direct reply to me, I have no such expectations!! However, I carefully read through the entire discussion that followed my comment, and still couldn’t find any point that could help me address my concerns. On the contrary, I noticed even more concerns being raised by a lot of delegates, like @Euphoria’s rationale, which also increased my anxiety over this proposal.
This personally leads me not to support this proposal, and since Abstain (which was my initial choice) votes count, I’ll be voting Against in the Tally vote. It’s not that I overlook the positive aspects of the proposal, but compared to the available alternatives, I personally believe it’s not the best option.
Thank you to the delegates who took time to join the Treasury Management call earlier today. The recording of the call can be accessed here. The proposal has been updated with the following langauge:
Entropy recognizes and agrees with delegates that at certain times a deployment to support ecosystem growth should be prioritized over a pure yield strategy. Our team weighs growth opportunities against foregone yield based on a few factors:
The timeline has also been updated to reflect the delayed pushed to Tally.
The following reflects the views of GMX’s Governance Committee, and is based on the combined research, evaluation, consensus, and ideation of various committee members.
We have voted in favour of the proposal. The L2 race is becoming very competitive, and utilising the idle ETH from the Treasury is a productive use of resources.
The following reflects the views of GMX’s Governance Committee, and is based on the combined research, evaluation, consensus, and ideation of various committee members.
We have voted in favour of the proposal. The L2 race is becoming very competitive, and utilising the idle ETH from the Treasury is a productive use of resources.
There were some differences and a lack of communication during the first Treasury management proposal, but Entropy has worked on addressing those issues and is now doing a fantastic job.
GMX contributors had a conversation with the OpCo lead a few days ago, discussing how the drip incentives have proven to be beneficial for GMX and deploying the ETH within the ecosystem will provide a significant liquidity boost.
Entropy is again acknowledging its COI as a member of the ATMC. We will be voting FOR the Transfer of 8500 ETH on Tally as it is our belief that it’s of the utmost importance for the DAO to begin deploying these funds and earning yield.
gm, I voted against this proposal on snapshot echoing the concerns of L2Beat, Camelot, cp0x and other delegates.
Absolutely in favor to allocate idle funds into productive pools.
Against a DAO stripped of the ability to even review and influence strategy pre-allocation, with its role reduced to passively viewing a dashboard after allocation, in the name of efficiency.
gm, I voted against this proposal on snapshot echoing the concerns of L2Beat, Camelot, cp0x and other delegates.
Absolutely in favor to allocate idle funds into productive pools.
Against a DAO stripped of the ability to even review and influence strategy pre-allocation, with its role reduced to passively viewing a dashboard after allocation, in the name of efficiency.
We were hoping to have more clarity beforehand for this round. This doesn’t necessarily mean having a granular list at this moment, before the voting, but instead understanding what the outcome will be and what we can reasonably expect for our chains and protocols.
Voting “For”, as I believe it’s important to move idle treasury assets into a yield bearing system.
I agree with @Michigan_Blockchain that discussion should be had about a minimum threshold that automatically triggers a transfer - whether that is a ETH amount, $ amount, or recurring % of ETH.
Voting “For”, as I believe it’s important to move idle treasury assets into a yield bearing system.
I agree with @Michigan_Blockchain that discussion should be had about a minimum threshold that automatically triggers a transfer - whether that is a ETH amount, $ amount, or recurring % of ETH.
I believe earning a lower yield in exchange of supporting the ecosystem is better than just maximizing yield (i.e., buying a staking token). We’ve seen a similar idea with the stablecoin funds for example.
I also will point out that this project has the OAT, which to my understanding is reviewing & approving / rejecting investments to avoid buearocratic issues like this - DAO members wanting to re-assess the program with every vote. If there is concerns they should catch and address them with the DAO, and if the DAO is unsatisfied with that I think it’s a separate issue to discuss and put to vote.
will be moved to Tally on October 6th, with voting active from October 9th to ~23rd
maybe not a good idea just yet, since it didn't achieve the current 3% quorum of 141.5m ARB on the offchain vote, since 113.2m + 18.6m = 131.8m ARB

As a reminder there is not a quorum requirement for a Snapshot vote unless it is otherwise self-imposed by the author. Given this is a proposal that requires an onchain vote for the transfer of funds, no such requirement was outlined. While Entropy is confident that this proposal can meet the non-constitutional quorum in an onchain vote, we recognize the criticism and feedback from delegates. At this stage we feel it is best to get everyone on the same page, and will be delaying the Tally vote until after we give everyone more insight into the allocation strategy on our call next Thursday at 1 pm UTC. During this we will share the first high-level draft of our Investment Policy Statement.
Thank you for the proposal!
As always, I support solutions that increase revenue and reduce costs. However, what happens if a choice increases revenue but not in the most efficient way?
Thank you for the proposal!
As always, I support solutions that increase revenue and reduce costs. However, what happens if a choice increases revenue but not in the most efficient way?
I recognize the importance of activating idle treasury assets, and this proposal presents a solid opportunity. This opportunity is the alignment of the treasury management with ecosystem support during DRIP, generating a sustainable yield (around 2% and maybe slightly higher), and diversifying beyond ARB. The governance safeguards (OAT approval, DAO wallets excluded from rewards) also inspire confidence.
That said, two factors are keeping me from being totally in favor of this proposal:
For these reasons, I will vote ABSTAIN at this stage. If clearer allocation plans and concrete KPIs are provided, I would have no reason not to support the proposal in future rounds. Otherwise, I will unfortunately have to vote against.
While acknowledging that Entropy has a COI as a member of the ATMC, our belief that it’s of the utmost importance to get this 8,500 ETH to work immediately has led us to vote FOR on Snapshot. For the wider community, if we assume just 2% of yield on 8,500 ETH ($4,100/ETH), the DAO is foregoing almost ~$58,000 every month as these funds sit idle in the treasury. This is obviously not in the best interest of the DAO and ARB token holders.
On Arbitrum DAO, we don’t use the snapshot native quorum, we follow the Arbitrum DAO constitution definition of quorum, which in the case of non-constitutional, Arbitrum Treasury Governor onchain proposals like this one, is 3% of votable tokens casting their voting power on For + Abstain, not on Against.
https://docs.arbitrum.foundation/dao-constitution#section-2-dao-proposals-and-voting-procedures

Camelot is voting Abstain for this proposal.
We agree the treasury should be put to work: assets sitting idle are a missed opportunity for the DAO. That said, an approach that is exclusively yield-oriented is, in our view, myopic. We were one of the few recipients of the last treasury allocation, which testifies to Camelot’s key role in the ecosystem. We were the only Arbitrum exclusive protocol to receive funds. While the other choices make sense on paper, they don’t necessarily favor the specific development of the chain or the teams that have been investing more heavily, in the past or currently, in our ecosystem with a particular focus on Arbitrum.
Camelot is voting Abstain for this proposal.
We agree the treasury should be put to work: assets sitting idle are a missed opportunity for the DAO. That said, an approach that is exclusively yield-oriented is, in our view, myopic. We were one of the few recipients of the last treasury allocation, which testifies to Camelot’s key role in the ecosystem. We were the only Arbitrum exclusive protocol to receive funds. While the other choices make sense on paper, they don’t necessarily favor the specific development of the chain or the teams that have been investing more heavily, in the past or currently, in our ecosystem with a particular focus on Arbitrum.
We also see a lot of confusion in how ATMC has evolved. In the first round the process was open (protocols could submit proposals, though few were selected). The process was fairly long with an open approach to proposals in terms of submission, but not in terms of discussion; the risk parameters the commission was looking for to decide on an allocation were not clear enough, and the end result was that we only had allocations in Lido-staked ETH, AAVE, Fluid, and Camelot, with our protocol being effectively 100% focused on Arbitrum. Note that this doesn’t mean that allocations can’t go to multi-chain ones, because we do understand how, for example, AAVE is the leading lending market on our chain, to name just one of the chosen protocols. But the end result of the previous round was quite underwhelming compared to the initial set of expectations.
We were hoping to have more clarity beforehand for this round. This doesn’t necessarily mean having a granular list at this moment, before the voting, but instead understanding what the outcome will be and what we can reasonably expect for our chains and protocols.
We think the goal of the DAO with its treasury should be to produce yield and foster growth. It doesn’t necessarily have to happen in this round, but setting a clear path ahead is necessary to avoid what seems like a partial plan, with some key decisions potentially taken at the last minute.
We’ll be voting Abstain.
We’re supportive of putting idle ETH from the treasury to work, but the goals here aren’t clearly defined. Past ATMC deployments underperformed staking, and while the focus on ecosystem growth over yield maximization makes sense, the requirements for selecting Arbitrum protocols are unclear.
We’ll be voting Abstain.
We’re supportive of putting idle ETH from the treasury to work, but the goals here aren’t clearly defined. Past ATMC deployments underperformed staking, and while the focus on ecosystem growth over yield maximization makes sense, the requirements for selecting Arbitrum protocols are unclear.
We agree that deploying ETH into onchain protocols on Arbitrum can strengthen the L2, but we’re wary of effectively kingmaking certain protocols over others, as it risks distorting market dynamics and alienating projects not chosen. If yield strategies continue to trail staking, this looks more like an ecosystem subsidy than treasury management. That’s fine if framed explicitly as growth, but without guardrails, it risks encouraging projects to lobby for allocations instead of focusing on product-market fit.
A suggestion would be to split treasury deployments into two tracks: one for maximizing risk-adjusted yield (benchmarked against staking), and another for ecosystem growth (explicitly framed as strategic subsidies with transparent criteria and guardrails). This would let the DAO evaluate treasury management and growth spending more clearly.
The answer that we got, so far, is that previous iteration was more oriented toward growth of the ecosystem, and this one will be more oriented toward pure yield for the DAO.
Gauntlet supports the transfer of ETH to the ATMC, but we'd prefer to see performance benchmarks and/or strategies the DAO intends to utilize. This ETH should be used, but we'd prefer to see the DAO take a less conservative approach toward yield. Entropy appears capable; however, we'd like to see them either propose or work with external parties to propose new strategies to deliver, or at least explore, more sophisticated returns than just staking.
A number of the critiques raised here seem to focus on two points:
We believe both criticisms miss the mark and, in fact, run counter to the operational efficiency benefits that the ATMC structure was designed to deliver.
The following reflects the views of the Lampros DAO governance team, composed of Chain_L (@Blueweb) and @Euphoria, based on our combined research, analysis, and ideation.
We are voting AGAINST this proposal in the Snapshot voting.
The following reflects the views of the Lampros DAO governance team, composed of Chain_L (@Blueweb) and @Euphoria, based on our combined research, analysis, and ideation.
We are voting AGAINST this proposal in the Snapshot voting.
We support the idea of putting idle ETH to work, but we cannot approve a large transfer now because the ATMC’s recent ETH allocations have underperformed simple staking, and there is no clear implementation plan for how the 8,500 ETH will be used.
The proposal mentions a blended 30-day APY near 2.4% and roughly 43.4 ETH generated since May. For a transfer of this size, those headline numbers are not enough; we need a side-by-side comparison of net APY after fees and costs against passive staking options (wstETH / Lido / Rocket Pool) and against high-quality DVT/validator options.
Equally important, the proposal does not lay out a concrete allocation plan. Moving 8,500 ETH without clear per-protocol allocations, caps, or documented selection rationale is premature. As other delegates mentioned, it is “premature to transfer ETH before a concrete and approved plan exists,” and we agree that funds should not be transferred first and decided upon later.
If part of the goal is ecosystem support, the proposal should also include measurable KPIs for those growth allocations and a timeline to reassess impact.
For these reasons, we are voting against it at this moment.
I'm voting AGAINST
No Approved Strategy It’s premature to transfer ETH before a concrete and approved plan exists. I believe it’s not the right approach to transfer funds first and only then decide how to use them. Why not approve or at least outline the strategies beforehand, and only then move the funds?
Yield Is Low, Delay Isn't Costly Expected yield is only ≈2.4% annually. A short delay to approve a strategy won’t materially affect returns but would improve transparency.
Transfer Alone Creates No Value Moving funds from one wallet to another, without clear execution plans, does not increase efficiency or benefit the ecosystem.
DAO Loses Control There’s no real role for the DAO in this scheme. All decisions are approved solely by the OAT committee. I don’t see how the DAO can influence these decisions in any meaningful way, which is why it’s so important to first know which strategies these funds will be allocated to, before transferring them. That’s a governance gap for such a large sum.
We support this proposal. While the projected yields may fall below those of simply staking ETH, we believe this trade-off is rational and aligned with the DAO’s broader objectives. The treasury is not designed to chase the highest numerical return; it is meant to preserve capital while also acting as a catalyst for ecosystem growth. Deploying idle ETH into strategies that deepen liquidity and reduce friction for participation directly strengthens DRIP and the wider Arbitrum DeFi economy in ways that passive staking cannot.
The true value here lies in the structural impact. By directing ETH into protocols that enhance liquidity, stabilize borrowing costs, and improve capital efficiency, we create conditions for long-term resilience and growth across the ecosystem. These outcomes, such as stickier TVL, more accessible leverage, and healthier market infrastructure, represent a form of return that is not captured in APY figures but is essential to Arbitrum’s success.
The following reflects the views of L2BEAT’s governance team, composed of @kaereste, @Sinkas, and @Manugotsuka, and is based on their combined research, fact-checking, and ideation.
We voted AGAINST.
The following reflects the views of L2BEAT’s governance team, composed of @kaereste, @Sinkas, and @Manugotsuka, and is based on their combined research, fact-checking, and ideation.
We voted AGAINST.
First, we agree that treasury assets should be allocated to generate yield and/or support ecosystem growth. However, we share other delegates’ view that the strategy remains unclear and that it is not evident how Entropy plans to utilize these assets. It is also surprising to see the underperformance of the allocations justified as “ecosystem support,” especially given that the opposite was emphasized during discussions around the previous allocation.
Furthermore, we echo other delegates’ concerns about Entropy’s lack of clear communication regarding allocations and the underlying strategy —both retrospectively and for this request. Even direct requests for additional information have gone unanswered (1, 2).
This lack of communication is concerning: the DAO lacks insight into the rationale behind key decisions. Entropy is not investing private assets; it is allocating DAO assets as a service provider to the DAO. The DAO should have full visibility into decision-making and strategy - both to provide feedback and to ensure continuity if responsibility is ever transferred to another provider. Currently, the DAO observes outcomes but not the strategy that produced them; if a new manager is appointed, we risk repeating the same mistakes.
In the past, we tentatively supported several programs and requested additional details after approval, but those details never materialized. Therefore, we are voting against this proposal.
However, we want to reiterate that this is not a vote against the idea of allocating idle funds, but rather a vote against this particular implementation proposal in the current context. We are happy to revisit our position and support similar proposals once communication with the DAO improves and more details on the strategy are provided.
We are supportive of the transfer of 8,500 ETH from the treasury to the ATMC ETH strategies. Echoing @karpatkey, we would like to see transfers of this nature become a recurring activity, rather than a one-off occurence. Perhaps the ATMC could identify a transfer-triggering threshold.
That said, we would like to understand whether the ATMC has internally implemented any guardrails to manage and reduce concentration risk and/or platform/smart contract risk. If not, it may be worth introducing a soft Investment Policy Statement (IPS) to set upper-bound risk parameters for each allocation, especially as more strategies are deployed.
Overall, this is a useful initiative, however:
At the very least, this proposal should be accompanied by several options for how these funds could be allocated. Right now, there are no options provided, and simply moving money from one place to another makes little sense. It only becomes meaningful when there are concrete strategies.
I also agree with @0xDonPepe regarding yield. I believe we should not settle for the minimum available return, but aim higher while keeping risks minimal, and in addition to interest, gain equity in other projects. This is, for example, what the Sky Ecosystem does: by investing in different protocols, it secures significant profits from project tokens, and those equity stakes can always be sold later.
The answer that we got, so far, is that previous iteration was more oriented toward growth of the ecosystem, and this one will be more oriented toward pure yield for the DAO.
I don’t believe that’s accurate; in fact, it’s the opposite of what Entropy stated for the last round:
Our primary goal with the GM Track has been quite simple since the beginning: Earn higher yield on idle treasury ETH than market buying an ETH LST(s), while maintaining a similar risk profile. Treasury management is, in our view, a program that optimizes for stable and safe returns with ecosystem support as an added benefit.
This explanation was offered in response to complaints about the lack of Arbitrum protocols in the allocation. Accordingly, the program’s underperformance cannot be justified by an “ecosystem growth” focus.
A number of the critiques raised here seem to focus on two points:
We believe both criticisms miss the mark and, in fact, run counter to the operational efficiency benefits that the ATMC structure was designed to deliver.
First, the yield history being cited stems from allocations that were made prior to the ATMC structure. Those allocations were heavily shaped by DAO input, with delegates explicitly requiring that Entropy prioritize ecosystem growth opportunities even when those choices came at the expense of yield and purposefully designed growth. It is not accurate to retroactively hold those outcomes against the current ATMC framework, which was created precisely to remove this type of slow, political, DAO-led allocation process.
Second, on the question of “why not just stake and earn more yield,” this frames treasury management as a false binary. In practice, yield and ecosystem growth are tradeoffs, and there are many cases where growth-aligned capital deployment through Protocol-Owned Liquidity makes far more sense than either pure staking or direct grants. For example: if a major lending market upgrade or exchange partnership earn product exclusively launching with Arbitrum requires ETH liquidity directed to a market in order to close, the DAO may be better served by deploying ETH directly at a modest APR rather than issuing a grant. The opportunity cost of 1–2% foregone yield is often far smaller than the cost of an incentive program to achieve the same result.
In terms of transparency around performance we have all of the funds tagged and tracked on a dashboard accessible to anyone (see here and here), provide regular updates on open DAO calls when appropriate, and have a dedicated thread on the forum where we post monthly updates and other relevant information to treasury management. Additionally, Entropy hosts bi-weekly office hours where anyone can join to ask questions on treasury management. We spend an exuberant amount of time each month simply providing information and remaining transparent, and as mentioned already, we cannot even move any funds without approval from the DAO-elected OAT and Arbitrum Foundation (custodian). We also scheduled a call for Thursday October 9th at 9am ET. Finally, we aim to do a better job in our reporting at segregating yield focused and growth focused allocation per the suggestions of Reverie. This is a great flag and will be addressed, our reporting will include as many details around justification as possible, though note at times NDA/private deal structures prevent it.
Finally, the governance structure itself already addresses the concern that decisions could be made unilaterally. The OAT, an elected body, serves as the check and balance. Entropy proposes allocations and will at times decide that the value of growth is worth lower risk-adjusted yield; the OAT reviews, approves, or rejects them. This is the mechanism through which the DAO retains oversight without dragging every operational decision back into a forum-level RFP debate.
In short, the ATMC was designed to (i) remove inefficiency, (ii) enable responsive treasury management, and (iii) balance yield and growth in a way that grants alone cannot. To vote on this proposal without analyzing the context of why the ATMC exists in the first place does Arbitrum a disservice, and foregoing yield in hopes of higher yield is net bad for the ARB token.
We support this proposal. While the projected yields may fall below those of simply staking ETH, we believe this trade-off is rational and aligned with the DAO’s broader objectives. The treasury is not designed to chase the highest numerical return; it is meant to preserve capital while also acting as a catalyst for ecosystem growth. Deploying idle ETH into strategies that deepen liquidity and reduce friction for participation directly strengthens DRIP and the wider Arbitrum DeFi economy in ways that passive staking cannot.
The true value here lies in the structural impact. By directing ETH into protocols that enhance liquidity, stabilize borrowing costs, and improve capital efficiency, we create conditions for long-term resilience and growth across the ecosystem. These outcomes, such as stickier TVL, more accessible leverage, and healthier market infrastructure, represent a form of return that is not captured in APY figures but is essential to Arbitrum’s success.
We also view this proposal as setting a strong precedent for how the DAO manages idle assets going forward. Rather than letting capital sit unproductive or relying solely on passive strategies, we can establish a recurring practice of putting treasury resources to work in ways that balance prudence with strategic impact. Maintaining a buffer for flexibility is sensible, but treating idle ETH as an active lever for ecosystem health ensures that the treasury is continuously delivering value.
In short, we see the modest yield sacrifice as a worthwhile exchange for deeper liquidity, stronger capital efficiency, and a healthier foundation for Arbitrum DeFi over the long term.
We are supportive of the transfer of 8,500 ETH from the treasury to the ATMC ETH strategies. Echoing @karpatkey, we would like to see transfers of this nature become a recurring activity, rather than a one-off occurence. Perhaps the ATMC could identify a transfer-triggering threshold.
That said, we would like to understand whether the ATMC has internally implemented any guardrails to manage and reduce concentration risk and/or platform/smart contract risk. If not, it may be worth introducing a soft Investment Policy Statement (IPS) to set upper-bound risk parameters for each allocation, especially as more strategies are deployed.
We also see potential for the ATMC to take ownership of decisions related to token airdrops, such as the recently airdropped SYND token. Given that Syndicate operates as an Orbit chain, strategic engagement could be valuable for ecosystem growth. This may include actively staking to participate in governance and generate yield, or pursuing other approaches that strengthen alignment and create value for the DAO.
We agree with @karpatkey that these transactions should become a recurring practice. We suggest the DAO establish a threshold for the amount of capital needed on hand (stored in the treasury) and any excess funds are automatically transferred to the ATMC. ATMC funds should be divided into tranches based on risk and liquidity, allowing the DAO to access certain capital for discretionary spending.
Michigan Blockchain | Jack Verrill | TG @JackVerrill
Last time, plenty of builders reached out proposing their infra, vaults and product to put the assets at work. Most of them didn’t make it, and was later explained how the proposal goals was mostly to produce yield in a very safe and would say passive way from the DAO. I will just assume that this process won’t happen again, and we will rely on the consideration and decision of the committee.
Last time, plenty of builders reached out proposing their infra, vaults and product to put the assets at work. Most of them didn’t make it, and was later explained how the proposal goals was mostly to produce yield in a very safe and would say passive way from the DAO. I will just assume that this process won’t happen again, and we will rely on the consideration and decision of the committee.
I would personally prefer an allocation skewed toward ecosystem growth. Arbitrum is not only lending: is dexes, is automated vaults, is perps, and we we should be mindful of every aspect of it and of the key players of our chain, albeit I do understand how lending market are often time a very good primitive to start enhancing the capital available.
I did vote in favor, but my concerns did grow in the last couple of weeks.
Do we need to allocate the idle assets in the treasury? Of course. But we have to be clear on what the main purpose is.
In the last few days, delegates called for a more comprehensive call to discuss parameters such as yield, risk allocation and overarching goal of this program. The answer that we got, so far, is that previous iteration was more oriented toward growth of the ecosystem, and this one will be more oriented toward pure yield for the DAO.
I wholeheartly disagree with the statement above.
In the last season, allocation was toward AAVE, Lido Eth, Fluid, Camelot. The one from Camelot was suboptimal as allocation due to the passive nature of the deployer (the foundation) which, talking with the risk committee, would have not been able to manage the position in a more active way. The allocation in Fluid for sure helped the protocol bootstrap in Arbitrum and the Drip is continuing the job. That said, i hardly see how this could be defined as "oriented toward growth" of the chain" as others framed it.
I don't want to only point out to semantic. I think we need to be all on the same page of what
So far former two points are, in my humble opinion, not properly laid out, the latter point is just not discussed at all.
I won't campaign against the current season, is not worth it, and it does bring benefits to the DAO. Reaching sustainability with a treasury that is concentrated in mostly one coin (arb) is a good goal.
I would invite Entropy, the Foundation and the delegates to reflect on the following point tho: does moving, for example, from a 2.6% net yield to a 3.2% net yield, bring us anything meaningful beside having on 8500 ETH a further 51 ETH so a further gain of $200,000 for us? In my opinion it does not.
There is a lot of underestimation about the second order effect of making the DAO the first customers of Arbitrum protocols. Any 0.x% more yield we could get on the ethereum we have will greatly be outpaced by any positive mindshare that changes how the ecosystem is perceived by participant; and it will reflect on our treasury because this is one of the multiple reasons why the price action of Arb as a coin has been lackluster compared to any benchmark. I am perfectly aware i am mentioning a rather complex topic, arb price action, that can't be reduced to a bullet list or a few sentences; but whoever is out there talking with users, and builders, know that we do have a perception problem in our ecosystem.
With my vote in favour I hope that we do indeed put the idle assets at work to produce yield as we should, but also that we start to properly frame the intent behind our action while having a more thoughtful and omni comprehensive scenarios of the choices at our disposal and what they means not only for us as a DAO but as ecosystem.
In the end, does it matte if we become a self sustainable DAO if no one is left in our chain beside us?
We acknowledge that the current positions’ blended performance figures are below the staking return rate of simply holding wstETH. However, as detailed in the governance post defining the goals and justification for those allocations, simply staking all of our ETH and not providing or bootstrapping any liquidity to native or migrating blue-chip protocols to spur ecosystem economic growth was at odds with the intent of the deployment.
We acknowledge that the current positions’ blended performance figures are below the staking return rate of simply holding wstETH. However, as detailed in the governance post defining the goals and justification for those allocations, simply staking all of our ETH and not providing or bootstrapping any liquidity to native or migrating blue-chip protocols to spur ecosystem economic growth was at odds with the intent of the deployment.
Can you shed some light on how this works in practice? Specifically around:
For example, Fluid Lending on Arbitrum is pretty much up and to the right. Does that mean it's now graduated from needing this implicit subsidy?
Camelot is the inverse -- the TVL and volumes are flat while Uniswap and Fluid (DEX) are growing. Does that mean it's no longer worth providing the implicit subsidy since there's no noticeable impact from it beyond the forgone revenue?
In general, we would recommend governance funds avoid these types of positions. It feels unfocused and unproductive without some specific plan from the supported project. We'd much rather see, for example, targeted subsidies for those who move an LP or borrowing position from another chain than generic subsidies that benefit traders/borrowers/protocols that would have just done the same activities they're already doing.
In short, we'd like to see anything below the "risk free rate" for ETH staking be accompanied by a clear plan to alter behavior of specific users. After all, we don't need to provide subsidies to users who Arbitrum is already won -- it's the next marginal user that needs to be onboarded who should be targeted.
We voted against.
In our opinion, putting this amount of value at any risk for a meager 2.4% APY - before management expenses - isn’t justified.
Further, we question why the discussion always revolves around non-ARB assets. ARB could just as well be used to supply liquidity in DEXes and money markets to boost Arbitrum’s TVL numbers if this is the primary goal of the proposal.
We voted against.
In our opinion, putting this amount of value at any risk for a meager 2.4% APY - before management expenses - isn’t justified.
Further, we question why the discussion always revolves around non-ARB assets. ARB could just as well be used to supply liquidity in DEXes and money markets to boost Arbitrum’s TVL numbers if this is the primary goal of the proposal.
Lastly, we’re concerned about the increasing reliance on centralized teams - without proper competition in the selection process - to manage the DAO’s assets.
Conclusively, we suggest that the DAO explores a discussion to:
If this finds support, we’re happy to lead the discussion and together with the DAO, explore all options to enshrine decentralization and transparency in the DAO’s financial operations.
IMO, the core idea makes complete sense: put idle assets to work. I’d like to share a few options and suggestions for consideration, some of which I already mentioned in my comment on the DRIP recap post.
IMO, the core idea makes complete sense: put idle assets to work. I’d like to share a few options and suggestions for consideration, some of which I already mentioned in my comment on the DRIP recap post.
Given that the 8500 ETH requested represents a material portion of the non-ARB, unallocated treasury funds, capital preservation and long-term impact remain primary priorities. Future proposals could consider allocating a smaller amount of ETH to newer and novel protocols requiring bootstrapped liquidity support.
I'm voting FOR
I'm 100% supportive of putting our assets to work, and using a council makes a lot of sense as it allows flexibility to optimize in real time. Just like how Plasma had $2B on chain at launch, having the funds be strategically utilized to support the DRIP initiative is just smart, and we get yield on top of it. Who would vote against >200 extra ETH per year while making DRIP more accessible?
I'm voting FOR
I'm 100% supportive of putting our assets to work, and using a council makes a lot of sense as it allows flexibility to optimize in real time. Just like how Plasma had $2B on chain at launch, having the funds be strategically utilized to support the DRIP initiative is just smart, and we get yield on top of it. Who would vote against >200 extra ETH per year while making DRIP more accessible?
It’s like we get paid to do our own strategic defi market making.
h/t to @Entropy for another great proposal
We are supportive of this proposal to transfer the ETH accrued from Sequencer fees and Timeboost into ATMC’s treasury strategies. Right now, these assets are sitting idle, and we believe they could be put to much better use. By moving them into active management, the DAO can strengthen its long-term financial sustainability while also creating opportunities to support ecosystem growth, particularly within Arbitrum’s DeFi.
In fact, we would encourage the DAO to make this a recurring practice rather than a one-off transfer. Regularly channelling the ETH generated from Sequencer fees and Timeboost into ATMC would ensure that capital doesn’t accumulate unused and instead becomes part of a structured treasury management approach. Over time, this could both improve the DAO's yield and align our treasury strategy more closely with ecosystem development goals.
We are supportive of this proposal to transfer the ETH accrued from Sequencer fees and Timeboost into ATMC’s treasury strategies. Right now, these assets are sitting idle, and we believe they could be put to much better use. By moving them into active management, the DAO can strengthen its long-term financial sustainability while also creating opportunities to support ecosystem growth, particularly within Arbitrum’s DeFi.
In fact, we would encourage the DAO to make this a recurring practice rather than a one-off transfer. Regularly channelling the ETH generated from Sequencer fees and Timeboost into ATMC would ensure that capital doesn’t accumulate unused and instead becomes part of a structured treasury management approach. Over time, this could both improve the DAO's yield and align our treasury strategy more closely with ecosystem development goals.
The key consideration will be ensuring that any chosen strategies are transparent in their risk profile and cost structure so the DAO can make informed decisions. Overall, we think this is a positive step forward and strongly support it.
in general in favour. With one caveat. We need to set expectation properly for this round.
Last time, plenty of builders reached out proposing their infra, vaults and product to put the assets at work. Most of them didn't make it, and was later explained how the proposal goals was mostly to produce yield in a very safe and would say passive way from the DAO. I will just assume that this process won't happen again, and we will rely on the consideration and decision of the committee.
in general in favour. With one caveat. We need to set expectation properly for this round.
Last time, plenty of builders reached out proposing their infra, vaults and product to put the assets at work. Most of them didn't make it, and was later explained how the proposal goals was mostly to produce yield in a very safe and would say passive way from the DAO. I will just assume that this process won't happen again, and we will rely on the consideration and decision of the committee.
I would personally prefer an allocation skewed toward ecosystem growth. Arbitrum is not only lending: is dexes, is automated vaults, is perps, and we we should be mindful of every aspect of it and of the key players of our chain, albeit I do understand how lending market are often time a very good primitive to start enhancing the capital available.
I support activating the idle ETH, and I believe we could get the most of these ETH if ATMC were to include a DVT (Distributed Validator Technology) allocation that routes stake to home-staker clusters via Obol/SSV. DVT splits validator key duties across multiple operators, improving fault-tolerance and reducing slashing risk, while directly strengthening Ethereum’s decentralization. A practical path is either (a) a small native ATMC DVT vault or (b) using an existing venue like Mellow’s Decentralized Validator Vault with Lido + Obol + SSV, currently showing ~4.8% APR (base stETH yield plus DVT incentives), which compares favorably to the ~2.4% 30-day APY cited for current ETH strategies. This would let Arbitrum earn yield, improve network security, and support home stakers, all aligned with our ecosystem goals.
Assuming a prospective allocation of 8500 ETH and a conservative ETH-denominated yield of ~2.4% (illustrative figure based on the 30-day average annualized yield for existing ATMC strategies)
Assuming a prospective allocation of 8500 ETH and a conservative ETH-denominated yield of ~2.4% (illustrative figure based on the 30-day average annualized yield for existing ATMC strategies)
Isn't this underperforming just passively staking the ETH? Eyeballing yields from May to now, it looks like it's equal to Rocket Pool and less than Lido, neither of which require active management or movement out of the treasury.
Can we get a breakdown of the costs (inclusive of fees and operating expenses) along with risk profiles to get what appears to be an equal or lower return to just staking the ETH?
Hi this is Brook from TiD Research, and we are supportive of this proposal.
While the projected yields from deploying 8,500 ETH may appear modest compared to passive staking, we feel the lower return is reasonable given the broader ecosystem benefits — especially in connection with the ongoing DRIP program.
Hi this is Brook from TiD Research, and we are supportive of this proposal.
While the projected yields from deploying 8,500 ETH may appear modest compared to passive staking, we feel the lower return is reasonable given the broader ecosystem benefits — especially in connection with the ongoing DRIP program.
As we highlighted in our earlier comment on DRIP, the lack of sufficient swap liquidity has been the biggest blocker to TVL growth from leveraged yield-bearing stablecoin and ETH LST/LRT loops. Volatile slippage and meaningful price impact (e.g., >2% to unwind $100k positions) discourage larger users and weaken the amplifying effect of efficient capital use. With deeper liquidity, every $1 of inflow could potentially scale into $10 of TVL through loops — but this requires users to move in and out efficiently. Deploying treasury ETH into liquidity-supportive strategies directly addresses this bottleneck.
It’s also worth remembering that, as outlined in the original Treasury Management V1.2 mandate, the treasury was never designed to chase the highest possible yield. The objectives are to (1) generate low-risk yield on otherwise idle ETH and (2) spur ecosystem growth. From that perspective, even modest returns are justified if the deployment helps strengthen market structure and unlock DRIP’s full potential.
Moreover, given this is the DAO’s first tranche of funds, we really wanted to ensure the DAO starts with a really strong and stable foundation, while securing key partnerships from the very beginning. Thus, we focused on selecting extremely high quality partners with low risk strategies that allowed the DAO’s funds to maximize its reach and impact within the Arbitrum ecosystem.
We’re glad to see Entropy take into account some of the suggestions we’ve shared both on GRC and in private discussions — particularly around aligning Treasury management with DRIP by providing protocol-owned liquidity. This approach helps achieve sustainable, low-risk yield for the treasury while also improving DEX liquidity on target assets.
Given that DRIP is already underway, we believe ensuring its success is especially important at this stage. It may not be realistic for the DAO to launch another incentive program of this scale in the near future, and the timing now feels critical: both stablecoin and ETH DeFi markets are booming, and Arbitrum has a unique opportunity to capture market share. The yield difference between strategies may only be 2–3%, but the upside in TVL growth and ecosystem stickiness from a successful DRIP could be much more significant.
We believe this is less about giving up yield or losing money, but more about recognizing that sacrificing a few percentage points in yield to support DRIP and lay a solid foundation for ecosystem growth can be the right priority for the DAO. In this sense, the proposal is well-aligned with the treasury’s mandate: it preserves capital, generates sustainable ETH-denominated returns, and, importantly, helps address the liquidity constraint that currently limits DRIP’s impact.
Isn’t this underperforming just passively staking the ETH? Eyeballing yields from May to now, it looks like it’s equal to Rocket Pool and less than Lido, neither of which require active management or movement out of the treasury.
The answer that we got, so far, is that previous iteration was more oriented toward growth of the ecosystem, and this one will be more oriented toward pure yield for the DAO.
I don’t believe that’s accurate; in fact, it’s the opposite of what Entropy stated for the last round:
Our primary goal with the GM Track has been quite simple since the beginning: Earn higher yield on idle treasury ETH than market buying an ETH LST(s), while maintaining a similar risk profile. Treasury management is, in our view, a program that optimizes for stable and safe returns with ecosystem support as an added benefit.
This explanation was offered in response to complaints about the lack of Arbitrum protocols in the allocation. Accordingly, the program’s underperformance cannot be justified by an “ecosystem growth” focus.
A number of the critiques raised here seem to focus on two points:
We believe both criticisms miss the mark and, in fact, run counter to the operational efficiency benefits that the ATMC structure was designed to deliver.
First, the yield history being cited stems from allocations that were made prior to the ATMC structure. Those allocations were heavily shaped by DAO input, with delegates explicitly requiring that Entropy prioritize ecosystem growth opportunities even when those choices came at the expense of yield and purposefully designed growth. It is not accurate to retroactively hold those outcomes against the current ATMC framework, which was created precisely to remove this type of slow, political, DAO-led allocation process.
Second, on the question of “why not just stake and earn more yield,” this frames treasury management as a false binary. In practice, yield and ecosystem growth are tradeoffs, and there are many cases where growth-aligned capital deployment through Protocol-Owned Liquidity makes far more sense than either pure staking or direct grants. For example: if a major lending market upgrade or exchange partnership earn product exclusively launching with Arbitrum requires ETH liquidity directed to a market in order to close, the DAO may be better served by deploying ETH directly at a modest APR rather than issuing a grant. The opportunity cost of 1–2% foregone yield is often far smaller than the cost of an incentive program to achieve the same result.
In terms of transparency around performance we have all of the funds tagged and tracked on a dashboard accessible to anyone (see here and here), provide regular updates on open DAO calls when appropriate, and have a dedicated thread on the forum where we post monthly updates and other relevant information to treasury management. Additionally, Entropy hosts bi-weekly office hours where anyone can join to ask questions on treasury management. We spend an exuberant amount of time each month simply providing information and remaining transparent, and as mentioned already, we cannot even move any funds without approval from the DAO-elected OAT and Arbitrum Foundation (custodian). We also scheduled a call for Thursday October 9th at 9am ET. Finally, we aim to do a better job in our reporting at segregating yield focused and growth focused allocation per the suggestions of Reverie. This is a great flag and will be addressed, our reporting will include as many details around justification as possible, though note at times NDA/private deal structures prevent it.
Finally, the governance structure itself already addresses the concern that decisions could be made unilaterally. The OAT, an elected body, serves as the check and balance. Entropy proposes allocations and will at times decide that the value of growth is worth lower risk-adjusted yield; the OAT reviews, approves, or rejects them. This is the mechanism through which the DAO retains oversight without dragging every operational decision back into a forum-level RFP debate.
In short, the ATMC was designed to (i) remove inefficiency, (ii) enable responsive treasury management, and (iii) balance yield and growth in a way that grants alone cannot. To vote on this proposal without analyzing the context of why the ATMC exists in the first place does Arbitrum a disservice, and foregoing yield in hopes of higher yield is net bad for the ARB token.
We support this proposal. While the projected yields may fall below those of simply staking ETH, we believe this trade-off is rational and aligned with the DAO’s broader objectives. The treasury is not designed to chase the highest numerical return; it is meant to preserve capital while also acting as a catalyst for ecosystem growth. Deploying idle ETH into strategies that deepen liquidity and reduce friction for participation directly strengthens DRIP and the wider Arbitrum DeFi economy in ways that passive staking cannot.
The true value here lies in the structural impact. By directing ETH into protocols that enhance liquidity, stabilize borrowing costs, and improve capital efficiency, we create conditions for long-term resilience and growth across the ecosystem. These outcomes, such as stickier TVL, more accessible leverage, and healthier market infrastructure, represent a form of return that is not captured in APY figures but is essential to Arbitrum’s success.
We also view this proposal as setting a strong precedent for how the DAO manages idle assets going forward. Rather than letting capital sit unproductive or relying solely on passive strategies, we can establish a recurring practice of putting treasury resources to work in ways that balance prudence with strategic impact. Maintaining a buffer for flexibility is sensible, but treating idle ETH as an active lever for ecosystem health ensures that the treasury is continuously delivering value.
In short, we see the modest yield sacrifice as a worthwhile exchange for deeper liquidity, stronger capital efficiency, and a healthier foundation for Arbitrum DeFi over the long term.
We are supportive of the transfer of 8,500 ETH from the treasury to the ATMC ETH strategies. Echoing @karpatkey, we would like to see transfers of this nature become a recurring activity, rather than a one-off occurence. Perhaps the ATMC could identify a transfer-triggering threshold.
That said, we would like to understand whether the ATMC has internally implemented any guardrails to manage and reduce concentration risk and/or platform/smart contract risk. If not, it may be worth introducing a soft Investment Policy Statement (IPS) to set upper-bound risk parameters for each allocation, especially as more strategies are deployed.
We also see potential for the ATMC to take ownership of decisions related to token airdrops, such as the recently airdropped SYND token. Given that Syndicate operates as an Orbit chain, strategic engagement could be valuable for ecosystem growth. This may include actively staking to participate in governance and generate yield, or pursuing other approaches that strengthen alignment and create value for the DAO.
We agree with @karpatkey that these transactions should become a recurring practice. We suggest the DAO establish a threshold for the amount of capital needed on hand (stored in the treasury) and any excess funds are automatically transferred to the ATMC. ATMC funds should be divided into tranches based on risk and liquidity, allowing the DAO to access certain capital for discretionary spending.
Michigan Blockchain | Jack Verrill | TG @JackVerrill
Last time, plenty of builders reached out proposing their infra, vaults and product to put the assets at work. Most of them didn’t make it, and was later explained how the proposal goals was mostly to produce yield in a very safe and would say passive way from the DAO. I will just assume that this process won’t happen again, and we will rely on the consideration and decision of the committee.
Last time, plenty of builders reached out proposing their infra, vaults and product to put the assets at work. Most of them didn’t make it, and was later explained how the proposal goals was mostly to produce yield in a very safe and would say passive way from the DAO. I will just assume that this process won’t happen again, and we will rely on the consideration and decision of the committee.
I would personally prefer an allocation skewed toward ecosystem growth. Arbitrum is not only lending: is dexes, is automated vaults, is perps, and we we should be mindful of every aspect of it and of the key players of our chain, albeit I do understand how lending market are often time a very good primitive to start enhancing the capital available.
I did vote in favor, but my concerns did grow in the last couple of weeks.
Do we need to allocate the idle assets in the treasury? Of course. But we have to be clear on what the main purpose is.
In the last few days, delegates called for a more comprehensive call to discuss parameters such as yield, risk allocation and overarching goal of this program. The answer that we got, so far, is that previous iteration was more oriented toward growth of the ecosystem, and this one will be more oriented toward pure yield for the DAO.
I wholeheartly disagree with the statement above.
In the last season, allocation was toward AAVE, Lido Eth, Fluid, Camelot. The one from Camelot was suboptimal as allocation due to the passive nature of the deployer (the foundation) which, talking with the risk committee, would have not been able to manage the position in a more active way. The allocation in Fluid for sure helped the protocol bootstrap in Arbitrum and the Drip is continuing the job. That said, i hardly see how this could be defined as "oriented toward growth" of the chain" as others framed it.
I don't want to only point out to semantic. I think we need to be all on the same page of what
So far former two points are, in my humble opinion, not properly laid out, the latter point is just not discussed at all.
I won't campaign against the current season, is not worth it, and it does bring benefits to the DAO. Reaching sustainability with a treasury that is concentrated in mostly one coin (arb) is a good goal.
I would invite Entropy, the Foundation and the delegates to reflect on the following point tho: does moving, for example, from a 2.6% net yield to a 3.2% net yield, bring us anything meaningful beside having on 8500 ETH a further 51 ETH so a further gain of $200,000 for us? In my opinion it does not.
There is a lot of underestimation about the second order effect of making the DAO the first customers of Arbitrum protocols. Any 0.x% more yield we could get on the ethereum we have will greatly be outpaced by any positive mindshare that changes how the ecosystem is perceived by participant; and it will reflect on our treasury because this is one of the multiple reasons why the price action of Arb as a coin has been lackluster compared to any benchmark. I am perfectly aware i am mentioning a rather complex topic, arb price action, that can't be reduced to a bullet list or a few sentences; but whoever is out there talking with users, and builders, know that we do have a perception problem in our ecosystem.
With my vote in favour I hope that we do indeed put the idle assets at work to produce yield as we should, but also that we start to properly frame the intent behind our action while having a more thoughtful and omni comprehensive scenarios of the choices at our disposal and what they means not only for us as a DAO but as ecosystem.
In the end, does it matte if we become a self sustainable DAO if no one is left in our chain beside us?
We acknowledge that the current positions’ blended performance figures are below the staking return rate of simply holding wstETH. However, as detailed in the governance post defining the goals and justification for those allocations, simply staking all of our ETH and not providing or bootstrapping any liquidity to native or migrating blue-chip protocols to spur ecosystem economic growth was at odds with the intent of the deployment.
We acknowledge that the current positions’ blended performance figures are below the staking return rate of simply holding wstETH. However, as detailed in the governance post defining the goals and justification for those allocations, simply staking all of our ETH and not providing or bootstrapping any liquidity to native or migrating blue-chip protocols to spur ecosystem economic growth was at odds with the intent of the deployment.
Can you shed some light on how this works in practice? Specifically around:
For example, Fluid Lending on Arbitrum is pretty much up and to the right. Does that mean it's now graduated from needing this implicit subsidy?
Camelot is the inverse -- the TVL and volumes are flat while Uniswap and Fluid (DEX) are growing. Does that mean it's no longer worth providing the implicit subsidy since there's no noticeable impact from it beyond the forgone revenue?
In general, we would recommend governance funds avoid these types of positions. It feels unfocused and unproductive without some specific plan from the supported project. We'd much rather see, for example, targeted subsidies for those who move an LP or borrowing position from another chain than generic subsidies that benefit traders/borrowers/protocols that would have just done the same activities they're already doing.
In short, we'd like to see anything below the "risk free rate" for ETH staking be accompanied by a clear plan to alter behavior of specific users. After all, we don't need to provide subsidies to users who Arbitrum is already won -- it's the next marginal user that needs to be onboarded who should be targeted.
We voted against.
In our opinion, putting this amount of value at any risk for a meager 2.4% APY - before management expenses - isn’t justified.
Further, we question why the discussion always revolves around non-ARB assets. ARB could just as well be used to supply liquidity in DEXes and money markets to boost Arbitrum’s TVL numbers if this is the primary goal of the proposal.
We voted against.
In our opinion, putting this amount of value at any risk for a meager 2.4% APY - before management expenses - isn’t justified.
Further, we question why the discussion always revolves around non-ARB assets. ARB could just as well be used to supply liquidity in DEXes and money markets to boost Arbitrum’s TVL numbers if this is the primary goal of the proposal.
Lastly, we’re concerned about the increasing reliance on centralized teams - without proper competition in the selection process - to manage the DAO’s assets.
Conclusively, we suggest that the DAO explores a discussion to:
If this finds support, we’re happy to lead the discussion and together with the DAO, explore all options to enshrine decentralization and transparency in the DAO’s financial operations.
IMO, the core idea makes complete sense: put idle assets to work. I’d like to share a few options and suggestions for consideration, some of which I already mentioned in my comment on the DRIP recap post.
IMO, the core idea makes complete sense: put idle assets to work. I’d like to share a few options and suggestions for consideration, some of which I already mentioned in my comment on the DRIP recap post.
Given that the 8500 ETH requested represents a material portion of the non-ARB, unallocated treasury funds, capital preservation and long-term impact remain primary priorities. Future proposals could consider allocating a smaller amount of ETH to newer and novel protocols requiring bootstrapped liquidity support.
I'm voting FOR
I'm 100% supportive of putting our assets to work, and using a council makes a lot of sense as it allows flexibility to optimize in real time. Just like how Plasma had $2B on chain at launch, having the funds be strategically utilized to support the DRIP initiative is just smart, and we get yield on top of it. Who would vote against >200 extra ETH per year while making DRIP more accessible?
I'm voting FOR
I'm 100% supportive of putting our assets to work, and using a council makes a lot of sense as it allows flexibility to optimize in real time. Just like how Plasma had $2B on chain at launch, having the funds be strategically utilized to support the DRIP initiative is just smart, and we get yield on top of it. Who would vote against >200 extra ETH per year while making DRIP more accessible?
It’s like we get paid to do our own strategic defi market making.
h/t to @Entropy for another great proposal
We are supportive of this proposal to transfer the ETH accrued from Sequencer fees and Timeboost into ATMC’s treasury strategies. Right now, these assets are sitting idle, and we believe they could be put to much better use. By moving them into active management, the DAO can strengthen its long-term financial sustainability while also creating opportunities to support ecosystem growth, particularly within Arbitrum’s DeFi.
In fact, we would encourage the DAO to make this a recurring practice rather than a one-off transfer. Regularly channelling the ETH generated from Sequencer fees and Timeboost into ATMC would ensure that capital doesn’t accumulate unused and instead becomes part of a structured treasury management approach. Over time, this could both improve the DAO's yield and align our treasury strategy more closely with ecosystem development goals.
We are supportive of this proposal to transfer the ETH accrued from Sequencer fees and Timeboost into ATMC’s treasury strategies. Right now, these assets are sitting idle, and we believe they could be put to much better use. By moving them into active management, the DAO can strengthen its long-term financial sustainability while also creating opportunities to support ecosystem growth, particularly within Arbitrum’s DeFi.
In fact, we would encourage the DAO to make this a recurring practice rather than a one-off transfer. Regularly channelling the ETH generated from Sequencer fees and Timeboost into ATMC would ensure that capital doesn’t accumulate unused and instead becomes part of a structured treasury management approach. Over time, this could both improve the DAO's yield and align our treasury strategy more closely with ecosystem development goals.
The key consideration will be ensuring that any chosen strategies are transparent in their risk profile and cost structure so the DAO can make informed decisions. Overall, we think this is a positive step forward and strongly support it.
in general in favour. With one caveat. We need to set expectation properly for this round.
Last time, plenty of builders reached out proposing their infra, vaults and product to put the assets at work. Most of them didn't make it, and was later explained how the proposal goals was mostly to produce yield in a very safe and would say passive way from the DAO. I will just assume that this process won't happen again, and we will rely on the consideration and decision of the committee.
in general in favour. With one caveat. We need to set expectation properly for this round.
Last time, plenty of builders reached out proposing their infra, vaults and product to put the assets at work. Most of them didn't make it, and was later explained how the proposal goals was mostly to produce yield in a very safe and would say passive way from the DAO. I will just assume that this process won't happen again, and we will rely on the consideration and decision of the committee.
I would personally prefer an allocation skewed toward ecosystem growth. Arbitrum is not only lending: is dexes, is automated vaults, is perps, and we we should be mindful of every aspect of it and of the key players of our chain, albeit I do understand how lending market are often time a very good primitive to start enhancing the capital available.
I support activating the idle ETH, and I believe we could get the most of these ETH if ATMC were to include a DVT (Distributed Validator Technology) allocation that routes stake to home-staker clusters via Obol/SSV. DVT splits validator key duties across multiple operators, improving fault-tolerance and reducing slashing risk, while directly strengthening Ethereum’s decentralization. A practical path is either (a) a small native ATMC DVT vault or (b) using an existing venue like Mellow’s Decentralized Validator Vault with Lido + Obol + SSV, currently showing ~4.8% APR (base stETH yield plus DVT incentives), which compares favorably to the ~2.4% 30-day APY cited for current ETH strategies. This would let Arbitrum earn yield, improve network security, and support home stakers, all aligned with our ecosystem goals.
Assuming a prospective allocation of 8500 ETH and a conservative ETH-denominated yield of ~2.4% (illustrative figure based on the 30-day average annualized yield for existing ATMC strategies)
Assuming a prospective allocation of 8500 ETH and a conservative ETH-denominated yield of ~2.4% (illustrative figure based on the 30-day average annualized yield for existing ATMC strategies)
Isn't this underperforming just passively staking the ETH? Eyeballing yields from May to now, it looks like it's equal to Rocket Pool and less than Lido, neither of which require active management or movement out of the treasury.
Can we get a breakdown of the costs (inclusive of fees and operating expenses) along with risk profiles to get what appears to be an equal or lower return to just staking the ETH?
Hi this is Brook from TiD Research, and we are supportive of this proposal.
While the projected yields from deploying 8,500 ETH may appear modest compared to passive staking, we feel the lower return is reasonable given the broader ecosystem benefits — especially in connection with the ongoing DRIP program.
Hi this is Brook from TiD Research, and we are supportive of this proposal.
While the projected yields from deploying 8,500 ETH may appear modest compared to passive staking, we feel the lower return is reasonable given the broader ecosystem benefits — especially in connection with the ongoing DRIP program.
As we highlighted in our earlier comment on DRIP, the lack of sufficient swap liquidity has been the biggest blocker to TVL growth from leveraged yield-bearing stablecoin and ETH LST/LRT loops. Volatile slippage and meaningful price impact (e.g., >2% to unwind $100k positions) discourage larger users and weaken the amplifying effect of efficient capital use. With deeper liquidity, every $1 of inflow could potentially scale into $10 of TVL through loops — but this requires users to move in and out efficiently. Deploying treasury ETH into liquidity-supportive strategies directly addresses this bottleneck.
It’s also worth remembering that, as outlined in the original Treasury Management V1.2 mandate, the treasury was never designed to chase the highest possible yield. The objectives are to (1) generate low-risk yield on otherwise idle ETH and (2) spur ecosystem growth. From that perspective, even modest returns are justified if the deployment helps strengthen market structure and unlock DRIP’s full potential.
Moreover, given this is the DAO’s first tranche of funds, we really wanted to ensure the DAO starts with a really strong and stable foundation, while securing key partnerships from the very beginning. Thus, we focused on selecting extremely high quality partners with low risk strategies that allowed the DAO’s funds to maximize its reach and impact within the Arbitrum ecosystem.
We’re glad to see Entropy take into account some of the suggestions we’ve shared both on GRC and in private discussions — particularly around aligning Treasury management with DRIP by providing protocol-owned liquidity. This approach helps achieve sustainable, low-risk yield for the treasury while also improving DEX liquidity on target assets.
Given that DRIP is already underway, we believe ensuring its success is especially important at this stage. It may not be realistic for the DAO to launch another incentive program of this scale in the near future, and the timing now feels critical: both stablecoin and ETH DeFi markets are booming, and Arbitrum has a unique opportunity to capture market share. The yield difference between strategies may only be 2–3%, but the upside in TVL growth and ecosystem stickiness from a successful DRIP could be much more significant.
We believe this is less about giving up yield or losing money, but more about recognizing that sacrificing a few percentage points in yield to support DRIP and lay a solid foundation for ecosystem growth can be the right priority for the DAO. In this sense, the proposal is well-aligned with the treasury’s mandate: it preserves capital, generates sustainable ETH-denominated returns, and, importantly, helps address the liquidity constraint that currently limits DRIP’s impact.
Isn’t this underperforming just passively staking the ETH? Eyeballing yields from May to now, it looks like it’s equal to Rocket Pool and less than Lido, neither of which require active management or movement out of the treasury.
Isn’t this underperforming just passively staking the ETH? Eyeballing yields from May to now, it looks like it’s equal to Rocket Pool and less than Lido, neither of which require active management or movement out of the treasury.
Can we get a breakdown of the costs (inclusive of fees and operating expenses) along with risk profiles to get what appears to be an equal or lower return to just staking the ETH?
Performance attribution can best be explained and seen by looking at the current ETH-denominated allocations here (pictured below) and by looking at the monthly updates. All yields displayed and referenced in both are net yields, with the exception of gas and bridging costs, which at this scale are considered de minimis and excluded.

We acknowledge that the current positions’ blended performance figures are below the staking return rate of simply holding wstETH. However, as detailed in the governance post defining the goals and justification for those allocations, simply staking all of our ETH and not providing or bootstrapping any liquidity to native or migrating blue-chip protocols to spur ecosystem economic growth was at odds with the intent of the deployment.
It’s also worth noting that although some of the allocations are providing lower yield than a simple staked ETH LST strategy, this was not an unintended consequence of past allocation decisions, but expected. In the governance post regarding the deployment of these funds, we anticipated that the Fluid ETH deployment would provide “1-2% native ETH yield,” and so far, performance is in line with expectations. Fluid’s growth on Arbitrum has been impressive, and this is a key example of return on investment that is slightly less tangible when looking at treasury return figures, but highly beneficial for the broader Arbitrum DeFi ecosystem.
To answer some of the general questions raised by @Jonezee @JoJo @karpatkey @jameskbh
Isn’t this underperforming just passively staking the ETH? Eyeballing yields from May to now, it looks like it’s equal to Rocket Pool and less than Lido, neither of which require active management or movement out of the treasury.
Can we get a breakdown of the costs (inclusive of fees and operating expenses) along with risk profiles to get what appears to be an equal or lower return to just staking the ETH?
Performance attribution can best be explained and seen by looking at the current ETH-denominated allocations here (pictured below) and by looking at the monthly updates. All yields displayed and referenced in both are net yields, with the exception of gas and bridging costs, which at this scale are considered de minimis and excluded.

We acknowledge that the current positions’ blended performance figures are below the staking return rate of simply holding wstETH. However, as detailed in the governance post defining the goals and justification for those allocations, simply staking all of our ETH and not providing or bootstrapping any liquidity to native or migrating blue-chip protocols to spur ecosystem economic growth was at odds with the intent of the deployment.
It’s also worth noting that although some of the allocations are providing lower yield than a simple staked ETH LST strategy, this was not an unintended consequence of past allocation decisions, but expected. In the governance post regarding the deployment of these funds, we anticipated that the Fluid ETH deployment would provide “1-2% native ETH yield,” and so far, performance is in line with expectations. Fluid’s growth on Arbitrum has been impressive, and this is a key example of return on investment that is slightly less tangible when looking at treasury return figures, but highly beneficial for the broader Arbitrum DeFi ecosystem.
To answer some of the general questions raised by @Jonezee @JoJo @karpatkey @jameskbh