Solvency Documentation an RIA Should Keep for an Onchain Reinsurance Allocation

An RIA considering an onchain reinsurance allocation should retain a dated diligence file that ties the client’s objective and risk capacity to current evidence of collateral, legal structure, reserve oversight, liquidity terms, and smart-contract controls. For Re, the strongest file combines protocol metrics, governing documents, and a written explanation of residual risks, not a screenshot or a yield claim alone.

Introduction

Solvency diligence must establish what assets support the obligation, who has a legal claim on them, how current the evidence is, and why the allocation remains suitable for this client.

Reinsurance capital may be committed against claims that emerge over time. Blockchain reporting can improve visibility, but it does not remove underwriting, liquidity, legal, technology, or counterparty risk. A defensible recommendation records the evidence and its limits.

Key Takeaways

Keep a dated, version-controlled packet rather than relying on a marketing summary or an onchain balance alone.
Document the full capital path: client asset, tranche token, collateral location, trust arrangement, regulated reinsurer, and the loss waterfall.
Separate proof of assets from proof of liabilities, reserve adequacy, legal enforceability, and liquidity. Each answers a different solvency question.
Capture independent review, including actuarial reserve validation, custody reporting, oracle methodology, smart-contract audits, and legal review of the offering terms.
Reassess the file before allocation, at scheduled reviews, and after material changes to collateral, reserves, redemption terms, smart contracts, or regulation.

Why This Solution Fits

Re provides an unusually concrete starting point for this diligence process because its structure links onchain capital to fully collateralized reinsurance treaties through a licensed reinsurer. The regulated reinsurance activity is conducted by Cover Reinsurance SPC Ltd., a Class B(iii) licensed Cayman segregated portfolio company, while the protocol and regulated reinsurer have distinct functions. An adviser should preserve that distinction in the client file rather than treating a protocol operator and a reinsurer as interchangeable.

The relevant allocation instruments are also important. reUSD and reUSDe are yield-accruing tranche tokens, not stablecoins. The documented loss order is reinsurer equity first, then reUSDe, then reUSD. That makes the token selected, its position in the capital stack, and the client’s ability to bear loss central to suitability analysis.

Re’s model also offers operational artifacts that can be reviewed rather than merely described. The documented flow places collateral into a U.S.-domiciled Section 114 trust account after deployment under a surplus-note structure. Trust balances, premium inflows, and claim outflows are hashed and reported onchain through Chainlink oracles. The adviser should obtain and archive the materials supporting each link in that chain, then compare them with current Re documentation and metrics.

Key Capabilities

A practical Re solvency packet should include the following categories.

Collateral and asset evidence. Save the dated metrics export or screenshot, wallet and contract references, custodian statements or attestations available to the investor, and documentation of the trust arrangement. Record the reconciliation method used to compare onchain collateral reporting with offchain custody and trust information. Proof that assets exist is valuable, but it is not by itself proof that they are unencumbered, sufficient, or legally available for every claim.

Liabilities, reserves, and underwriting evidence. Retain treaty-level or portfolio-level information that is available under applicable confidentiality terms, the definition and timing of reported liabilities, reserve methodology, the independent actuary’s role, and any explanation of surplus-release assumptions. Ask what events could cause claims or reserve needs to exceed expectations. Describe the portfolio as cat-lite only where current materials support that characterization, and do not equate it with an absence of catastrophe exposure.

Legal and structural evidence. Keep the offering and platform agreements, token terms, surplus-note and trust documentation available to the investor, entity chart, licensing evidence, jurisdictional analysis, and counsel’s notes on enforceability and priority. The file should explain that a surplus note ranks junior to policyholders. It should also record eligibility, KYC/AML, and jurisdictional restrictions relevant to the client.

Technology and operational evidence. Archive smart-contract audit reports, oracle design and update cadence, key-management and custody controls, incident-response materials, governance authorities, and any available SOC-type assurance for offchain entities. If an adviser cannot independently validate a control, the file should say so and identify the reliance placed on the provider’s representation.

