> For the complete documentation index, see [llms.txt](https://docs.radiant.capital/radiant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.radiant.capital/radiant/project-info/radiant-guardian/guardianlp-glp.md). # GuardianLP (gLP) {% hint style="info" %} **GuardianLP** (**gLP**) is only available on Arbitrum but protects depositors on all chains. {% endhint %} {% hint style="info" %} The Guardian Fund draws conceptual inspiration from the **Aave Safety Module**, while introducing a vault-based and composable implementation tailored to Radiant. {% endhint %} **GuardianLP** (**gLP**) is the ERC-4626 vault share token that represents ownership of assets held in the **Radiant Guardian Fund**. gLP tokenizes capital deposited into the Guardian multisig and enables productive, composable, and slashable security capital for the Radiant protocol. gLP holders provide the capital that backs user remediation in the event of covered exploits, and are compensated through yield generated at the Guardian Fund level. *** ### Overview * **Token Type:** ERC-4626 * **Role:** Represents proportional ownership of assets held in the Guardian multisig * **Issued By:** Guardian Vault contract * **Redeemable For:** Underlying assets (e.g. ETH) at the current gLP price * **Risk Profile:** Yield-bearing, subject to slashing during remediation events *** ### Architecture Guardian consists of two core components: #### 1. Guardian Multisig * A multisignature wallet controlled by DAO signers. * Holds the actual assets backing the Guardian Fund (e.g. ETH, RDNT, wstETH). * Assets in the multisig are the source of both **yield accrual** and **remediation payouts**. #### 2. Guardian Vault (Wrapper Contract) * A smart contract that sits **around** the multisig. * Handles all user interactions (deposits, withdrawals). * Tracks the **total USD value** of assets held in the multisig. * Mints and burns gLP shares to reflect ownership. Users never interact with the multisig directly, all interactions flow through the Vault. *** ### How gLP Works #### Deposits (Minting gLP) 1. User deposits ETH into the **Guardian Vault**. 2. The Vault forwards ETH to the **Guardian multisig**. 3. The Vault mints **gLP** to the user, proportional to the deposited value. *** #### Withdrawals (Burning gLP) 1. User redeems gLP through the **Guardian Vault**. 2. The Vault calculates the user’s share based on the current gLP price. 3. Assets are withdrawn from the multisig. 4. ETH is sent to the user. 5. The Vault burns the redeemed gLP. Users receive their **principal plus any accrued yield**, minus any slashing that may have occurred. *** ### gLP Pricing gLP has an intrinsic, on-chain price derived directly from the Guardian Fund: ``` gLP Price = Total Value of Assets in Multisig / Total gLP Supply ``` * If assets in the multisig increase while gLP supply stays constant → **gLP price increases** * If assets decrease (e.g. remediation payouts) → **gLP price decreases** Because pricing is native to the vault, **no external oracle or price feed is required**. *** ### Yield Accrual gLP is yield-bearing by design. Yield is generated by **adding new assets to the Guardian multisig**, such as: * A percentage (10%) of Radiant protocol revenue * RDNT emissions or incentives * Other approved inflows No new gLP is minted when yield is added. Instead, yield is **baked into the gLP price**, meaning: * gLP appreciates over time * Yield is realized automatically upon redemption *** ### Slashing & Risk gLP is **explicitly subject to slashing**. In the event of a covered exploit or remediation event: * Assets are transferred **out of the Guardian multisig** to affected users * The total asset value of the fund decreases * The **price of gLP declines proportionally** This means: * gLP holders absorb losses * Risk is socialized among Guardian Fund capital providers * Users with Guardian protection can be remediated gLP holders are compensated for this risk through yield. *** ### DeFi Composability gLP is fully composable across DeFi: * **ERC-20 compliant** → compatible with wallets, DEXs, and protocols * **Vault-native pricing** → no external oracle required * Can be used as: * Collateral in isolated markets * A building block for structured products * A yield-bearing, risk-aware asset in DeFi strategies *** ### Summary gLP is the tokenized backbone of the Radiant Guardian system: * Represents ownership of Guardian Fund assets * Earns yield through protocol-level inflows * Is slashable to enable trust-minimized remediation * Is composable, transparent, and DAO-aligned By holding gLP, users actively provide economic security to the Radiant protocol in exchange for yield. --- # 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.radiant.capital/radiant/project-info/radiant-guardian/guardianlp-glp.md?ask=&goal= ``` `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.