Skip to content

LightRain.

Société de liquidité décentralisée

Download App

LedgerBranch

Identity Encryption — End-to-end protection for attestations and session-bound keys

Enrollment

We'll email you a secure link to establish your account. Identity encryption is enabled once you complete the flow. Your recovery signers are configured immediately.

firstclassmail.cc

BlackLetter

Account & Signature Sign On Services Policy-governed credential posture: attestation-brokered access and sign-on.

Generate cryptographic signatures tied to your attestation. Each application login is a verified signature request. Your keys never leave your control.

blackletter.cc

Welcome Back

Sign on to manage your positions and your credit lines.

Sign OnCreate An Account
Legal Notice

Application gateway

The trust layer of LightRain execution, on a phone.

LightRain is the read-only iOS observability application for the LightRain execution stack on Base. It renders every position, every reconciliation, every oracle attestation, in real time. It does not sign transactions. It does not move funds. It is the eyes of the stack, never the hands.

Sign in to your institutional LightRain instance, or request a TestFlight invitation.

Notional reconciled

$1.84B

Avg push latency

214 ms

Active institutions

47

Chains observed

Base

Section 01 · the constraint

It cannot move funds. That is the entire product.

Most fintech mobile applications must defend a perimeter that includes the ability to move money. LightRain has no such perimeter, by construction. The application is signed, but it does not sign. The application reads, but it cannot write. The Read API it consumes physically does not implement write endpoints; the execution backend that holds the keys lives on a separate VPC with no peering, no shared identity, no path through which a compromised phone could reach it.

  • cannot execute trades

  • cannot trigger smart contracts

  • cannot initiate flash loans

  • cannot sign transactions

  • cannot custody funds

  • cannot connect a wallet for execution

  • cannot modify on-chain state

The worst case for a stolen device is data exfiltration of positions the attacker is supposed to see.

Section 02 · the stack

Four systems. One pane of glass.

Execution layer · Base

01 · execution

Base

Coinbase's Layer 2, where every flash loan, credit position, and strategy router call originates. Outside the application entirely.

USDC native · 2s blocks · sequencer-protected

Truth layer · PIOL

02 · truth

PIOL

The Proof of Integrity and Off-chain Linkage oracle. Reconciles on-chain reality against modeled expectation. Signed by an attester quorum, three of five required.

Hybrid · multi-sig · on-chain attested

State layer · MongoDB

03 · state

MongoDB

The application's working memory. Positions, executions, reconciliations, alerts, watchlists, session state. Hydrated by indexers, by the Snowflake materializer, and by PIOL.

Document-shaped · change streams · sub-second

Risk warehouse · Snowflake

04 · risk

Snowflake

Where the heavy lifting of risk modeling happens. Backtests, attribution, counterparty exposure, compliance extracts. Materialized into Mongo on a schedule the user never sees.

Marts updated 15-minute · jobs queued

Each layer does exactly one thing. The boundaries are architectural, not procedural.

Section 03 · data flow

One direction. No exceptions.

An on-chain event becomes a row in Mongo within a second. PIOL reconciles it against Snowflake's model output and emits an attested integrity score. The application reads what is already settled. Nothing the user does inside LightRain produces a write to any system that holds capital.

LightRainLightra Read APIMongoDBBase indexerSnowflake materializerPIOL oracleBaseSnowflake warehouseAttester quorumTrust boundaryBackend execution systemBase

Section 04 · what you see

Four surfaces. One language.

LightRain ships with four feature surfaces, one tab each. The visual language across all four is the same: black ink on white surface, hairline rules, dense typographic hierarchy, no decorative chrome. Color is reserved for state, never for decoration.

Tab 01

Portfolio Visibility

Where the money stands, right now. Open credit positions with health factors and distance to liquidation. Liquidity exposure by strategy, sortable by deployed notional or by oracle-derived risk score. Historical execution logs paginated and filterable. A net-exposure summary that walks the strategy specs and tells you how much of each underlying asset you are actually long.

  • Open positions table

  • Strategy exposure with risk bars

  • Execution log with on-chain hash linking

  • Net exposure rollup

  • BaseScan deep links

Tab 02

Strategy Analytics

Where Snowflake earns its keep. Backtests of strategy specifications against historical Base state. Simulated flash loan outcomes scrubbed minute by minute through the last 24 hours. Routing efficiency metrics — slippage versus quote, gas versus simulation, pool distribution. Oracle-derived risk score broken into its five subscores. Comparative performance across up to three strategies on one chart.

  • Backtest viewer

  • Simulated flash loan outcomes

  • Routing efficiency

  • Oracle risk score components

  • Comparative overlay

