Whitepaper
Conceptual security model in plain language—not a substitute for technical documentation, penetration tests, or your own threat modeling. Use this page to understand how we talk about safety and control before you dive into implementation detail.
Your sign-in and device posture are designed around you controlling the session—not a distant account warehouse that can be reset by a bored support agent. Strong onboarding and recovery exist precisely so you stay in charge.
Keys and signing policy are yours to configure within the product’s model. LightRain does not present itself as a custodial omnibus where “we” move funds on your behalf without your explicit operator actions.
Recovery is described in terms of passphrases, backup codes, hardware keys, and encrypted files you hold—not a single reset button that bypasses everything you set up.
The architecture narrative assumes segregated, attributable flows—not a black pool where customer balances are merged in a way that obscures who owns what on-ledger.
We do not market omnibus settlement as a consumer wallet feature. If your deployment involves omnibus structures, that is a licensed-entity design conversation—not a default LightRain consumer story.
Delegation and policy are meant to be visible in the product story: who can sign, what limits apply, and what history exists. “Magic” routing that moves value without a clear actor is contrary to the posture this page describes.
© 2026 Hated By Many LLC. All Rights Reserved