> For the complete documentation index, see [llms.txt](https://lucia-protocol.gitbook.io/lucia-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lucia-protocol.gitbook.io/lucia-protocol/risk-management.md). # Risk Management **Capitalization and insPlot Funding** The initial capital inflow for the insPlot pool will primarily be sourced from the Security Token Offering (STO), public sales, additional listings, and partnerships with liquidity providers. Liquidity providers are incentivized to stake LCI tokens into the insPlot pool, particularly during the project's nascent stages when valuation is comparatively low. This mechanism not only allows them to accumulate a larger stake in the project but also to partake in shared revenue streams, as elaborated in prior sections. This incentive is calculated as a function of the initial valuation *V* and the revenue share *R*:
**Risk Evaluation and Premium Structuring** The Lucia Credit Attribution score serves as the cornerstone for risk evaluation, subsequently influencing the insurance premium levels. The granular data provided by this scoring model are instrumental in precisely tailoring the insurance fees. The individualized nature of each lender and "Shed" introduces a variance in risk profiles. Borrowers with positive credit attribution scores, a sound repayment history, and a stable current "Shed" are generally subjected to lower fees. The Lucia Credit Attribution Score (*S*) is integral to risk evaluation. The individualized risk premium (*RP*) for insurance is calculated as:

Where Repayment_History and Shed_Stability are other factors affecting the risk profile.

\ **Dynamic Fee Structuring** When a sudden surge in claims occurs (*𝛥Claims*), either for a specific borrower or within an asset "Barn" pool, the insurance fee structure is recalibrated. The new fee (*New\_Fee*) is calculated as:

Where h is a function that takes into account the spike in claims, the Lucia Credit Attribution Score, and the current fee Current_Fee.

**Community-Based Fee Voting** The community's vote (*V\_community*) for a balanced fee is modeled as:

Where k is a function that balances market incentives and current risks to determine the voted fee.

**Compliance with Traditional Regulatory Frameworks** In an effort to ensure financial stability and stave off insolvency, Lucia Protocol intends to adhere to established capital requirements analogous to traditional insurance providers. Specifically, compliance will align with the **Solvency II Supervisory System laid out in Article 101**. Accordingly, a confidence level of 99.5% must be maintained, signifying the probability of meeting all payment obligations over a one-year horizon. The coverage ratio, representing the ratio of worst-case scenario capital requirements to Lucia Protocol's own reserves, must equate to 100%. In simple terms, this stipulates that Lucia Protocol must maintain sufficient capital reserves to weather adverse financial conditions, thereby providing insurance customers with a 100% coverage ratio. --- # 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://lucia-protocol.gitbook.io/lucia-protocol/risk-management.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.