# Service Wind‑down Overview Inception is in the process of winding down all products and services. As part of this process, users will no longer be able to open to deposit additional assets into Inception smart contracts through our UIs. Existing users will retain the ability to withdraw their assets from the protocol smart contracts for a defined period from the UI. The primary objective of this wind‑down is to give every user a clear, transparent, and safe path to exit the protocol while contracts remain operational onchain. After the withdrawal period ends, the user interface and supporting infrastructure for Inception may be shutdown, but the **underlying smart contracts will continue to exist** on each networks and can be accessed via block explorer such as Etherscan. *** ### Key dates and what changes * **New deposits disabled:** All new deposits and minting of new inTokens is now disabled from the UI. * **Withdrawal‑only period:** Users can withdraw their assets from Inception smart contracts using compatible wallets and Etherscan. * **Front‑end shutdown:** On `December 31, 2025`, the Inception application and website may be taken offline. After this point, withdrawals will only be possible by interacting directly with the smart contracts onchain. *Transactions are irreversible and require network gas fees paid in ETH.* *** ### What you need before withdrawing Before starting the withdrawal process, make sure you have: * The wallet that currently holds your **inTokens** or **deposit positions** (e.g., MetaMask, Ledger, etc.). * A small amount of ETH in the same wallet to pay **network gas fees for contract interactions**. * The relevant **Inception smart contract addresses** (provided in the sections below). If you use a hardware wallet, ensure it is connected and unlocked before interacting with Etherscan. Always verify URLs manually and avoid clicking unknown links. *** ### How to withdraw your assets All withdrawals must be executed directly through the vault smart contracts on Ethereum using Etherscan. Follow these steps carefully to withdraw your deposited assets. ### Step 1: Find your vault contract address Locate the vault contract for the specific asset you deposited. Each asset type has its own dedicated vault: **Available vaults:** {% content-ref url="/pages/aRgXZsztDuLqEZJEPP1b" %} [Addresses](/developers/addresses) {% endcontent-ref %} ### Step 2: Open the vault contract on Etherscan 1. Go to `https://etherscan.io` 2. Paste the vault address from Step 1 into the search bar 3. Press Enter to open the contract page 4. Verify the address matches exactly with the one listed above ### Step 3: Connect your wallet 1. On the contract page, click the **"Contract"** tab 2. Select **"Write Contract"** (not "Read Contract") 3. Click **"Connect to Web3"** 4. Choose your wallet provider (MetaMask, WalletConnect, etc.) 5. Approve the connection request in your wallet popup Ensure you're connecting with the same wallet that holds your deposited assets. ### Step 4: Execute flashWithdraw function 1. In the "Write Contract" section, scroll down to find the **`flashWithdraw`** function 2. Click to expand the function 3. You will see an input field labeled **`amount`** (or similar) 4. Enter the amount you want to withdraw in the token's smallest unit: * For most tokens, multiply your desired amount by `1000000000000000000` (18 zeros) * Example: To withdraw 1.5 tokens, enter `1500000000000000000` * To withdraw your entire balance, check your balance first using the "Read Contract" tab 5. Click the **"Write"** button 6. Review the transaction details in your wallet popup carefully 7. Check the gas fee—adjust if needed based on network congestion 8. Click **"Confirm"** in your wallet to submit the transaction ### Step 5: Wait for transaction confirmation 1. After submitting, Etherscan will display a transaction hash link 2. Click the link to monitor the transaction status 3. Wait for the transaction to be confirmed (typically 15-60 seconds) 4. Do not close your browser or disconnect your wallet until confirmation appears ### Step 6: Verify your withdrawal 1. Once confirmed, check your wallet balance for the withdrawn asset 2. The asset should appear in your wallet within a few minutes 3. If you don't see the token, you may need to manually add the token contract address to your wallet's token list **Important notes:** * Each withdrawal requires a network gas fee paid—ensure your wallet has enough balance to cover gas * Transactions are final and cannot be reversed once confirmed * Always double-check the amount before confirming the transaction *** ### Calculating withdrawal amounts To avoid errors when entering amounts in the `flashWithdraw` function: **For 18-decimal tokens (most ERC20 tokens):** * 1 token = `1000000000000000000` (1 followed by 18 zeros) * 0.5 tokens = `500000000000000000` * 10 tokens = `10000000000000000000` **Online converter tools:** * Use `https://eth-converter.com/` to convert between units * Enter your amount in "Ether" and copy the "Wei" value to use in the function *** ### Troubleshooting common issues **"Transaction failed" or "Execution reverted":** * You may not have sufficient balance in the vault * Gas limit might be too low—try increasing it manually * The vault might have insufficient liquidity at this moment—try a smaller amount or wait **"Insufficient funds for gas":** * Add more ETH to your wallet to cover transaction fees * Current gas prices can be checked at `https://etherscan.io/gastracker` **"Wrong network" error:** * Ensure your wallet is connected to Ethereum Mainnet, not a testnet or other chain **Cannot find `flashWithdraw` function:** * Make sure you're on the "Write Contract" tab, not "Read Contract" * Verify you've connected your wallet—the functions only appear after connection * Confirm you're viewing the correct vault contract address **Asset not showing in wallet after withdrawal:** * Check the transaction on Etherscan to confirm it succeeded * Manually add the token by importing its contract address into your wallet * Some wallets take a few minutes to refresh balances # Overview **Inception is the unifying access layer for curated DeFi.** Inception aggregates the best structured vaults, curated solutions, and shared security opportunities into a single composable layer. By abstracting fragmentation and liquidity friction, Inception gives users access to sustainable, multi-source rewards across multiple ecosystems, all through modular tokens called **inTokens**. ### Get to know Inception {% content-ref url="/pages/iMlkESWiPvOygNc1zdK4" %} [inTokens](/primitives/intokens) {% endcontent-ref %} {% content-ref url="/pages/WogwP7tGyFSjWOATByfv" %} [Concepts](/introduction/concepts) {% endcontent-ref %} {% content-ref url="/pages/aRgXZsztDuLqEZJEPP1b" %} [Addresses](/developers/addresses) {% endcontent-ref %} {% content-ref url="/pages/utSyXi9f4Qi1C0hGNZpK" %} [Audit Reports ](/resources/audit-reports) {% endcontent-ref %} ### Get Started with Inception {% embed url="" %} dApp {% endembed %} # Concepts | **Curated Vault** | A DeFi product built by an independent curator, not a protocol core team, on top of an open and permissionless infrastructure. | | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Curator** | An individual or entity that builds, maintains, and handles DeFi vaults. Curators are responsible for allocation design, risk management, and performance upkeep. | | **Structured Vault** | A reward-bearing tokenized position composed of multiple underlying allocations, often blending DeFi-native and institutional assets. | | **Shared Security** | A DeFi primitive that allows multiple protocols to bootstrap security mechanics (often via restaking) from a common pool of stakers. This enables additional yield for securing infrastructure. | | **Restaking** | A mechanism that lets staked assets be repurposed and help secure additional protocols or services. | | **Composability** | The ability for DeFi building blocks to work together seamlessly. inTokens enable this by bundling multiple yield streams into a standard ERC-4626 format. | | **Flash-&-Stake** | A built-in Inception feature that enables instant liquidity exit from inToken positions, bypassing unbonding periods via a shared liquidity pool. | | **inToken** | A structured ERC-4626 vault token issued via Inception that can represent multiple reward layers: curated vaults, shared security, and other DeFi strategies. | # Context DeFi has undergone a structural evolution over the past few years, moving from **monolithic protocols** to **modular, curator-driven ecosystems**. In the early stages of DeFi (2018–2021), protocols like *Aave, Compound,* and *Lido* dominated the landscape. Each protocol was vertically integrated: the same team designed the product, operated the infrastructure, managed risk, and determined how rewards were distributed. The role of the *curator* — someone who builds and manages financial products — was played entirely by the protocol itself. As a result, user experience was predictable but limited. Strategies were rigid, and reward opportunities were bound to the design choices of a single team. From 2022 onward, this started to change. New protocols such as *Morpho, EigenLayer,* and *Symbiotic* introduced permissionless infrastructure layers, allowing *independent curators* to build and deploy their own vaults and strategies on top of shared infrastructure.

The Evolution of DeFi

