An Ethereum-based protocol delivering continuous, on-chain security risk feeds for DeFi infrastructure. It transforms fragmented off-chain security data into composable oracle feeds that protocols consume programmatically.
RLAR does not adjudicate truth. It constructs transparent, on-chain confidence metadata for systems operating on external data.
Immutable on-chain security data registration. Auditors, security researchers, and protocol teams submit structured entries: audit report hashes, deployment metadata, dependency maps, admin key configurations, incident disclosures.
Each submission requires an RLAR token stake as collateral. Records are permanent and tamper-proof. Inaccurate submissions result in stake slashing and redistribution to challengers.
Aggregates registered security data into dynamic, per-contract Risk Scores through automated on-chain computation and optimistic validation.
Base scores derived from quantifiable on-chain signals: contract age, audit coverage, admin key configuration, upgrade history, and dependency risk propagation. Off-chain data incorporated through optimistic ingestion with stake-backed challenge periods.
Scores decay toward lower confidence without new data — rewarding continuous audit coverage.
DeFi protocols consume RLAR risk feeds directly within smart contract logic through subscription-based access denominated in RLAR tokens.
Adjust liquidation thresholds and borrow caps automatically based on collateral Risk Score changes.
Filter vault strategies by minimum security score, excluding protocols below threshold.
Consume Risk Score history to calculate premiums and automate policy issuance.
Display security warnings at the point of transaction signing.
Fixed hard-cap supply. No inflation. No future minting. All revenue generated from oracle subscription fees paid by integrating protocols.
Revenue allocated across protocol buyback and permanent burn, data submitter rewards, validator compensation, and governance-controlled treasury.
Submitters and validators stake RLAR tokens, subject to slashing. Buyback tokens permanently burned — every burn is a net supply reduction with no dilutive offset.
Integrate security-aware infrastructure into your protocol.