What Lubin and Chalom’s Ether DAT case means for corporate treasury

On February 12, 2026, SharpLink executives Joe Lubin and Joseph Chalom argued that ether digital asset treasury, or DAT, strategies should be judged by what ETH can do onchain, not only by its recent price action. The point matters now because treasury teams are still deciding whether crypto exposure belongs in a balance sheet as a passive reserve or as a more active operating asset.

What was the core argument?

Lubin and Chalom’s case was that ether can be treated as productive infrastructure. In the reporting from CoinDesk and in the event video, they pointed to staking and broader Ethereum use cases such as stablecoins and tokenization as reasons ETH may have a different role from a simple speculative holding.

That is a meaningful distinction. A treasury asset that can be used to support network activity, generate yield, or sit inside a broader onchain workflow has a different risk and return profile from one that is held only for price appreciation. It also creates a different operating burden, because teams need to think about custody, liquidity, lockup periods, and governance rather than just market timing.

Why does this matter for treasury operators?

The practical question is not whether ETH is strong or weak on a given week. It is whether a company can tolerate the volatility, operational complexity, and accounting treatment that come with a productive crypto treasury. A staking-based approach may improve capital efficiency, but it can also reduce flexibility if assets are locked or if policy changes force a quick exit.

That is why the SharpLink discussion is relevant beyond one company. It reflects a broader corporate finance debate about whether digital assets should be held as static reserves or used more actively. For finance teams, the decision should start with three checks: expected holding period, liquidity needs, and the internal controls required to manage onchain assets safely.

What are the main risks and limitations?

The main limitation is that yield does not remove market risk. Even if ETH generates staking rewards, the underlying asset can still decline sharply, which can overwhelm income from the strategy. There is also execution risk if a company lacks operational experience with wallets, validators, custody providers, or treasury policy design.

Another limitation is that the argument is still a thesis, not a settled standard. The February 2026 panel was a reported discussion, not a regulatory ruling or a formal corporate finance rulebook. That means operators should treat it as a lens for evaluation, not as a template to copy blindly.

What should teams do next?

Companies evaluating ether DATs should model downside scenarios first, then test whether any staking or onchain yield meaningfully improves the treasury case after fees, lockups, and controls. They should also define who can approve movements, how exposure is reported internally, and what triggers a rebalance or exit.

For teams that want to move beyond theory, the operational question is how to connect treasury policy to payments and settlement workflows without adding unnecessary risk. That is where a payments partner such as Radom can be relevant if a business is already handling crypto receipts or payouts, but the treasury case still needs to stand on its own.

In short, Lubin and Chalom’s argument is not that every company should buy ETH. It is that corporate finance may need a new framework for judging whether digital assets can be productive, not just passively held.