This shift gave rise to what we now call **curator-led DeFi**: an ecosystem where third-party experts design reward-bearing products with diverse risk-return characteristics. These curators: * Choose assets and risk parameters * Combine reward sources across protocols * Manage vault upgrades and performance * Create structured products, including those backed by real-world assets As this design space expands, so does the potential for **sustainable, diversified, and composable rewards**. But it also introduces significant complexity — and that’s where Inception steps in. # Problem As institutional and retail capital moves on-chain, a new set of challenges emerges. The growth of curated vaults has made opportunity design more dynamic, but accessing and composing these opportunities has become **operationally difficult** and **technically fragmented**. Let’s break it down: ### **▸ Fragmentation across ecosystems** Each curator operates in isolation. Vaults built on Morpho are siloed from those on Symbiotic, EigenLayer, or Gearbox. Even when strategies offer similar exposure (e.g., stETH restaking), they live in separate systems with different wrappers, constraints, and interfaces. This fragmentation makes it difficult for users to build coherent portfolios or understand comparative risk. ### **▸ Limited composability** The diversity of vault structures: fixed income, restaking, LPs, or tokenized credit, creates reward streams that are difficult to unify. Protocols lack standardized interfaces. Positions can’t be composed into a single ERC-20 or ERC-4626. This limits users’ ability to **stack multiple sources of reward** into one liquid, capital-efficient solution. ### **▸ Liquidity constraints** While shared security unlocks new rewards, it introduces friction: * Unbonding periods of 7–21 days * Lockup mechanics that delay liquidity * Exposure to infrastructure-level risk This reduces capital mobility, particularly painful for approaches that require flexibility, such as liquidity provisioning or looping strategies. ### **▸ Operational complexity** Today’s curated DeFi requires: * Managing multiple vault interfaces and strategies * Navigating custom wrappers and unstaking logic * Tracking asynchronous rewards and emission schedules * Assessing risk and decentralization parameters For sophisticated institutions, this means more overhead. For retail users, it creates a barrier to entry. # Why now? There’s a clear inflection point in the evolution of on-chain capital markets. Three structural forces are converging, creating the need for infrastructure like Inception: ### **1. Curator-led Environments are Growing** A few years ago, less than 1% of DeFi’s TVL flowed through curator-led vaults. Today, over **21%** of total TVL is allocated to protocols where third parties manage vault design and rewards. Protocols like *Morpho, Symbiotic, Spectra*, and *EigenLayer* are not competing for TVL as vertically integrated products, they’re acting as **permissionless vault frameworks**. As more capital flows into these ecosystems, users and institutions need a way to access and compose exposure across them without getting trapped in siloed experiences.

TVL Growth of Curated DeFi

### **2. Institutional Capital is Being Onboarded Onchain** In 2020, institutional involvement in DeFi meant buying into blue-chip vaults or LP positions.\ By 2024, institutions are **issuing on-chain products themselves**: * Tokenized T-bills * Structured credit * Custom basis trade vaults * Permissioned staking pools This means institutions are playing the role of curators, and they need infrastructure that supports **design, issuance, and liquidity abstraction** at scale.

Total amount of RWAs Onchain

### **3. RWAs and DeFi-native rewards are merging** Today’s highest-performing vaults combine real-world and on-chain components. A single product might include: * A tokenized short-term bond (RWA) * A restaking wrapper on a shared security infrastructure * A looping mechanism through a lending protocol * A liquidity provisioning strategy via a DEX This layered design is powerful, but without modular infrastructure, it’s inaccessible to most users and hard to manage even for power users. ### In Summary Curated DeFi is where the market is heading, but **access and composability** haven’t kept up with its growth. **Inception exists to solve this.** By unifying access to the best curated vaults and standardizing reward composition through inTokens, the protocol gives users a way to interact with DeFi’s next phase without having to rebuild the plumbing themselves. # 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 → ***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 *****doesn't***** 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 *****doesn't***** 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 *****doesn't***** 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. # Integrations Once minted, **inTokens** can be deployed across DeFi protocols to earn additional rewards or participate in further strategies such as lending, LPing, or yield tokenization. Below is a breakdown of our partners and integrations, categorized by their functionalities: ## DeFi Integrations
PoolinTokenCollateralProtocolTypeNetwork
inwstETHsinwstETHs--SpectraYield Ethereum✖︎5✅ Live
inwstETHs/wstETHinwstETHswstETHTermMaxLendingEthereum✖︎2✅ Live
inwstETHs/ETHinwstETHsETHLoopLendingEthereum✖︎3✅ Live
inwstETHsinwstETHs--ZircuitYieldZircuit✖︎3✅ Live
inwstETHs/wstETHinwstETHswstETHCurveDEX LPEthereum✖︎3✅ Live
inwstETHsinwstETHs--EulerLendingEthereum✖︎3✅ Live
inwstETHs/wstETHinwstETHswstETHBalancerDEX LPEthereum✖︎3✅ Live
inwstETHs/wstETHinwstETHswstETHUniswapDEX LPEthereum🚧 Coming Soon🕒 Queued
inBTCs/LBTCinBTCsLBTCUniswapDEX LPEthereum🚧 Coming Soon🕒 Queued
> 🔢 **Totem Multiplier** is the reward boost (for Inception points) received for depositing your inToken into the corresponding integration — e.g., ✖︎5 means you now earn x5 the amount ot Totem you would normally receive. For the full list of live integrations, visit our DeFi page on our app: *** ## Supported Wallets * MetaMask * WalletConnect * Trust Wallet * Coin98 Wallet * Bitget Wallet * Bybit Wallet * OKX Wallet # Flash Unstake The Flash Unstake module allows users to **immediately** convert their inTokens into their original state. This feature is achieved by using a fixed-rate conversion approach, which ensures that users receive the full value of their underlying assets. *** ## **Flash Unstake Dynamic Fees** The fee structure for Flash Unstake is intended to be dynamic and responsive to the amount of ETH unstaked. This ensures that the costs remain fair and consistent, adjusting according to the volume of assets involved in the transaction. Here are the different scenarios that could play out: * **Initial Fee**: When the pool's liquidity is abundant, the fee starts at a base rate, providing cost-effective liquidity. * **Rising Demand**: As more ETH is unstaked and the pool's liquidity drops, the fee increases to prevent excessive withdrawals and maintain stability. * **Stabilization**: Once the unstaked amount reaches a higher threshold, the fee stabilizes at an ideal rate, ensuring the pool can support high volumes of transactions without depleting its resources.

Flash Unstake Dynamic Fee

