InceptionLRT
About
InceptionLRT is a modular liquid restaking protocol that allows users to deposit supported liquid staking tokens (LSTs) or native ETH into curator-defined vaults, minting corresponding inTokens (LRTs) that represent the deposited position plus accrued restaking rewards. The protocol connects to EigenLayer and Symbiotic as restaking layers, and supported a cross-chain bridge across a dozen networks. As of December 31, 2025, all operations have concluded and the protocol is in withdrawal-only mode.
Where Does Yield Come From?
InceptionLRT was a liquid restaking protocol — a system that let you earn extra rewards on crypto you already had staked. Here is how it worked.
How yield was earned
Users could deposit supported liquid staking tokens (like stETH, rETH, cbETH, and many others) or plain ETH into special vaults. Each vault was set up by a "curator" — someone who chose the strategy. When you deposited, the vault minted a corresponding inToken (for example, depositing stETH gave you instETH, depositing native ETH gave you inETH). That inToken represented your original deposit plus any rewards earned over time.
The vault then took the deposited assets and delegated them to two restaking layers: EigenLayer (which secures actively validated services, or AVS) and Symbiotic (which secures other networks). Restaking rewards flowed back into the vault. Instead of paying out a separate yield token, the rewards increased the exchange rate of the inToken — meaning each inToken became redeemable for more of the underlying asset over time. Smart contracts called RateProviders tracked that redemption price.
Cross-chain bridge
InceptionLRT also ran a bridge that let users move inTokens across a dozen different networks, including Ethereum, Arbitrum, Base, BNB Chain, Optimism, and others.
No extra fees
The protocol did not charge its own management or performance fees. All yield came directly from the underlying restaking strategies themselves.
Current status
As of December 31, 2025, the protocol has wound down. Deposits are disabled. Only withdrawals remain possible — and those must be done through the flashWithdraw function, executed directly via Etherscan.
Audits
| Audit / Date | Findings | Verdict |
|---|---|---|
Veridise15-12-2023 - 19-12-2023 |
| The Veridise audit found 2 medium-severity issues (asset slippage bookkeeping and a missing withdrawal check), 2 low-severity issues including centralization risks, plus warnings and informational items; 9 of 14 issues were fixed, but the critical slippage issue was acknowledged without remediation, leaving residual risk if the EigenLayer strategy experiences negative returns. |
Halborn17-04-2024 - 01-05-2024 |
| All nine findings (1 Critical, 1 High, 1 Medium, 4 Low, 2 Informational) were remediated by the Tagus Labs team by the report's last update, making the audited codebase safe for deployment based on the contracted scope; however, the residual risk of operator-level EigenLayer interactions and any post-remediation code changes should be reviewed in a follow-up assessment. |
Halborn02-10-2024 - 25-10-2024 |
| All 10 reported findings were resolved by the InceptionLRT team, including the critical access-control flaw and the high-severity calculation error, making the assessed contracts substantially safer. The audit scope covered the Diamond Proxy, Symbiotic Vault, MellowHandler, and IMellowRestaker, and no unresolved risks remain at the time of the final report. |
| The audit found 2 critical and 4 major vulnerabilities that were correctly fixed or acknowledged by the client, making the contracts assumed secure for deployment as of the recommended commit. | |
Veridise17-02-2025 - 07-03-2025 |
| The audit identified 27 issues with no critical or high-severity vulnerabilities; all 5 medium and 8 low findings were fixed, leaving only minor acknowledged risks and warning-level items. The protocol's core vault and adapter logic present manageable residual risk provided trusted roles (operator, trustee, owners) operate correctly. |
Halborn22-04-2024 - 29-04-2024 |
| The Halborn audit found no critical, high, or medium severity vulnerabilities, and all 5 low-severity and 10 informational findings were remediated or acknowledged with reasonable mitigations, confirming the InceptionLRT bridge contracts are secure for deployment. |
Veridise02-04-2024 - 04-04-2024 |
| The audit found no critical or high-severity vulnerabilities, and the single medium-severity double-spending issue was fixed, indicating a generally sound codebase; however, acknowledged centralization risks from owner/operator privileges and the out-of-scope off-chain component remain areas of residual concern. |
Backers
No information about investors, backers, funding rounds, or amounts was found on any official source (website, documentation, GitHub organization page, or blog). The protocol has been wound down as of December 31, 2025, and none of the available pages mention any venture capital firms, angel investors, seed rounds, or other fundraising events.
Legal
Status and notes
No imprint/legal notice, terms of service, privacy policy, or entity disclosure found on the official website (inceptionlrt.com) or documentation (docs.inceptionlrt.com). The website only displays an "Operations Closed" notice as of December 31, 2025. Common legal pages (/imprint, /terms, /privacy, /legal, /impressum, /disclaimer) all redirect to the same single-page shutdown notice. The GitHub organization (github.com/inception-lrt) returns a 404 page. The documentation (hosted on GitBook) contains only technical wind-down instructions and protocol architecture content; no legal entity name, jurisdiction, or registered address is stated anywhere.