# GVNR Overview

## <mark style="color:orange;">Token Orientated</mark>

When building out this model, consideration has been taken to make sure that GVNR has consistent and predictable revenue from a multifaceted approach to token valuation.

***

<figure><img src="/files/umnr6rkZElLMNdfLGya4" alt=""><figcaption></figcaption></figure>

### GVNR Token Transaction Fees | <mark style="color:orange;">Frictionless Adoption</mark> <a href="#annual-chain-contributions" id="annual-chain-contributions"></a>

1. Actors do not need to buy the $GVNR Token as gas will be paid in native tokens depending on chain being used.
2. Extracted fees flow to the GVNR furnace, the protocols automated buy and burn mechanism.

***

### Annual Chain Contributions | <mark style="color:orange;">Consistent Revenue</mark> <a href="#annual-chain-contributions" id="annual-chain-contributions"></a>

1. Annually recurring chain contributions are required from chain foundations.
2. Transactional activity can reduce or fully offset this fee dependant on activity on chain.
3. Participating Foundations can speed up connectivity through a fast track fee, or build their own permissionless connection to GVNR.

***

### Deflationary Tokenomics | <mark style="color:orange;">Organic Reduction in $GVNR</mark> <a href="#deflationary-tokenomics" id="deflationary-tokenomics"></a>

1. Tokenomics driven by the protocols dynamic deflationary buy and burn mechanism.  This moves value extracted through fee capture into the entire token ecosystem.
2. A scaling percentage of fees will be dedicated to price agnostically buying and burning of $GVNR automatically by the protocol.


---

# 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://docs.gvnr.xyz/docs/gvnr-overview.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.