*** ## **The Flash Unstake Pool** The Flash Unstake feature uses a pool of liquid assets set aside exclusively for this operation. This pool is initially limited to **5% of the total deposited tokens in an InceptionLRT** solution (inToken). As the protocol’s Total Value Locked (TVL) increases, the pool scales accordingly, accommodating varying levels of demand and ensuring sustainable liquidity. **Replenishment Mechanism:** * **Fee Distribution**: A portion of the Flash Unstake fee goes to the InceptionLRT treasury, while another portion is used to attract new or existing inToken holders to replenish the pool. * **Bonus**: New depositors earn additional incentives as a result of the Flash Unstake fee, promoting continued participation and maintaining competitive inToken prices. *** ## **Workflow Example** ### **Flash Unstake Process Example:** 1. **User Action**: A user initiates a Flash Unstake request to convert a given inToken back to ETH. 2. **Unstake Amount**: They flash unstake 250 ETH, representing 50% of the Flash Unstake Capacity. 3. **Fee Calculation**: A fee of 0.5% (1.25 ETH) is applied. This fee is split equally, with 0.625 ETH supporting the protocol and 0.625 ETH rewarding new depositors. 4. **Transaction Execution**: Users receive 248.75 ETH instantly, bypassing the traditional 7-day unbinding period. ### **Depositing Process Example:** 1. **New User Action**: Another user wants to acquire 400 ETH for inETH (for example) 2. **Depositing Process:** A user deposits ETH directly on Inception in return for an inToken, receiving additional rewards. 3. **Bonus Mechanics**: The first 250 ETH deposited receives a bonus, while the remaining 150 ETH is deposited without a bonus. The total bonus for the 400 ETH deposit is 0.3125%, based on the proportion of the initial 250 ETH deposit receiving the bonus. For more technical details regarding the Flash Unstake feature, please check here: [***Flash Unstake***](broken://pages/5HE6i3MtwapAm0922UxG#flash-unstake) # Why Flash Unstake? Immediate liquidity is essential for the smooth functioning of decentralized applications (dApps). However, usually, unstaking processes involve lengthy unbonding periods (such as the **7-day withdrawal delay in EigenLayer**), which lock up users' assets and diminish capital efficiency. Inception's Flash Unstake feature takes this challenge head-on. To address this, Inception users can leverage the Flash Unstake feature to immediately convert their inTokens to their original state. *** ## **Scenario Analysis** ### **Scenario 1: DEX Stable LPs** #### **Issues Identified:** * **Low Swap fees**: Transaction fees on Decentralized Exchanges (DEXs) are often minimal, resulting in lower earnings for liquidity providers * **Slippage:** Large trades can have a considerable price impact, particularly in less liquid markets, resulting in inefficient trading. * **Partial Reward Participation**: In pools matched against ETH, only the liquidity offered by the staked token gets rewards, not the ETH portion. * **Opportunity Cost:** Low Swap fees do not offset the opportunity cost of having 100% of tokens earn staking rewards. Liquidity providers may earn more by directly staking their assets. #### Conclusion: * **Capital Inefficiency:** Low Fees, slippage, and partial reward participation make these pools capital efficient, not justifying the risks and opportunity costs involved. * **Unsustainable Model:** Low swap costs do not provide adequate incentives for liquidity providers, making the model unsustainable. * **High Incentivization Costs:** Significant incentives are required to attract liquidity, which can be costly to sustain. ### **Scenario 2: Concentrated Liquidity** #### **Issues Identified:** * **Low Swap Fees:** Similar to the first scenario, swap fees can be low, affecting Liquidity Providers revenues. * **Slippage:** Despite the concentrated liquidity within a specific price range, slippage remains an issue for trades outside these ranges. * **Unpredictability:** The percentage of Liquid Staking Tokens (LSTs) or Liquid Restaking Tokens (LRTs) in the pool can be unpredictable, leading to uncertain outcomes for Liquidity Pools. #### Conclusion: * **ETH Dominance in LP**: Concentrated liquidity pools for LST/LRT tend to be predominantly composed of ETH due to the value deviation of LST/LRT from their underlying assets. * **Primary Market Price (LRT Ratio):** LST or LRTs are often traded at a discount on DEXs compared to their primary market price set by the protocol. They rarely trade at a premium. * **Ineffective Concentrated LPs:** Tokens frequently fall outside of the ideal trading range, rendering concentrated liquidity pools ineffective. *** ## **Advantages of Flash Unstake / What It Addresses** The Flash Unstake module provides a structured solution to the issues identified in typical liquidity provision scenarios. Here's what the feature has to offer: * **Immediate Liquidity**: Allows users to bypass conventional unbinding periods. * **Flexibility:** This feature allows swift portfolio adjustments in response to changing market conditions. Whether reallocating funds to more profitable opportunities or immediately abandoning positions to mitigate risk, the ability to instantly unstake assets gives you a substantial advantage in the dynamic market of DeFi. * **Fixed-rate Conversion**: The Flash Unstake feature allows users to convert staked tokens (LST/LRT) without worrying about slippage. **Fixed-rate conversions eliminate slippage**, resulting in a more predictable and stable experience. * **Predictable Cost of Liquidity:** The cost of liquidity is limited to a maximum of **5%** of the staking rewards, ensuring that liquidity provision is predictable and manageable. This enables users to plan more successfully * **Scalable Liquidity Provision**: The Flash Unstake feature is meant to scale with the protocol's Total-Locked-Value (TVL), accommodating various levels of demand. # Bridge Inception's internal bridge adheres to the **xERC20 standard**, which is a protocol meant to assure interoperability and smooth asset transfer between various Ethereum-compatible networks. This standard enables the development and management of tokenized assets that exhibit consistent behavior and value across numerous blockchains. The bridge allows the transfer of the following Inception Liquid Restaking Tokens (Native or Isolated) to key networks such as: | Network | LRT | | ------------ | --------------------------- | | **Ethereum** | inwstETHs, amphrLRT, inLBTC | | **Arbitrum** | inwstETHs | | **Base** | inwstETHs | | **Zircuit** | inwstETHs | Future versions will include bridge support for new networks, each carefully selected and rigorously tested for adoption, stability, and user experience to ensure optimal security and performance. Users interact with the Bridge using Inception's dedicated user interface, which streamlines asset transfers: [*https://www.inceptionlrt.com/app/bridge/*](https://www.inceptionlrt.com/app/bridge/) # 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) {% 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) {% 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) {% 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) {% 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) {% 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. # Addresses The Inception Protocol is implemented via Inception Vault — a vault based on the[ EIP-4626](https://eips.ethereum.org/EIPS/eip-4626) standard. The protocol supports several LSTs (Liquid Staking Token) as collateral, and for each token, we created a corresponding Inception vault instance and Inception LRT (Liquid Restaking Token). InceptionLRT also has its own Native Liquid Restaking Token (nLRT): **inETH**. All the Involved Smart Contracts, for LST and Native Restaking, are as follows: # inTokens ## -> Symbiotic *** ### inwstETHs #### Ethereum * [**Inception Vault**](https://etherscan.io/address/0xf9D9F828989A624423C48b95BC04E9Ae0ef5Ec97): 0xf9D9F828989A624423C48b95BC04E9Ae0ef5Ec97 * [**Inception Token**](https://etherscan.io/address/0x8E0789d39db454DBE9f4a77aCEF6dc7c69f6D552): 0x8E0789d39db454DBE9f4a77aCEF6dc7c69f6D552 #### Zircuit * [**Inception Token**](https://explorer.zircuit.com/address/0x9eFdE41A87fa4dD47BAa584954e8Abd5b8bdBfE7): 0x9eFdE41A87fa4dD47BAa584954e8Abd5b8bdBfE7 *** ### inLBTCs * [**Inception Vault**](http://etherscan.io/address/0xD496417a50DB34279631e0aF459493Cf9685F529): 0xD496417a50DB34279631e0aF459493Cf9685F529 * [**Inception Token**](http://etherscan.io/address/0xF07052b5A61bbcc8d14a8567494ae8AD688641F9): 0xF07052b5A61bbcc8d14a8567494ae8AD688641F9 *** *** ## **Discontinued** ## -> Symbiotic ### inLsETHs #### **Ethereum** * [**Inception Vault**](https://etherscan.io/address/0xA8211B17Ee8cC9C3E739c32710Cc4d6621B360AE): 0xA8211B17Ee8cC9C3E739c32710Cc4d6621B360AE * [**Inception Token**](https://etherscan.io/address/0x11E8808018AfE9343fceB33043f06E1bfbD5d3f3): 0x11E8808018AfE9343fceB33043f06E1bfbD5d3f3 ## -> EigenLayer ### inETH ### > Mainnet #### Ethereum * [**Inception Token**](https://etherscan.io/token/0xf073bac22dab7faf4a3dd6c6189a70d54110525c)**:** 0xf073bAC22DAb7FaF4a3Dd6c6189a70D54110525C * [**Inception Vault**](https://etherscan.io/address/0x46199cAa0e453971cedf97f926368d9E5415831a)**:** 0x46199cAa0e453971cedf97f926368d9E5415831a #### Mode * [**Inception Token**](https://modescan.io/token/0x5A7a183B6B44Dc4EC2E3d2eF43F98C5152b1d76d)**:** 0x5A7a183B6B44Dc4EC2E3d2eF43F98C5152b1d76d #### Linea * [**Inception Token**](https://lineascan.build/token/0x5a7a183b6b44dc4ec2e3d2ef43f98c5152b1d76d)**:** 0x5A7a183B6B44Dc4EC2E3d2eF43F98C5152b1d76d #### Blast * [**Inception Token**](https://blastscan.io/token/0x5a7a183b6b44dc4ec2e3d2ef43f98c5152b1d76d): 0x5A7a183B6B44Dc4EC2E3d2eF43F98C5152b1d76d #### BNB Chain * [**Inception Token**](https://bscscan.com/address/0x5A7a183B6B44Dc4EC2E3d2eF43F98C5152b1d76d): 0x5A7a183B6B44Dc4EC2E3d2eF43F98C5152b1d76d #### Arbitrum * [**Inception Token**](https://arbiscan.io/address/0x5a7a183b6b44dc4ec2e3d2ef43f98c5152b1d76d): 0x5A7a183B6B44Dc4EC2E3d2eF43F98C5152b1d76d #### Optimism * [**Inception Token**](https://optimistic.etherscan.io/address/0x5A7a183B6B44Dc4EC2E3d2eF43F98C5152b1d76d)**:** 0x5A7a183B6B44Dc4EC2E3d2eF43F98C5152b1d76d **X Layer** * [**Inception Token**](https://www.oklink.com/xlayer/address/0x5a7a183b6b44dc4ec2e3d2ef43f98c5152b1d76d)**:** 0x5A7a183B6B44Dc4EC2E3d2eF43F98C5152b1d76d ### > Testnet #### Ethereum - Holesky * [**Inception Token**](https://holesky.etherscan.io/address/0x76944d54c9eF0a7A563E43226e998F382714C92f)**:** 0x76944d54c9eF0a7A563E43226e998F382714C92f #### Arbitrum - Sepolia * [**Inception Token**](https://sepolia.arbiscan.io/address/0xb1692ed9b08f8dd641f4109568ed6f471166c7e5)**:** 0xb1692ed9b08f8dd641f4109568ed6f471166c7e5 #### Optimism - Sepolia * [**Inception Token**](https://sepolia-optimism.etherscan.io/address/0xb1692ed9b08f8dd641f4109568ed6f471166c7e5)**:** 0xb1692ed9b08f8dd641f4109568ed6f471166c7e5 #### BNB Chain Testnet * [**Inception Token**](https://testnet.bscscan.com/address/0xb1692ed9b08f8dd641f4109568ed6f471166c7e5)**:** 0xb1692ed9b08f8dd641f4109568ed6f471166c7e5 #### Blast Sepolia * [**Inception Token**](https://sepolia.blastscan.io/address/0xb1692ed9b08f8dd641f4109568ed6f471166c7e5): 0xb1692ed9b08f8dd641f4109568ed6f471166c7e5 *** ### instETH #### Ethereum * [**Inception vault**: ](https://etherscan.io/address/0x814CC6B8fd2555845541FB843f37418b05977d8d)0x814CC6B8fd2555845541FB843f37418b05977d8d * [**Inception token**: ](https://etherscan.io/address/0x7FA768E035F956c41d6aeaa3Bd857e7E5141CAd5)0x7FA768E035F956c41d6aeaa3Bd857e7E5141CAd5 #### Linea * [**Inception Token**](https://lineascan.build/address/0xd08C3F25862077056cb1b710937576Af899a4959): 0xd08C3F25862077056cb1b710937576Af899a4959 #### Optimism * [**Inception Token**](https://optimistic.etherscan.io/address/0xd08C3F25862077056cb1b710937576Af899a4959): 0xd08C3F25862077056cb1b710937576Af899a4959 #### Arbitrum * [**Inception Token**](https://arbiscan.io/address/0xd08C3F25862077056cb1b710937576Af899a4959): 0xd08C3F25862077056cb1b710937576Af899a4959 *** ### insfrxETH #### Ethereum * [**Inception vault**: ](https://etherscan.io/address/0x295234B7E370a5Db2D2447aCA83bc7448f151161)0x295234B7E370a5Db2D2447aCA83bc7448f151161 * [**Inception token**: ](https://etherscan.io/token/0x668308d77be3533c909a692302Cb4D135Bf8041C)0x668308d77be3533c909a692302Cb4D135Bf8041C #### Fraxtal * [**Inception Token**](https://fraxscan.com/address/0xE162075a1C0Ac7e985253972bEcA5e83Da3BBaa4): 0xE162075a1C0Ac7e985253972bEcA5e83Da3BBaa4 *** ### inswETH #### Ethereum * [**Inception vault**: ](https://etherscan.io/address/0xc4181dC7BB31453C4A48689ce0CBe975e495321c)0xc4181dC7BB31453C4A48689ce0CBe975e495321c * [**Inception token**: ](https://etherscan.io/address/0xC3ADe5aCe1bBb033CcAE8177C12Ecbfa16bD6A9D)0xC3ADe5aCe1bBb033CcAE8177C12Ecbfa16bD6A9D *** ### **inankrETH** #### Ethereum * [**Inception vault**](https://etherscan.io/address/0x36B429439AB227fAB170A4dFb3321741c8815e55): 0x36B429439AB227fAB170A4dFb3321741c8815e55 * [**Inception token**](https://etherscan.io/address/0xfa2629B9cF3998D52726994E0FcdB750224D8B9D): 0xfa2629B9cF3998D52726994E0FcdB750224D8B9D #### Mode * [**Inception Token**](https://modescan.io/token/0x5A32d48411387577c26a15775cf939494dA8064A): 0x5A32d48411387577c26a15775cf939494dA8064A #### BNB Chain * [**Inception Token**](https://bscscan.com/address/0x5A32d48411387577c26a15775cf939494dA8064A): 0x5A32d48411387577c26a15775cf939494dA8064A #### Linea * [**Inception Token**](https://lineascan.build/address/0x5A32d48411387577c26a15775cf939494dA8064A): 0x5A32d48411387577c26a15775cf939494dA8064A *** ### incbETH #### Ethereum * [**Inception vault**](https://etherscan.io/address/0xfE715358368416E01d3A961D3a037b7359735d5e): 0xfE715358368416E01d3A961D3a037b7359735d5e * [**Inception token**](https://etherscan.io/address/0xBf19Eead55a6B100667f04F8FBC5371E03E8ab2E): 0xBf19Eead55a6B100667f04F8FBC5371E03E8ab2E #### Base * [**Inception token**](https://basescan.org/address/0xb655932ee66a3c609d57cc24309a0e2c594c944e): 0xb655932ee66a3c609d57cc24309a0e2c594c944e *** ### inETHx #### Ethereum * [**Inception vault**](https://etherscan.io/address/0x90E80E25ABDB6205B08DeBa29a87f7eb039023C2): 0x90E80E25ABDB6205B08DeBa29a87f7eb039023C2 * [**Inception token**](https://etherscan.io/address/0x57a5a0567187FF4A8dcC1A9bBa86155E355878F2): 0x57a5a0567187FF4A8dcC1A9bBa86155E355878F2 *** ### inlsETH #### Ethereum * [**Inception vault**](https://etherscan.io/address/0x6E17a8b5D33e6DBdB9fC61d758BF554b6AD93322): 0x6E17a8b5D33e6DBdB9fC61d758BF554b6AD93322 * [**Inception token**](https://etherscan.io/token/0x94B888E11a9E960A9c3B3528EB6aC807B27Ca62E): 0x94B888E11a9E960A9c3B3528EB6aC807B27Ca62E *** ### inmETH #### Ethereum * [**Inception vault**: ](https://etherscan.io/address/0xd0ee89d82183D7Ddaef14C6b4fC0AA742F426355)0xd0ee89d82183D7Ddaef14C6b4fC0AA742F426355 * [**Inception token**](https://etherscan.io/token/0xeCf3672A6d2147E2A77f07069Fb48d8Cf6F6Fbf9): 0xeCf3672A6d2147E2A77f07069Fb48d8Cf6F6Fbf9 *** ### inoETH #### Ethereum * [**Inception vault**: ](https://etherscan.io/address/0x4878F636A9Aa314B776Ac51A25021C44CAF86bEd)0x4878F636A9Aa314B776Ac51A25021C44CAF86bEd * [**Inception token**: ](https://etherscan.io/address/0x9181f633E9B9F15A32d5e37094F4C93b333e0E92)0x9181f633E9B9F15A32d5e37094F4C93b333e0E92 *** ### inosETH #### Ethereum * [**Inception vault**: ](https://etherscan.io/address/0xA9F8c770661BeE8DF2D026edB1Cb6FF763C780FF)0xA9F8c770661BeE8DF2D026edB1Cb6FF763C780FF * [**Inception token**: ](https://etherscan.io/address/0xfD07fD5EBEa6F24888a397997E262179Bf494336)0xfD07fD5EBEa6F24888a397997E262179Bf494336 *** ### inrETH #### Ethereum * [**Inception vault**: ](https://etherscan.io/address/0x1Aa53BC4Beb82aDf7f5EDEE9e3bBF3434aD59F12)0x1Aa53BC4Beb82aDf7f5EDEE9e3bBF3434aD59F12 * [**Inception token**](https://etherscan.io/address/0x80d69e79258FE9D056c822461c4eb0B4ca8802E2): 0x80d69e79258FE9D056c822461c4eb0B4ca8802E2 *** ### inwbETH #### Ethereum * [**Inception vault**: ](https://etherscan.io/address/0xC0660932C5dCaD4A1409b7975d147203B1e9A2B6)0xC0660932C5dCaD4A1409b7975d147203B1e9A2B6 * [**Inception token**](https://etherscan.io/token/0xda9b11cd701e10c2ec1a284f80820edd128c5246): 0xDA9B11Cd701e10C2Ec1a284f80820eDD128c5246 #### BNB Chain * [**Inception Token**](https://bscscan.com/address/0x3059a337b134Cc89851c8DE18A00D880fa1D5519): 0x3059a337b134Cc89851c8DE18A00D880fa1D5519 *** ### inEIGEN #### Ethereum * [**Inception Vault**](https://etherscan.io/address/0xC6Cc133477f63D9c0C53D1eF7DA83fa250778DB4): 0xC6Cc133477f63D9c0C53D1eF7DA83fa250778DB4 * [**Inception Token**](https://etherscan.io/address/0xf21014B114bb976F890E15c19900cE9bE5Fb1e12): 0xf21014B114bb976F890E15c19900cE9bE5Fb1e12 *** ### intBTC #### **Ethereum** * [**Inception Vault**](https://etherscan.io/address/0x016E074Ca7304b815E29A9b9d8CF7a5603DA2A5f): 0x016E074Ca7304b815E29A9b9d8CF7a5603DA2A5f * [**Inception Token**](https://etherscan.io/address/0x1AEe5EC60fc79B669f11FE368fDe789E267649e2): 0x1AEe5EC60fc79B669f11FE368fDe789E267649e2 *** ### insFRAX #### **Ethereum** * [**Inception Vault**](https://etherscan.io/address/0xeFaF124849b11b513C35350CD8643d29DE49c2ba): 0xeFaF124849b11b513C35350CD8643d29DE49c2ba * [**Inception Token**](https://etherscan.io/address/0x50253dc4a01c6408Fab9646e804FCbFDb74e3E4c): 0x50253dc4a01c6408Fab9646e804FCbFDb74e3E4c #### Fraxtal * [**Inception Token**](https://fraxscan.com/address/0x157743261C3ba961e92421b268A881AeCe450d41): 0x157743261C3ba961e92421b268A881AeCe450d41 *** ### inslisBNB #### Ethereum * [**Inception Vault**](https://etherscan.io/address/0xC7373753E8991cEa030B01D580c53dDA4DA31D18): 0xC7373753E8991cEa030B01D580c53dDA4DA31D18 * [**Inception Token**](https://etherscan.io/address/0x74D1984A64F447371Be4019920180b52A33aDAdD): 0x74D1984A64F447371Be4019920180b52A33aDAdD #### BNB Chain * [**Inception Token**](https://bscscan.com/address/0xB2B446386633C6746B0a2735FB57edBb066c5878): 0xB2B446386633C6746B0a2735FB57edBb066c5878 *** # Bridge Mainnet Bridges have the same address across all supported chains. ## > Mainnet ### Ethereum * [**Bridge**](https://etherscan.io/address/0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac): 0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac ### Arbitrum * [**Bridge**](https://arbiscan.io/address/0xc00cd5599f7e128fc5ed5563147a45b12e83b3ac)**:** 0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac ### Base * [**Bridge**](https://basescan.org/address/0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac): 0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac ### Blast * [**Bridge**](https://blastscan.io/address/0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac)**:** 0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac ### BNB Chain * [**Bridge**](https://bscscan.com/address/0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac)**:** 0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac ### Fraxtal * [**Bridge**](https://fraxscan.com/address/0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac): 0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac ### Linea * [**Bridge**](https://lineascan.build/address/0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac): 0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac ### Mode * [**Bridge**](https://modescan.io/address/0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac)**:** 0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac ### Optimism * [**Bridge**](https://optimistic.etherscan.io/address/0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac)**:** 0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac ### X Layer * [**Bridge**](https://www.oklink.com/xlayer/address/0xc00cd5599f7e128fc5ed5563147a45b12e83b3ac)**:** 0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac ### Zircuit * [**Bridge**](https://www.oklink.com/xlayer/address/0xc00cd5599f7e128fc5ed5563147a45b12e83b3ac): 0xC00cD5599F7E128FC5Ed5563147a45B12e83B3ac ## > Testnet ### Ethereum - Holesky * [**Bridge**](https://holesky.etherscan.io/address/0xCDeA808c1C43F95309C8ca398DF41a257aF2Dc8a)**:** 0xCDeA808c1C43F95309C8ca398DF41a257aF2Dc8a ### Arbitrum - Sepolia * [**Bridge**](https://sepolia.arbiscan.io/address/0xCDeA808c1C43F95309C8ca398DF41a257aF2Dc8a)**:** 0xCDeA808c1C43F95309C8ca398DF41a257aF2Dc8a ### BNB Chain Testnet * [**Bridge**](https://testnet.bscscan.com/address/0x983c2239ad08307F978096844166c67E0f1b2630)**:** 0x983c2239ad08307F978096844166c67E0f1b2630 ### Blast - Sepolia * [**Bridge**](https://sepolia.blastscan.io/address/0x983c2239ad08307F978096844166c67E0f1b2630)**:** 0x983c2239ad08307F978096844166c67E0f1b2630 ### Linea - Sepolia * [**Bridge**](https://sepolia.lineascan.build/address/0xCDeA808c1C43F95309C8ca398DF41a257aF2Dc8a)**:** 0xCDeA808c1C43F95309C8ca398DF41a257aF2Dc8a ### Optimism - Sepolia * [**Bridge**](https://sepolia-optimism.etherscan.io/address/0x983c2239ad08307F978096844166c67E0f1b2630)**:** 0x983c2239ad08307F978096844166c67E0f1b2630 # RateProvider The ***RateProvider*** contract is used to get the redemption price for a specific Inception inToken. Check all the contracts below: ## inwstETHs #### Ethereum * [**RateProvider**](https://etherscan.io/address/0xae48B92CBc0882a7D70D878e42cc121a62ceB632)**:** 0xae48B92CBc0882a7D70D878e42cc121a62ceB632 *** *** ## **Discontinued** ## inLsETHs #### Ethereum * [**RateProvider**](https://etherscan.io/address/0x34241c4c5fb90a9c6b37583ed77a346e1a053c17)**:** 0x34241c4c5fb90a9c6b37583ed77a346e1a053c17 ## inETH ### > Mainnet #### Ethereum * [**RateProvider**](https://etherscan.io/address/0xC29783738A475112Cafe58433Dd9D19F3a406619): 0xC29783738A475112Cafe58433Dd9D19F3a406619 #### Arbitrum * [**RateProvider**](https://arbiscan.io/address/0x971b35225361535D04828F16442AAA54009efE1a): 0x971b35225361535D04828F16442AAA54009efE1a #### Blast * [**RateProvider**](https://blastscan.io/address/0xC0660932C5dCaD4A1409b7975d147203B1e9A2B6): 0xC0660932C5dCaD4A1409b7975d147203B1e9A2B6 #### Linea * [**RateProvider**](https://lineascan.build/address/0xBf47307F7Bd75a8db3c8f69F913e9B77fc222e84): 0xBf47307F7Bd75a8db3c8f69F913e9B77fc222e84 #### Mode * [**RateProvider**](https://modescan.io/address/0x971b35225361535D04828F16442AAA54009efE1a): 0x971b35225361535D04828F16442AAA54009efE1a ### > Testnet #### BNB Chain Testnet * [**RateProvider**](https://testnet.bscscan.com/address/0xFea428946A2c602C09c0F737Ea65BC16298b0415)**:** 0xFea428946A2c602C09c0F737Ea65BC16298b0415 #### Linea Sepolia * [**RateProvider**](https://sepolia.lineascan.build/address/0x5d944729CDdfd8270be5c557E53868353cF80A46)**:** 0x5d944729CDdfd8270be5c557E53868353cF80A46 ## instETH #### Ethereum * [**RateProvider**](https://etherscan.io/address/0x343281Bb5029C4b698fE736D800115ac64D5De39)**:** 0x343281Bb5029C4b698fE736D800115ac64D5De39 #### Arbitrum * [**RateProvider**](https://arbiscan.io/address/0x57a5a0567187FF4A8dcC1A9bBa86155E355878F2)**:** 0x57a5a0567187FF4A8dcC1A9bBa86155E355878F2 #### **Linea** * [**RateProvider**](https://lineascan.build/address/0xA365fB18f98cd724F08109f64EA88ED8D7864266)**:** 0xA365fB18f98cd724F08109f64EA88ED8D7864266 ## inrETH #### Ethereum * [**RateProvider**](https://etherscan.io/address/0xD6d553327b16dd6076D69c2DAEc91A50dD1E9F66)**:** 0xD6d553327b16dd6076D69c2DAEc91A50dD1E9F66 ## inoETH #### Ethereum * [**RateProvider**](https://etherscan.io/address/0xbd600020f943f7C61a8123fE2720A05434A3B38b): 0xbd600020f943f7C61a8123fE2720A05434A3B38b ## inosETH #### Ethereum * [**RateProvider**](https://etherscan.io/address/0x1F27848Ae927Ba278eE575e4A55f6c7ED7BFFe8C)**:** 0x1F27848Ae927Ba278eE575e4A55f6c7ED7BFFe8C ## inankrETH #### Ethereum * [**RateProvider**](https://etherscan.io/address/0x8bC73134A736437da780570308d3b37b67174ddb): 0x8bC73134A736437da780570308d3b37b67174ddb ## incbETH #### Ethereum * [**RateProvider**](https://etherscan.io/address/0xa1Bb72c5915a7e2C85BaeA2C563858eaCB3F7A45): 0xa1Bb72c5915a7e2C85BaeA2C563858eaCB3F7A45 ## inwbETH #### Ethereum * [**RateProvider**](https://etherscan.io/address/0x69c59c3DD7566eb12792203f8F832ca81a050eB1): 0x69c59c3DD7566eb12792203f8F832ca81a050eB1 ## inswETH #### Ethereum * [**RateProvider**](https://etherscan.io/address/0xebFa0353DFF1801F5c8Ea07448771D6FadD1E721): 0xebFa0353DFF1801F5c8Ea07448771D6FadD1E721 ## inETHx #### Ethereum * [**RateProvider**](https://etherscan.io/address/0xd812bA3543f9aB64b2BCBcE34fb3b00bFF2bA2FC): 0xd812bA3543f9aB64b2BCBcE34fb3b00bFF2bA2FC ## insfrxETH #### Ethereum * [**RateProvider**](https://etherscan.io/address/0x07f86901057F392fd3A508b8AbcbaafB08c13B1e): 0x07f86901057F392fd3A508b8AbcbaafB08c13B1e #### Fraxtal * [**RateProvider**](https://fraxscan.com/address/0xC0660932C5dCaD4A1409b7975d147203B1e9A2B6): 0xC0660932C5dCaD4A1409b7975d147203B1e9A2B6 ## inmETH #### Ethereum * [**RateProvider**](https://etherscan.io/address/0xA22A7A8c550760574Fd7b722C9f7100902D57707): 0xA22A7A8c550760574Fd7b722C9f7100902D57707 ## inlsETH #### Ethereum * [**RateProvider**](https://etherscan.io/address/0x20f6d8e1e821Bd5B94f7bF725AF304Bc5ef09c36): 0x20f6d8e1e821Bd5B94f7bF725AF304Bc5ef09c36 ## inEIGEN #### Ethereum * [**RateProvider**](https://etherscan.io/address/0xF3207c4A1FC0d32CcD1159f47A8E5A4b1C0fD59F)**:** 0xF3207c4A1FC0d32CcD1159f47A8E5A4b1C0fD59F ## intBTC #### Ethereum * [**RateProvider**](https://etherscan.io/address/0x12181a5454542610f524e53650038889EDC6a07f)**:** 0x12181a5454542610f524e53650038889EDC6a07f ## insFRAX #### Ethereum * [**RateProvider**](https://etherscan.io/address/0xD8554b2075E9b403d26c8cC444B2dd3b929162c2): 0xD8554b2075E9b403d26c8cC444B2dd3b929162c2 #### Fraxtal * [**RateProvider**](https://fraxscan.com/address/0xDA9B11Cd701e10C2Ec1a284f80820eDD128c5246)**:** 0xDA9B11Cd701e10C2Ec1a284f80820eDD128c5246 ## inslisBNB #### Ethereum * [**RateProvider**](https://etherscan.io/address/0xC88B97CEe6dB90c1186497619Eb43Cc8160e391C): 0xC88B97CEe6dB90c1186497619Eb43Cc8160e391C # Modules # Vaults The `vaults` module in the Inception protocol manages how assets are deposited, tokenized, and routed through strategy-specific adapters. It forms the foundation of the Inception inToken infrastructure and enables composability by abstracting different underlying strategies behind a unified vault interface. Vaults are modular and extensible, powered by a plug-in architecture using adapters and handlers. Each vault is deployed through a factory and interacts with both assets and strategies via well-defined adapter interfaces. ## Key Components #### 1. **Base Adapters** * **`InceptionBaseAdapter.sol`**: Core abstract contract that standardizes the adapter structure. It handles initialization, asset registration, access control, and compatibility with ERC-4626-like logic. * **`InceptionEigenAdapter.sol`**: Adapter implementation integrating EigenLayer strategies into Inception vaults. #### 2. **Adapter Handler** * **`AdapterHandler.sol`**: A router that maps vaults to their respective adapters. Ensures that calls from vaults are correctly forwarded to the adapter implementing the logic for the selected strategy. #### 3. **Asset Handler** * Controls the list of supported tokens and tracks relationships between vaults and the tokens they can accept. #### 4. **Interfaces** * Define the expected structure and communication standard between vaults, adapters, and other contracts (e.g., `IVault`, `IAdapter`, etc.). ## Flow Overview 1. A new vault is created via the factory, specifying: * Accepted asset(s) * Adapter to use * Configuration parameters 2. Deposits into the vault are routed to the adapter, which executes strategy-specific logic (e.g., restaking, yield generation). 3. Withdrawals are similarly processed through the adapter, ensuring asset recovery and accounting. 4. Tokenized representations (e.g., `inETH`) are minted and burned based on deposits/withdrawals. ## Smart Contract Highlights | Contract | Role | | ----------------------------- | ------------------------------------------ | | `InceptionBaseAdapter.sol` | Defines adapter logic base class | | `InceptionEigenAdapter.sol` | Specific adapter for EigenLayer strategies | | `AdapterHandler.sol` | Central adapter registry and router | | `AssetHandler.sol` | Asset registry and validation | | `VaultFactory.sol` (external) | Deploys and configures new vaults | ## Extensibility * Developers can build new adapters for different protocols (e.g., Lido, Pendle, Morpho). * New strategies only require adapter contracts to follow the same interfaces. * Vaults are upgradeable (OpenZeppelin proxies), allowing iterative improvements and safety fixes. ## Notes * Contracts are written in Solidity and follow Hardhat development standards. * `.openzeppelin/` folder contains proxy deployment metadata. * Tests and deployment scripts are found in `test/` and `scripts/` respectively. # Restaking Pools The `restaking-pool` module powers the aggregation and delegation of user assets into curated strategies. These pools act as intermediaries between users and shared security networks like EigenLayer or Symbiotic, enabling scalable and permissionless participation in restaking. Each pool can be tailored to a specific strategy or validator set. The architecture supports off-chain coordination via a Go SDK and contract bindings, enhancing automation and interoperability with external systems. ## Key Components #### 1. **Smart Contracts (`contracts/`)** * Implement pool logic, user deposits, validator coordination, and restaking lifecycle. * Likely includes access control (e.g., operator, curator), performance tracking, and rewards management. #### 2. **Off-chain SDK (Go)** * Located in `abigen/`, `generated/`, and `generation/` folders. * Provides tools for interacting with smart contracts from Go-based services. * Includes scripts like `compile_contracts.sh` and `fastgen.py` to build contract bindings and streamline integration. #### 3. **Deployment & Governance** * `deploy/` and `deployment/` folders handle deployment logic, potentially using Hardhat or custom scripts. * `.openzeppelin/` includes metadata for upgradeable deployments. ## Flow Overview 1. **User deposits assets** into a restaking pool smart contract. 2. **Pool logic** routes assets to a target strategy (e.g., EigenLayer restaking). 3. **Rewards and performance data** are tracked. 4. **External validators** or service providers interact via off-chain bindings using the Go SDK. 5. **Withdrawals or reallocation** can be performed by users or orchestrators. ## Cross-Chain & Off-Chain Coordination * Go modules enable validators or external AVS actors to read from/write to contracts efficiently. * `abigen.go`, `utils.go`, and `generated.go` provide a bridge between the on-chain pool state and off-chain decision-making. ## Smart Contract Highlights | Contract Area | Role | | ------------------ | ------------------------------------------------------ | | Pool Core | Manages user deposits, withdrawals, strategy routing | | Access Roles | Defines operators/curators and their permissions | | Rewards Logic | Tracks and distributes earned rewards from restaking | | Validator Registry | (If present) Registers approved restaking destinations | ## Extensibility * Supports modular integration with new shared security networks. * Can be extended with new off-chain agents using the Go SDK. * Deployment scripts make pool creation repeatable and auditable. ## Notes * Implements a blend of Solidity and Go for on-chain and off-chain interoperability. * Ideal for use cases where external actors (e.g., Shared Security Networks, oracles) must participate in pool coordination. # Bridge The bridge module supports multi-chain deployment and configuration of Inception smart contracts. It manages addresses, proxy deployments, and environment-specific parameters for interacting across networks like BSC and Arbitrum. It does not define a protocol-specific bridging mechanism (i.e., token bridges or messaging layers), but instead organizes deployment metadata and configuration files needed to operate Inception’s infrastructure in a multi-chain environment. ## Components #### 1. **Deployment Metadata (`.openzeppelin/`)** * JSON files like `bsc.json`, `arbitrum-one.json` store proxy deployment states for OpenZeppelin upgradeable contracts. * These files are required to maintain upgrade logic across environments. #### 2. **Config Addresses (`config/addresses/`)** * Directory structure by category: * `assets/`: Token address mappings per network * `bridges/`: Addresses of third-party bridges (if applicable) * `factory/`: Vault and adapter factory addresses * `rate_providers/`, `ratios/`: Oracle and pricing feed configurations * Used during deployments and scripts for resolving environment-specific variables. #### 3. **Audits (`audits/`)** * Contains two security reports: * `InceptionBridge_Halborn.pdf` * `InceptionBridge_Veridise.pdf` * These cover upgradeability, access control, and configuration risk. #### 4. **Hardhat Scripts and Config** * `hardhat.config.js`: Hardhat project base setup. * Likely paired with `scripts/` folder to deploy or verify bridge-related contracts. #### 5. **README.md** * Project-level context and installation info. ## Notes * There is no single `Bridge.sol` contract or dedicated on-chain bridge logic in this repo. * The module is primarily responsible for managing multi-network infrastructure and deployment references. * All deployments rely on OpenZeppelin's upgradeable proxy model. # Airdrop The airdrop module manages the permissioned distribution of ERC-20 tokens using an on-chain contract. The main contract, `InceptionAirdrop.sol`, handles eligibility verification, claiming, and tracking of distributed amounts. The module includes its own ERC-20 mock tokens for testing purposes and supports upgradable deployments via OpenZeppelin proxies. ## Components #### 1. **InceptionAirdrop.sol** * Core contract for processing token claims. * Likely includes a Merkle proof-based eligibility verification system or an internal mapping of claimable balances. * Handles validation, token transfers, and claimed state tracking. #### 2. **IInceptionAirdrop.sol** * Interface defining the functions exposed by the main airdrop contract. * Enables integration with other contracts or frontend applications. #### 3. **MockErc20Token.sol / Token.sol** * Simple ERC-20 implementations used for testing. * These are not production contracts. #### 4. **Hardhat Setup** * Hardhat config (`hardhat.config.ts`) and scripts automate deployment. * Uses `.env_example` for environment configuration. #### 5. **Deployment Metadata** * `.openzeppelin/mainnet.json` tracks upgradeable deployment data. ## Flow Overview 1. A Merkle root or claim mapping is initialized with eligible addresses and claimable amounts. 2. A user calls the `claim()` function, passing the required proof (if applicable). 3. The contract validates eligibility and transfers the corresponding ERC-20 amount. 4. The contract marks the user as claimed to prevent re-claims. ## Smart Contract Highlights | Contract | Role | | --------------------------------- | ------------------------------------ | | `InceptionAirdrop.sol` | Airdrop logic and eligibility checks | | `IInceptionAirdrop.sol` | Interface for external interaction | | `MockErc20Token.sol`, `Token.sol` | Mock tokens used in test environment | ## Notes * Intended for token distributions controlled by Inception (e.g., Totem airdrops). * Implementation details (e.g., Merkle root vs mapping) can be confirmed by inspecting the contract directly. * Tests and scripts are provided but require environment setup via `.env`. *** # Rate Providers The rate providers module exposes logic for retrieving or computing the value of vault tokens or underlying assets. This is often required for integrations with strategies, reward calculations, oracles, and accounting systems. Each provider follows a consistent interface and can be asset-specific, with isolated logic per supported token. ## Components #### 1. **Base Provider Logic** * **`RateProvider.sol`** defines core functionality shared across all implementations. * Includes methods to retrieve the current rate, normalize decimals, and interface with upstream pricing sources. #### 2. **Interfaces** * **`IRateProvider.sol`**: Generic interface for fetching the rate of a vault or token. * **`IInceptionVault.sol`**: Interface for reading data from vault contracts (used by providers). #### 3. **Per-Asset Implementations** * Located under `contracts/lst-providers/` * Each folder (e.g., `inankrETH`, `inETHx`, etc.) includes: * A concrete implementation of a rate provider for that asset. * These often wrap external data sources or perform internal calculations. **Example:** ``` function getRate() external view override returns (uint256); ``` ## Flow 1. A vault or strategy contract queries a `RateProvider` contract. 2. The provider retrieves or computes a normalized rate. 3. This rate is used for accounting, reward calculation, or integration purposes. ## Contract Summary | Contract | Role | | ----------------------------------------------------------- | ----------------------------------- | | `RateProvider.sol` | Base logic for rate computation | | `IRateProvider.sol` | Interface for all rate providers | | `InETHxRateProvider.sol`, `inankrETHRateProvider.sol`, etc. | Asset-specific rate retrieval logic | ## Notes * All implementations conform to the same interface for compatibility. * Rate calculation logic may differ depending on the underlying protocol used by the asset (e.g., Lido, Ankr). * Testing and deployment are handled via Hardhat. # Shared Utilities The project does not include a centralized Solidity library for common utilities. Instead, shared functionality is embedded within module-specific folders (e.g., `interfaces/`, `adapters/`, `handlers/`). A small number of scripting utilities also support off-chain operations. ## TypeScript Utility #### `read-json-files.ts` * Located in `projects/common/` * Likely used for reading config or deployment files (e.g., address mappings, JSON ABIs). * Intended to support scripting environments, not used in on-chain logic. ## Interface and Utility Spread * Interface contracts like `IVault`, `IAdapter`, and `IRateProvider` are placed in their respective module folders. * Access control, math operations, and upgradeability are handled via OpenZeppelin contracts imported directly in each Solidity module. ## Notes * Solidity-based shared logic is modular but not centralized. * Developers should reference the interface folders in each module for integration points. * External utility libraries (e.g., OpenZeppelin) are used instead of reimplementing core features. # Deployment This section outlines how Inception smart contracts are deployed across supported networks. The project uses Hardhat as the deployment framework and follows a structured, repeatable process for proxy-based contract deployment. ## Structure * `hardhat.config.ts`: Main configuration file for network definitions and compiler settings. * `.env_example`: Used to define sensitive deployment variables like private keys and RPC URLs. * `.openzeppelin/`: Stores deployment metadata and proxy admin state (for upgradeable contracts). * `scripts/`, `deploy/`, `deployment/`: Contain deployment logic and contract initialization scripts. ## Key Notes * Contracts are deployed using OpenZeppelin’s upgradeable proxy pattern. * Separate JSON config files define deployed addresses for each chain. * Deployment automation is handled by Hardhat scripts tailored per module. * Token address resolution and vault creation parameters are managed via environment configs and script inputs. > This process is primarily intended for internal or development use. External contributors should consult specific module documentation or request access to network-specific deployment instructions if required. # Bug Bounty At Inception, security is our top priority. To ensure the safety and reliability of our platform, we have launched a comprehensive Bug Bounty Program in collaboration with **HackenProof**. This program invites security researchers and ethical hackers to identify potential vulnerabilities in our smart contracts and ecosystem, with rewards of up to **$500,000** for critical findings. *** ## **Focus Areas** The Bug Bounty Program is focused on identifying vulnerabilities within the Inception smart contracts and infrastructure. All testing should comply with the rules and scope outlined below to qualify for rewards. ## **Impacts in Scope** The following impacts are eligible under the Bug Bounty Program: * **Critical Impact (Up to $500,000)**: * Governance voting result manipulation. * Direct theft of user funds. * Permanent freezing of funds. * Miner-extractable value (MEV) exploitation. * Protocol insolvency. * **High Impact (Up to $50,000)**: * Theft of unclaimed yield or royalties. * Permanent freezing of unclaimed yield or royalties * Temporary freezing of funds (at least 30 days). * **Medium Impact (Up to $5,000)**: * Block stuffing for profit. * Griefing attacks. * Unbounded gas consumption. * Theft of gas. * **Low Impact (Up to $1,000)**: * Smart contract failing to deliver promised returns. For a full list of impacts, visit the [***HackenProof Bug Bounty Program***](https://hackenproof.com/programs/inceptionlrt-smart-contracts). ## **Out of Scope** The following are excluded from the Bug Bounty Program: * Attacks requiring leaked credentials or privileged access. * Issues stemming from third-party systems, oracles, or non-eligible contracts. * Denial-of-service (DoS) attacks or automated testing generating excessive traffic. * Sybil attacks, centralization risks, or critiques of best practices. Participants are **prohibited** from testing on public testnets or mainnet environments. Additionally, phishing, social engineering, or testing external third-party systems is **strictly prohibited**. *** ## **Eligibility Criteria** To qualify for rewards: * Be the **first** to report a valid vulnerability. * Submit a detailed, reproducible report **within 24 hours** of discovery through HackenProof. * Include any necessary attachments such as proof of concept, screenshots, or relevant code snippets. * Comply with coordinated disclosure practices, **refraining from publicizing the vulnerability**. #### **Additional rules apply:** * Reports must be submitted using the **email registered** with your HackenProof account. * Participants must not be former or current employees of Inception or affiliated contractors. *Important*: If an attacker can block the contract, but we can resolve the issue by upgrading it, we do not classify this as a permanent freeze. Therefore, we consider it to have a low impact. ## **Assets in Scope** Only smart contracts listed under the [***Inception GitHub repository***](https://github.com/inceptionlrt) and defined as in-scope are eligible for consideration. Proxy contracts and their current or future implementations are included. ## **Range of Rewards** Rewards are based on the severity of the vulnerability: * **Critical**: $5,000 - $500,000 * **High**: $5,000 - $50,000 * **Medium**: $1,000 - $5,000 * **Low**: $100 - $1,000 ## **Join the Effort** Help us make Inception the most secure and reliable platform in DeFi. Submit your findings and become part of the movement to build a safer decentralized future. -> [***Inceptions Bug Bounty Program***](https://hackenproof.com/programs/inceptionlrt-smart-contracts) # Totems **Inception Totems** are an important feature of the Inception Reward system, aiming to deliver tangible benefits to users who actively participate in the platform. Users can accumulate Totems in different ways within the ecosystem, and these can then be used to gain access to exclusive airdrops and additional incentives
*** ## Purpose of Totems **Totems** are reward points that represent a user’s **participation and involvement** with the Inception protocol. They are obtained by Restaking and participating in ongoing campaigns that contribute to the ecosystem’s growth. This section further outlines how Totems can be acquired and used in the platform. *** ## How to Earn Totems: * **Restaking through Inception** * **Liquidity Provision through Defi Integrations**: Engaging with our Defi partner platforms enables users to contribute to liquidity and earn Totem Multipliers as part of ongoing Campaigns * **Referral Program**: Our referral program offers additional Totem Reward boosters (See the Referral Program section for more details) There is no minimum amount required; any restaked ETH will earn Totems. For new users who have recently deposited, it may take 15 minutes to a few hours for the points to show up. As a result of new integrations and use cases within the DeFi space, users will be able to get Inception Totems by interacting with certain protocols. *** ## Calculating Totems: The daily and total quantity of Totems you can earn depends on the amount you Restake in ETH: * 0.001 ETH will yield 10 Totems per day. * 0.1 ETH — 100 Totems per day. * 1 ETH — 1,000 Totems per day. The number of daily Totems received is, as a result, calculated as follows: Daily Totems = Amount of ETH staked x 1,000 The total number of totems received by users is dependent on the number of days staking with Inception Total Number of Totems = Daily Totems x Number of Days The maximum number of Totems a user can earn is capped at 1 billion *** ## Where will my Totems Appear? You may access your Totems through the Dashboard that you used to restake your assets. *** ## Is it Possible to Transfer or Even Lose my Totems? Totems cannot be transferred or lost. The worst-case scenario is that Totem accrual stops if you unstake all of your assets. # FAQ ## What are Totems? Totems aim to provide tangible rewards to users who are actively involved on the platform. They represent a user's participation in the InceptionLRT ecosystem and can be used to obtain exclusive rewards and incentives. ## How can I earn Totems? Totems can be earned through any type of restaking on InceptionLRT, providing liquidity via DeFi Integrations, and taking part in our referral program. ## Is there a minimum amount I need to restake to be eligible to receive Totems? No, any amount of restaked ETH or LSTs will earn Totems. ## How is the daily number of Totems Calculated? The amount of ETH you restake determines how many Totems you receive each day. For instance, restaking 0.001 ETH yields 10 Totems per day, 0.1 ETH yields 100 Totems per day, and 1 ETH yields 1,000 Totems per day. ## How can I calculate the total number of Totems I can earn? The total amount of Totems you can win is calculated by multiplying the daily number of Totems by the number of days you've staked on InceptionLRT. For example, if you stake one ETH for ten days, you will receive 10,000 Totems. ## Is there a cap on the number of Totems I can earn? Yes, each user can earn a maximum of one billion Totems. ## Where can I see my Totems? You can access your Totems through the Dashboard used to restake your assets. ## Can I Transfer my Totems to another User? No, you’re not able to transfer Totems to another user. ## Can I lose my Totems? Totems can't be lost. If you unstake all of your assets, your Totem accrual will simply end. ## How Long does it take for new deposits to reflect in my Totem Balance? For new users who have recently restaked with InceptionLRT, the points may take 15 minutes to a couple of hours to show up on your Dashboard. ## Where Can I find all Totem Boosts? Users can access the Defi Integrations section on the Documentation for detailed information on point boosts for every Integration. -> [***Defi Integrations*** ](broken://pages/gRMHzRZ7K68F0BgHCNa0)
# Referral Program Inception has launched its Referral program, a new tool that rewards our community for spreading the word about our platform. The Program allows you to earn more Totems by asking friends and relatives to join and stake ETH using Inception. ## How the Referral Program Works: 1. **Get your Referral Link** - Once you have your wallet connected, you'll be able to access your referral link here: {% embed url="" %} Referral Program Dashboard {% endembed %} 2. **Share your Link**: Share your referral link with your friends, and social media followers. There is no limit to how many referrals you can invite! 3. **Earn Your Rewards:** For each individual who signs up using your referral link and starts staking, **you'll receive:** * **20%** of the Totems of your referrals * An extra **100 Totems** for every 0.1 ETH staked by your referrals There is no limit to the number of totems you may earn through referral, making it a terrific way to increase your rewards! # Brand Assets ## Logo

