Proof of concept

This page describes the proof-of-concept credit-line flow for API/RPC providers. The credit-line mechanics (facilities, usage, limits, settlements, on-chain observation) are built. Underwriting and KYB are interim. Each section says which is which. See the Roadmap for the full list.

Service provider, Float, small business#

The core credit-line relationship. Float scores the business and sends the provider a credit-limit attestation. The provider serves API calls on credit, and the business settles through an auto-deducted Solana delegation. Usage and settlement events flow back to Float and update reputation.

flowchart LR
  F["Float<br/>scores the business"]
  SP["API/RPC provider"]
  B["Small business"]
  subgraph SOL["Solana · funds move here only. Float never holds, routes or moves funds"]
    D["Auto-deducted delegation<br/>Subscriptions & Allowances"]
  end
  F -->|"1 · credit-limit attestation"| SP
  SP -->|"2 · serves API calls on credit"| B
  B -->|"3 · usage settles"| D
  D -->|"3 · settlement pulled"| SP
  SP -.->|"4 · usage + settlement events"| F
  D -.->|"4 · observed by chain observer"| F

Tiers for higher limits#

Limit and rate move together as a function of settlement history. Each clean cycle earns better terms, but the step gets smaller as the streak lengthens. There is little information early, so the first moves are big. Once there is a track record, the same evidence moves the terms less.

flowchart LR
  A["Credit extended<br/>at current terms"] --> B["Usage &<br/>settlement"]
  B --> C["Verified on-chain"]
  C --> D["Reputation updates"]
  D --> E["Terms reassessed"]
  E --> A

Know-Your-Business (KYB)#

The pre-check before a business's first credit line, when no on-chain reputation exists yet. A pass or fail feeds into the first underwriting assessment as one input.

flowchart LR
  A["Business onboards"] -.-> B["KYB + wallet<br/>sanctions screening<br/>in progress"]
  B -.->|"pass / fail"| C["Input to first<br/>underwriting assessment"]

Underwriting#

How a credit-line request becomes an assessment, and then a credit facility.

flowchart TB
  A["Credit-line request<br/>submitted"] --> B["Handed to the<br/>underwriting engine"]
  subgraph POC["Interim POC engine · not the final engine"]
    direction LR
    K["KYB / sanctions result"] --> R["Conservative<br/>fixed-limit rule"]
  end
  B --> POC
  POC --> S["Assessment stored"]
  S --> C["Credit facility created"]
  C --> F["approved limit<br/>connected provider<br/>reset cadence"]

1. Submit

   The provider submits a credit-line request. It is acknowledged immediately and processed asynchronously.

2. Dispatch

   Float hands the request to the underwriting engine.

3. Interim assessment

   The POC engine combines the KYB and sanctions result with a conservative fixed-limit rule. The real engine isn't built yet.

4. Store and open the facility

   The assessment is stored, and a credit facility is created with its approved limit, connected provider and reset cadence.