Legal Entity & Corporate Structure
Operating company
Protocol vs. application distinction
Tokenless architecture
Offshore components
Jurisdiction & Applicable Law
Governing law
Jurisdiction check — how we determine eligibility
- 01.IP geolocation cross-referenced against a maintained blocklist of sanctioned and restricted territories;
- 02.Counterparty self-certification of legal domicile, entity type, and regulatory classification;
- 03.OFAC SDN list screening via an accredited third-party compliance vendor;
- 04.KYC/KYB review by licensed compliance personnel, including document verification and beneficial ownership mapping;
- 05.Ongoing transaction monitoring for patterns inconsistent with stated counterparty profile.
Restricted territories
Dispute resolution
Eligibility & Who Qualifies
Qualified users
- 01.Accredited investors as defined under Rule 501(a) of Regulation D promulgated under the U.S. Securities Act of 1933, as amended;
- 02.Qualified purchasers as defined under Section 2(a)(51) of the U.S. Investment Company Act of 1940;
- 03.Institutional counterparties including registered investment advisors, hedge funds, family offices, and corporate treasuries with verified AUM exceeding $10 million;
- 04.Non-U.S. persons accessing the protocol pursuant to Regulation S under the Securities Act, subject to additional jurisdiction screening;
- 05.DAO treasuries with verified multi-signature governance and formal resolution authorizing access, subject to enhanced due diligence.
Verification process
Representations by users
Regulatory Framework
U.S. regulatory posture
FinCEN / BSA compliance
EU / MiCA considerations
OFAC compliance
Travel Rule
Risk Disclosures
The following risk disclosures are provided pursuant to applicable law and best practices for digital asset service providers. This list is not exhaustive. Users should consult independent professional advisors.
01
Smart contract risk
Smart contracts may contain undiscovered vulnerabilities. Two independent security audits have been completed and results are publicly available, but no audit guarantees the absence of exploitable defects.
02
Liquidity risk
Flash liquidity is sourced from third-party liquidity pools, principally Aave v3. Pool depth, utilization, and availability may fluctuate. Transactions that cannot be fulfilled atomically will revert.
03
Oracle risk
Price and reputation data is sourced from Chainlink and Uniswap v3 TWAP feeds. Oracle manipulation, latency, or failure could result in incorrect liquidation or pricing outcomes.
04
Regulatory risk
The regulatory environment for digital asset protocols is rapidly evolving. Changes in law or regulatory interpretation may materially restrict or prohibit access to the protocol in certain jurisdictions.
05
Counterparty risk
Credit lines and collateralized positions carry counterparty risk. LightRain's credit vault does not guarantee repayment. Liquidation proceeds may be insufficient to cover outstanding positions in extreme market conditions.
06
Operational risk
Protocol upgrades, sequencer downtime on Base, or infrastructure failures may temporarily render the protocol inaccessible. The Company maintains operational incident procedures but cannot guarantee uninterrupted service.
Privacy & Data Protection
Data collected
Data use
Retention
CCPA / California rights
Intellectual Property
Ownership
Open protocol
Trademarks
Investor Relations
No public offering
Reporting cadence
Correspondence
Legal Correspondence
General legal
legal@lightra.inCompliance & regulatory
compliance@lightra.inPrivacy & data
legal@lightra.inSecurity disclosures
security@lightra.inInvestor relations
investors@lightra.inPress & media
press@lightra.inRegistered address
Hated By Many LLC
Texas, United States of America
« Tout est public. Tout est daté. Tout est signé. »
Version 2026.05 · Hated By Many LLC · Texas