# Thetanuts V4

<figure><img src="https://2359591010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPIuR1X1Xz3wXFEgMDgY9%2Fuploads%2FH62zqvy3aWoNN5WjYhz8%2Fv4%20Banner2.png?alt=media&#x26;token=dd517fe6-351b-46a0-b2b9-d451eb0ef6f5" alt=""><figcaption></figcaption></figure>

### Overview

Thetanuts has always pushed the boundaries of what DeFi-native options can be. **V4 is a new foundation**: a builder-first, RFQ-powered options infrastructure that supports event-driven structures, custom payoffs, and institutional liquidity—while preserving a smooth user experience.

**What V4 unlocks**

* **Greater flexibility** — tailored quotes for dynamic, event-driven structures.
* **Better execution** — tighter spreads and more competitive pricing via open quoting.
* **Deeper liquidity** — sourced directly from market participants.

> V4 is **chain-agnostic**, **trustless**, and **composable**—built to deploy where the best communities and infrastructure exist.

***

### RFQ System

At the heart of V4 is a **Request-for-Quote (RFQ) engine**. Instead of relying on AMMs, liquidity providers deliver **direct quotes** that apps can request and users can execute on-chain.

**Why RFQ**

* **Customized structures** → more predictable outcomes and reduced slippage.
* **Open competition** → market-driven pricing, tighter spreads.
* **Liquidity depth** → direct access to active market participants.

**Seeding liquidity (the flywheel)**

* **Early support** — select builder teams are already testing V4 and simulating real-world environments.
* **Scaling up** — as the quoting environment matures, we connect app teams and early LPs with professional market makers, deepening liquidity and tightening spreads.
* **Future breadth** — broader support for additional structures (e.g., American options) as flow grows.

> The RFQ engine strengthens as more apps, makers, and strategies plug in—forming a **self-reinforcing liquidity flywheel**.

***

### Architecture Summary

**Chain-agnostic by design**

* Deployable across Ethereum L2s, modular stacks, and emerging high-performance chains.
* Prioritizes **low transaction costs**, **fast settlement**, and **vibrant DeFi ecosystems** for composability.

**Trustless & decentralized**

* **All settlements on-chain**, verifiable by anyone.
* **Quotes & execution via smart contracts**, minimizing intermediaries.
* **Fully collateralized** interactions: users keep control of funds and positions while trades are honored by counterparties.

**Built for builders**

* Clean **RFQ rails** that power custom strategies without rebuilding an options desk.
* Composable primitives that downstream apps can integrate through SDKs/APIs.
* A roadmap that expands instruments, oracles, and settlement adapters as the ecosystem grows.

***

### Vision

We’re building the **Theta System**—a modular options ecosystem where every product shares the same RFQ liquidity backbone and composes with the rest.

**What the Theta System enables**

* **Structured vaults**, **event-driven options**, **custom RFQ strategies**, and **institutional access points** that connect seamlessly.
* **Builder extensibility** — plug into RFQ to launch specialized vaults or trading products.
* **Unified flow for makers** — market makers tap a consolidated stream of options demand across products.

**The flywheel**

> More products → More flow → Deeper liquidity → Better pricing → Even more products.

***

You can access our website at: <http://thetanuts.finance/>


---

# 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.thetanuts.finance/thetanuts-v4.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.