PNG

SVG

## Logo Without Text

PNG

SVG

## Totems Logo

PNG

SVG

## ING Token Logo

PNG

SVG

## Inception Token Logos ### > inwstETHs

PNG

SVG

### > inLBTC

PNG

SVG

### > amphrLRT

PNG

SVG

# Audit Reports To strengthen its security and prioritize the safety of users’s funds, InceptionLRT has undergone external security reports. Here are all the auditing reports: * **January 2024 Audit Report by Veridise (Inception v1):** * [**Veridise Report**](https://github.com/inceptionlrt/smart-contracts/blob/master/audits/InceptionV1_Veridise.pdf) * **April 2024 Audit Report by Halborn (Inception v2):** * [**Halborn Report**](https://github.com/inceptionlrt/smart-contracts/blob/master/audits/InceptionV2_Halborn.pdf) * **October 2024 Audit Report (reaudit + Symbiotic Vault)** * [**Halborn Report**](https://github.com/inceptionlrt/smart-contracts/blob/feat/halborn_symbiotic_script/audits/Inception_DiamondProxy_SymbioticVault_Halborn.pdf) * **March 2025 Audit Report (Symbiotic Vault)** * [**Oxorio Report**](https://github.com/inceptionlrt/smart-contracts/blob/master/audits/Inception_MellowV2_Symbiotic_Oxorio.pdf) * **March 2025 Audit Report (Symbiotic Vault)** * [**Veridise Report**](https://github.com/inceptionlrt/smart-contracts/blob/master/audits/VAR_inception_250210_smart_contracts_V3.pdf) ## B**ridge:** * **April 2024 Audit Report by Halborn:** * [**Halborn Report**](https://github.com/inceptionlrt/bridge/blob/master/audits/InceptionBridge_Halborn.pdf) * **April 2024 Audit Report by Veridise:** * [**Veridise Report**](https://github.com/inceptionlrt/bridge/blob/master/audits/InceptionBridge_Veridise.pdf)