# inTokens

**inTokens are modular, composable vault tokens that unify DeFi’s most competitive, sustainable, and risk-adjusted reward opportunities into a single, ERC-standardized structure.**

They are built using ERC-4626 (standardized vaults) and optionally support ERC-7540 (asynchronous operations), allowing for powerful integrations, yield abstraction, and seamless interoperability across protocols.

Each Intoken bundles one or more layers of curated exposure:

| **inToken0: Multi-Curated Vault**    | Vaults built by industry-grade curators, sourced from top DeFi ecosystems.     |
| ------------------------------------ | ------------------------------------------------------------------------------ |
| **inToken: Shared Security Rewards** | Opt-in composability with shared security layers like EigenLayer or Symbiotic. |
| **inToken+: Strategy Enhancements**  | Additional DeFi strategies like LPs, looping, or yield tokenization on top.    |

Every inToken is issued by an independent curator, not by Inception itself, using a permissionless infrastructure powered by Inception’s vault factory, routing, and liquidity tooling.

***

## inToken0&#x20;

→ ***Multi-Curated Vault Access***

The **base layer inToken0** gives users access to curated vaults sourced from multiple protocols, all bundled into a single solution.

**▸ What it includes:**

* Handpicked vaults from curators operating on Morpho, Midas, Gearbox, etc.
* Allocations can be built around themes: RWAs, Stablecoin lending, Solana Staking, etc.
* Risk diversification by design, no single point of failure in vault logic.

**▸ What it&#x20;*****doesn't*****&#x20;include:**

* No exposure to shared security network rewards
* No active DeFi execution (looping, LPing, etc.)

*Use case:* A user wants simple, multi-source exposure to curated DeFi rewards with strong risk-adjusted returns, without shared security mechanics or strategic overlays

***

## inToken

→ ***Shared Security Composability***

The **inToken+** introduces a second layer of rewards: **shared security networks**.

These are curated vaults that also participate in economic security provisioning for third-party infrastructures like **EigenLayer** or **Symbiotic,** meaning the user gets additional rewards from being indirectly involved in securing on-chain infrastructure (e.g., DA layers, oracles, sequencers) on top of the underlying rewards that inToken0 (layer 1) have to offer.

**▸ What it includes:**

* All Layer 1 vault exposure (curator-selected vaults)
  * Shared security rewards from protocols leveraging Inception's collateral

**▸What it&#x20;*****doesn't*****&#x20;include:**

* Active DeFi strategy overlays (like LPing, looping, etc.)

*Use case*: A user who seeks risk-adjusted rewards but doesn’t want to get locked into shared security's native friction (e.g., 7–21 day unbonding periods) and wants a composable position with built-in abstraction and opt-out liquidity through Inception’s *Flash Unstake module*.

***

## inToken+

→ ***Full Stack Strategy Execution***

The most rewarding exposed layer is **inToken+,** which bundles curated vaults, shared security rewards, and **DeFi-native strategy overlays,** built directly into the vault logic.

These strategies can include:

* Looping (through lending markets)
* Liquidity provisioning (through DEXs)
* Yield tokenization or fixed-term strategies
* Delta-neutral or basis trade setups

**What it includes:**

* Full Layer 1: multi-curated vaults
* Full Layer 2: shared security rewards
* Execution of DeFi-native strategies

**What it&#x20;*****doesn't*****&#x20;include:**

* Manual complexity, all logic abstracted into a single token with transparent mechanics

*Use case:* A DeFi user or institution that wants exposure to advanced, high-performing strategies that are otherwise difficult to manage manually, all through a single liquid token.


---

# 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.inceptionlrt.com/primitives/intokens.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.