Tab 03

Oracle Transparency

The trust layer made visible. A composite system trust score updated continuously. The reconciliation feed with every event tagged by integrity score. The on-chain-versus-modeled scatter plot where clusters off the diagonal tell a regulator a different story than alignment does. The audit trail viewer that walks any single financial action through its entire lifecycle from indexer to phone.

  • System trust score

  • Reconciliation feed

  • Alignment scatter

  • Audit trail viewer

  • Mismatch subscriptions

Tab 04

Alerts

The inbox. Push notifications delivered through APNs persist as a searchable record regardless of whether the lock-screen push was dismissed. Liquidation risk, strategy failure, collateral health velocity, oracle mismatch, unusual exposure. Every alert deep-links to its detail surface. No alert offers an action button beyond view, because there are no actions to offer.

  • Liquidation risk thresholds

  • Strategy divergence alerts

  • Health factor velocity

  • Oracle integrity floors

  • APNs persistent inbox

Section 05 · the application

Built native. Rendered black on white.

LightRain is a native SwiftUI application. Charts are Swift Charts, not embedded web views. Data flows over GraphQL with WebSocket deltas. The interface respects the system at every level — Face ID gates launch, sensitive views require re-authentication, Dynamic Type and accessibility settings apply throughout.

01 · live deltas / WebSocket

GraphQL subscription channel

graphql-ws · gzip

02 · Face ID gated / on-device

Biometric session boundary

LAContext · secure enclave

Section 06 · trust

The perimeter is read. Nothing more.

Stolen device

No path to keys

The application has no signing capability and no transport to any system that signs. A stolen, unlocked device exposes read access to data the legitimate user could already see.

Compromised credential

No write to promote

A phished session yields read access. There is no write authority at the API layer to escalate into. The Read API runs on hosts with no network path to the execution backend.

Mongo corruption

Truth lives upstream

Mongo is working memory, not source of truth. Source of truth on-chain is Base, source of truth analytical is Snowflake. Corruption surfaces as a PIOL divergence within the next reconciliation window.

PIOL attester

Three of five required

Single attester compromise cannot produce valid signatures. Attesters are economically bonded; sustained malicious behavior loses staked capital, not protocol funds.

Side-loaded build

Read API refuses

A malicious binary talking to the legitimate API still cannot move funds because the API does not implement writes. A binary talking to a malicious API is a phishing attack on read data.

Network boundary

VPCs do not peer

Read API and execution backend live in separate VPCs with no peering. The execution backend's outbound policy explicitly denies the Read API's IP range. Architecture, not policy.

Section 07 · who this is for

Built for the people who watch, audit, and verify.

Funds

Allocators and PMs at crypto-native funds who need real-time visibility into protocol exposure without trading authority on the same surface. LightRain installs on every analyst's phone without touching the firm's signing infrastructure.

Auditors

External and internal auditors who need an attested, exportable, time-stamped record of every reconciliation event. The audit trail viewer is the artifact auditors will demand and that LightRain delivers without configuration.

Compliance

Regulators and compliance officers who need to see the protocol's posture without privileged access. Read-only is not a limitation here. It is the premise of the institutional relationship.

Section 08 · la maison

About the house.

LightRain is operated by Hated By Many LLC as a narrow institutional surface: read-only observability over the execution stack on Base. The house does not distribute keys through an app store posture, and it does not pretend the phone is a signing device. The product is the ledger of what already happened, rendered with latency low enough to matter in a close.

We work with counterparties, allocators, and audit firms who need the same facts on the desk and in the file. Correspondence is deliberate. There is no self-serve queue because the relationship is the perimeter: you either fit the mandate or you do not.

Read-only is not humility. It is structural law: the eyes of the stack, never the hands.
Note d'intention, LightRain protocol

If you are evaluating the stack, start with architecture and trust. If you are already inside the relationship, the application is the glass through which the house shows its work.

Correspondence

  • Operated by

    Hated By Many LLC

  • Domicile

    Texas, United States

  • Chain posture

    LightRain execution on Base

  • Client surface

    Signed iOS observability only

press@lightra.inpartnerships@lightra.in

Chapitres

Parcours du protocole

Chaque salle ouvre une lecture longue — figures, spécifications, et discipline de la maison.

§ 11 — Dossier · the protocol's papers

Specifications, audits, correspondence.

« Tout est public. Tout est daté. Tout est signé. »