# \[Discussion\] Treasury Reporting Standards & MET Treasury Framework

**URL:** <https://discourse.metronome.io/t/discussion-treasury-reporting-standards-met-treasury-framework/66>\
**Category:** General\
**Created:** [July 2, 2026, 9:25am UTC](https://discourse.metronome.io/t/discussion-treasury-reporting-standards-met-treasury-framework/66 "2026-07-02T09:25:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![DomCrypto](https://avatars.discourse-cdn.com/v4/letter/d/bc8723/32.png) [@DomCrypto](https://discourse.metronome.io/u/DomCrypto)\
**Post date:** [July 2, 2026, 9:25am UTC](https://discourse.metronome.io/t/discussion-treasury-reporting-standards-met-treasury-framework/66/1 "2026-07-02T09:25:34Z")

</div>

## **Summary**

Formalize treasury reporting standards and establish governance guidelines surrounding treasury-held MET.

## **Background**

Over the past year, Metronome has significantly improved transparency across protocol operations.

Community members can currently track protocol revenue, incentive spend, and buybacks through [DefiLlama dashboard](https://enterprise.defillama.com/odyssey-ecosystem), while treasury assets and allocations are publicly visible through [Octav](https://metronome.octav.fi/app/Treasury) and [DeBank](https://debank.com/bundles/213082/accounts). In addition, monthly reports provide recurring updates regarding protocol performance and development.

While these tools provide substantial visibility into protocol operations, there is currently no formal framework describing treasury classifications or the intended use of treasury-held MET.

## **Abstract**

This proposal formalizes DefiLlama and Octav/DeBank as the primary sources of protocol reporting and treasury transparency.

Metronome should continue monthly reporting and maintain documentation describing the purpose of major treasury wallets and treasury categories where applicable.

The proposal also establishes governance guidance regarding treasury-held MET.

## **Treasury-Held MET**

The Metronome treasury currently holds a substantial portion of the MET supply. At this time, there are no plans to circulate treasury-held MET besides MET incentives stated in MIP-33.

Treasury-held MET should be viewed as a strategic reserve asset and should remain non-circulating unless its deployment serves a clear purpose that benefits the protocol. Acceptable uses of treasury-held MET may include:

- Liquidity programs and market development initiatives, where MET substitutes USDC spend and only under the condition that MET trades at a surplus to its treasury backing. For example, this could include directing some MET toward liquidity incentives on selected markets where doing so is more capital efficient than spending stablecoins.

- Strategic investments, treasury swaps, OTC agreements, and ecosystem partnerships.

- Emergency backstopping of protocol operations during catastrophic events.

- Temporary treasury operations, including cross-chain liquidity management, where an equivalent amount of MET is expected to return to treasury reserves over time.

## **Specification**

- Formalize DefiLlama and Octav/DeBank as primary treasury reporting tools.

- Continue monthly reporting and treasury updates.

- Maintain documentation regarding treasury wallet classifications and treasury purpose.

- Establish governance guidance regarding acceptable uses of treasury-held MET.

- Recognize treasury-held MET as a strategic reserve asset that should remain non-circulating absent a clear protocol benefit.

---

<div class="post-metadata">

**Author:** ![AnonTrader](https://avatars.discourse-cdn.com/v4/letter/a/cab0a1/32.png) [@AnonTrader](https://discourse.metronome.io/u/AnonTrader)\
**Post date:** [July 6, 2026, 5:04pm UTC](https://discourse.metronome.io/t/discussion-treasury-reporting-standards-met-treasury-framework/66/2 "2026-07-06T17:04:58Z")

</div>

I agree with this MIP. No notes.

---

<div class="post-metadata">

**Author:** ![Mudokan](https://avatars.discourse-cdn.com/v4/letter/m/b487fb/32.png) [@Mudokan](https://discourse.metronome.io/u/Mudokan)\
**Post date:** [July 6, 2026, 8:51pm UTC](https://discourse.metronome.io/t/discussion-treasury-reporting-standards-met-treasury-framework/66/3 "2026-07-06T20:51:21Z")

</div>

No changes/additions

I support it as written.

---

<div class="post-metadata">

**Author:** ![beargrassbullllama](https://avatars.discourse-cdn.com/v4/letter/b/d78d45/32.png) [@beargrassbullllama](https://discourse.metronome.io/u/beargrassbullllama)\
**Post date:** [July 6, 2026, 11:21pm UTC](https://discourse.metronome.io/t/discussion-treasury-reporting-standards-met-treasury-framework/66/4 "2026-07-06T23:21:36Z")

</div>

I support this MIP as written!

---

<div class="post-metadata">

**Author:** ![SubZer0](https://avatars.discourse-cdn.com/v4/letter/s/54ee81/32.png) [@SubZer0](https://discourse.metronome.io/u/SubZer0)\
**Post date:** [July 9, 2026, 12:17am UTC](https://discourse.metronome.io/t/discussion-treasury-reporting-standards-met-treasury-framework/66/5 "2026-07-09T00:17:32Z")

</div>

I support this MIP as it allows for better accounting and clarity around all metrics associated with the Metronome protocol.