Skip to main content
CoverFi helps Stellar users create short-term protection positions, resolve payments by username, keep receipt history, and understand reserve risk before signing. Protection is not insurance. Payouts are not guaranteed. Every important action depends on wallet signatures, contract rules, oracle freshness, reserve state, and Stellar network execution.

Start with your goal

I am a new user

Learn the exact app flow from wallet connection to protection, payments, and receipts.

I am learning the terms

Understand reserves, premiums, liquidity, basis points, oracle data, settlement, and claims.

I am reviewing CoverFi

See the SCF/reviewer summary, proof checklist, limitations, and milestone plan.

I am evaluating the architecture

Review the combined product, protocol, operations, and ledger transparency architecture.

Technical architecture

Review the current Stellar, Soroban, backend, username payment, receipt, and verification architecture.

CoverFi app

Learn the dashboard routes, protection flow, username payments, and mobile behavior.

CoverFi AI

Understand chat mode, research mode, live market context, and payment drafts.

Smart Contracts Ecosystem

Review the architecture, flow, deployment, and testing details of CoverFi contracts.

Security & trust

Review the threat model, oracle policy, admin policy, and audit readiness checklist.

Economics model

Understand fee, reserve capacity, payout cap, and utilization rules.

How CoverFi works

CoverFi is split into a public website, authenticated app, backend API, protocol monitor, research library, docs site, and Soroban contract workspace.

Product surfaces

Important behavior

Protected app routes preserve the page a user wanted to open. For example, visiting /app/protect directly sends the user to /login?next=app/protect, then returns them to /app/protect after wallet login. CoverFi AI can draft payment and protection instructions, but it never executes transactions. Users must always review and sign through their wallet. The core product is the protection and reserve workflow. AI is a support layer, not the trust anchor.