> For the complete documentation index, see [llms.txt](https://docs.inceptionlrt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inceptionlrt.com/developers/overview.md).

# Overview

This section provides a high-level overview of Inception's smart contract system. It introduces the architectural structure and roles of major components, offering a conceptual map for understanding how different modules interact.

Inception’s architecture is modular, with each contract group handling a specific piece of functionality — such as vault creation, restaking, tokenized reward flow, or configuration. This separation of concerns allows for flexibility, upgradability, and ease of auditing.

## Architecture Map

### Vaults

Vaults tokenize user deposits and route funds through strategy-specific adapters. Each vault adheres to a standard interface and interacts with:

* **Adapters**: Execute protocol-specific logic (e.g., EigenLayer)
* **Asset Handlers**: Validate supported tokens

{% content-ref url="/pages/zu0fK5KyWNPjLTcCxgO0" %}
[Vaults](/developers/modules/vaults.md)
{% endcontent-ref %}

### Restaking Pools

Restaking pools accept deposits and coordinate delegation to restaking services or validator networks. They may interact with off-chain actors through Go bindings and are intended to manage shared security participation.

{% content-ref url="/pages/hIb0LQ8EYHF0w6jrTZIg" %}
[Restaking Pools](/developers/modules/restaking-pools.md)
{% endcontent-ref %}

### Rate Providers

These contracts provide up-to-date valuation of vault tokens or restaked assets. Each rate provider is tailored to a specific asset or protocol and used for accounting and integrations.

{% content-ref url="/pages/G2B58S3d7KzIVQskPDuV" %}
[Rate Providers](/developers/modules/rate-providers.md)
{% endcontent-ref %}

### Airdrop

The airdrop contract handles permissioned token distributions. It verifies eligibility and processes claims, with configurations controlled off-chain.

{% content-ref url="/pages/3Of6XEWQVMPtAmlZ79eV" %}
[Airdrop](/developers/modules/airdrop.md)
{% endcontent-ref %}

### Bridge

The bridge module is responsible for coordinating multi-chain deployment. It includes network-specific configurations and tracks proxy-based contract deployments. It does not include its own on-chain bridging mechanism.

{% content-ref url="/pages/bIrQBNYhtlvvLgpg6srG" %}
[Bridge](/developers/modules/bridge.md)
{% endcontent-ref %}

### Reward Wrappers *(not isolated)*

Reward logic appears embedded within vault adapters and restaking implementations. There is no standalone reward-wrapper module, but reward flows are handled via adapter patterns and possibly within integrations.

### Notes

* All contracts are written in Solidity and deployed using Hardhat with OpenZeppelin proxies.
* Off-chain coordination (e.g., validator actions) is supported via generated Go bindings.
* Each module is independently upgradable and auditable.

Refer to the individual module pages for detailed behavioral documentation and integration notes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.inceptionlrt.com/developers/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.