Business Validator Protocol

Insurance Validator

How scheduled payments become protocol records and covered shortfalls become claims.

View Markdown ↗

Responsibility

An Insurance Validator (IV) underwrites specified asset obligations through policies with defined coverage, expiry, and a beneficiary. It must maintain the capital and operational process to meet covered claims.

Insurance capital and protocol stake serve different purposes. Claims are funded from the IV's business capital; ASSET stake makes failures costly. A posted stake balance does not establish that every insured loss can be paid.

The payment schedule anchors the obligation

An asset's schedule records amounts and due times. The settlement interface exposes whether each payment is missed or resolved. Insurance and scoring consume those records, so their meaning must remain consistent across integrations.

A partial payment does not resolve a full obligation. Resolution requires the recorded cumulative payment to reach the amount due.

How the tokenization adapter records payment

The T-REX settlement adapter records payment attestations from an authorized settlement reporter. Each record includes a payment reference and evidence commitment. Timer-based missed-payment marking and eligible claim opening can be triggered by other callers, but payment recording is permissioned.

The adapter is an accounting bridge to the payment process. Calling it does not itself move fiat or stablecoins to investors. A payment recorded on-chain therefore carries a trust dependency on the reporter and its evidence process. Do not interpret it as independent proof of a bank transfer.

From a shortfall to a claim

At testnet block 4503, one address held the settlement-reporter role. Governance can change that address through the timelock. The reporter's evidence and operational controls matter because scoring and insurance consume its records. A keeper can trigger eligible time-based processing, but cannot replace a missing payment attestation with independent proof of payment. An IV binds a policy to an asset with specified coverage, expiry, and a beneficiary. When a covered scheduled payment is missed, claim eligibility and size are derived from the policy and settlement records.

Coverage is bounded. The adapter accounts for the remaining shortfall and available policy coverage, rather than allowing every overlapping policy to claim the whole loss. When several policies cover a payment, claim-opening order can affect which policy's coverage is allocated first.

The tokenization adapter treats the policy beneficiary as a trustee or special-purpose entity representing holders. It does not automatically allocate the claim across every current token holder.

Payout and enforcement

The IV is responsible for funding the claim from its operating capital. The reporter records claim payments, and full recorded payment resolves the claim. Late resolution and continued non-payment lead to different penalty paths.

A penalty against stake and payment of the insurance claim are separate events. Slashing does not by itself demonstrate that the beneficiary has received compensation.

Recovery has its own limits

The protocol includes interfaces for the Disaster Recovery Fund (DRF) and NDT recovery claims. They allow enforcement and wind-down to record recovery obligations and route proceeds.

These components currently have reference implementations; production funding and redemption remain unverified. Coverage, beneficiary rights, available recovery funds, and distribution arrangements must be confirmed for the particular deployment and instrument.

Prepare insurance operations

Follow Become a Business Validator for admission and role preparation. Plan for insurance book transfer and wind-down before accepting long-lived policies.