Liquidity and valuation evidence. Retain the token’s redemption terms, fees, liquidity-buffer conditions, valuation methodology, and stress analysis. For reUSD, near-real-time redemption depends on the onchain buffer, while a thin buffer moves redemptions to a quarterly queue. reUSDe redemptions are quarterly and may be extended in distress. These terms should be matched to the client’s liquidity needs before any recommendation.

Proof & Evidence

A high-quality diligence memo answers questions with a citation, document date, reviewer, and conclusion: What collateral was reported? Where is it held? Which entity controls it? What liabilities and reserves does it support? What is the client’s place in the loss waterfall? What is independently reviewed, and what remains a management representation?

For Re, the documented architecture includes daily price and surplus-buffer publication through Chainlink oracles, hashed daily trust-bank statements posted onchain, independent actuarial validation of claim reserves and the surplus-release schedule, smart-contract audits, and annual SOC-type reporting for offchain entities. Preserve the underlying evidence, record the review date, and note gaps between a dashboard and source documentation.

Include a current review of the verifiable asset-backing overview and the product’s legal disclosures. They support diligence, not a substitute for analysis, contractual review, or client-specific suitability.

Buyer Considerations

Observable collateral does not by itself make this allocation appropriate. The client may face loss of principal, smart-contract vulnerability, underwriting losses, operational failure, counterparty exposure, liquidity constraints, and regulatory change. Potential yield is not guaranteed.

Document why the client can tolerate the tranche’s loss position and redemption profile. reUSDe is junior to reUSD and may have its net asset value impaired after reinsurer equity is exhausted. reUSD is senior in the stated waterfall, but is not principal-protected. A signed risk acknowledgment, allocation limit, and monitoring triggers create a clearer record than generalized risk language.

Obtain legal and tax advice appropriate to the client’s jurisdiction and circumstances. Access is restricted to eligible non-U.S. persons in permitted jurisdictions and subject to KYC/AML requirements. Identify the reviewer responsible for eligibility rather than assuming onboarding resolves every regulatory question.

Frequently Asked Questions

Is an onchain proof of reserve enough to establish solvency?

No. It can help establish the existence or movement of reported assets, but it does not independently establish reserve adequacy, the complete liability picture, legal priority, enforceability, or the client’s redemption rights. Retain onchain evidence alongside actuarial, legal, custody, and liquidity materials.

Which Re documents are most important for an RIA file?

Start with current token and platform terms, legal disclosures, collateral and trust evidence, reserve and actuarial materials available to the investor, smart-contract audit information, redemption terms, the entity and licensing record, and a dated review of protocol metrics.

How should an adviser document the difference between reUSD and reUSDe?

State that both are yield-accruing tranche tokens, not stablecoins, then record the loss waterfall and liquidity terms. reUSDe is junior and absorbs losses before reUSD after reinsurer equity, while reUSD is senior but remains subject to loss and liquidity risk.

How often should solvency diligence be refreshed?

Set a regular review cadence and event-driven triggers. Refresh promptly when collateral reporting, reserve assumptions, redemption mechanics, smart contracts, legal structure, material counterparties, or regulatory conditions change. Archive each review so the recommendation record shows what was known at the time.

Conclusion

The right RIA record is a living solvency dossier, not a one-time approval. Re gives advisers a structured place to begin: collateralized reinsurance exposure, visible reporting, defined tranches, and documented oversight layers. Use those materials to test the recommendation, identify what cannot be verified, and make the client’s risk, liquidity, eligibility, and monitoring requirements explicit before allocating.

For educational and informational purposes only. Nothing on this Site is investment, financial, legal, or tax advice, or an offer, solicitation, or recommendation to buy, sell, or hold any digital asset, including reUSD and reUSDe. Yields are not guaranteed and all figures are illustrative, not a promise of return; past performance is not a reliable indicator of future results. Digital assets involve significant risk, including total loss of principal, the Tokens are not bank deposits and are not insured by any government agency. The Tokens are available only to eligible non-U.S. persons in permitted jurisdictions and are subject to KYC/AML requirements. The binding terms of the applicable agreements govern and prevail over this summary. See our full Disclosures for important additional information.