# Risks mitigation

At Credix, we've deployed various strategies/design choices to keep the platform operational in case of disaster scenarios and to mitigate blockchain/stable-coin risks.

\
**Only whitelisted parties allowed**

On-chain interactions are only possible by parties who go through KYC/B + accreditation. This is enforced on a smart-contract level by on-chain whitelisting (on the environment level).&#x20;

**Segregated on-chain environment per pool/deal**

A new, on-chain environment will be set up for this deal. Only whitelisted parties, specifically for a pool/deal, will be able to interact with the pool/deal.&#x20;

\
**Eliminating the need for web3 wallets & custody**

[Smart contract-owned wallets](https://www.notion.so/credix/EXT-Smart-Contract-Owned-Wallets-4470f175212b48a59069736c11d9746e?pvs=4) eliminate the need and overhead of operating a web3 wallet + custody. (tranche) tokens are only used on-chain for accounting reasons; settlement happens directly on the exchange of choice<br>

**Short-lived USDC exposure**

End-to-end transaction processing automation by leveraging smart contract-owned wallets and sub-second confirmation times on Solana reduces USDC exposure to minutes.&#x20;

**Off-chain data lake for disaster continuity**

We record every on-chain transaction with the Credix smart contracts and store this information in a database. Not only does this data power (historical) monitoring and reporting; but it can also be used to move settlement flows off-chain in the unlikely event of a Solana outage. Using and updating the off-chain data and calculations, we can settle using fiat rails or through Circle. <br>


---

# Agent Instructions: 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:

```
GET https://docs.credix.finance/other-links-and-resources/risks-mitigation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
