# NOVA Monetary Dashboard

### I. Supply Statement (Like Base Money)

**Current Circulating Supply**\
**Total Issued Since Genesis**\
**Total Permanently Burned**\
**Net Supply Change (30D)**

Then a simple equation shown clearly:

> Net Supply = Emissions − Buybacks & Burns

You want this visually clean. Almost boring.\
Institutional.

***

### II. Issuance (Expansion Side)

**Daily Scheduled Emission**

* Vault incentives
* Borrow incentives
* Liquidity incentives

**Emission Velocity (30D avg)**\
**Projected Annualized Issuance**

This is your “monetary expansion” side of the ledger.

***

### III. Contraction (Buyback & Burn)

**Protocol Revenue This Period**

* Interest spread
* Fees
* Liquidation revenue
* Other mechanical flows

**Market Buybacks Executed**\
**Tokens Permanently Removed**

Then:

**Burn Velocity (30D avg)**\
**Annualized Burn Rate**

This is your “open market operations.”

***

### IV. Net Monetary Position

A single line that matters:

> Net Supply Change (Last 30 Days)

Green if negative.\
Neutral if flat.\
Red if inflationary.

Also:

**Deflation Ratio = Burn ÷ Emission**

If > 1 → structurally compressive\
If < 1 → expansionary phase

That one ratio will become the headline metric.

***

### V. Balance Sheet Framing

You could literally split screen:

#### Assets (Protocol Activity)

* Total Deposits
* Total Borrowed
* Liquidity Depth
* Fee Revenue

#### Liabilities (Token Supply)

* Circulating NOVA
* Emitted This Period
* Burned This Period

That’s powerful.

You’re saying:

> Token supply is a function of system usage.

That’s monetary engineering, not farming.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://trader-li.gitbook.io/horizon-protocol/transparency/nova-monetary-dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.