Risk travels.
Signals don't. Until now.
Cross-chain risk intelligence, powered by OmniRisk
RayaChain is a canary layer — an early warning network that moves context across chains, not just assets. OmniRisk produces the signals. RayaChain distributes them. Analysis happens once. Awareness becomes available network-wide.
Three signal types,
one canary layer.
The infrastructure for moving value cross-chain is mature. The infrastructure for moving meaning is almost non-existent. RayaChain fills that gap — an interpretation layer that adds risk and credit semantics to cross-chain transport so downstream protocols can act on context, not just balances.
Sudden deleveraging, rapid cross-chain movement, repayment pattern changes. A wallet that unwinds a leveraged position on Base and bridges to Arbitrum looks new to Arbitrum — but the signal existed on Base. RayaChain broadcasts it before the next position opens.
See the broadcast →Liquidity instability, collateral stress, abnormal usage within a protocol — OmniRisk scores these before they surface in price. RayaChain distributes the score so lending protocols and vaults can adjust dynamically.
See live route health →Correlated withdrawals across protocols, unusual bridge flows, coordinated deleveraging — patterns that no single chain can observe alone. Risk is a data type, not a vibe.
Subscribe to the feed →Move value without moving blind.
A single unified transfer surface. Connect your wallet, choose source and destination, and get a route-aware quote with the full risk picture before you sign.
- → Route-aware quoting
Prices reflect the route, not a model average.
Liquidity, latency, and validator set are priced in at quote time.
- → In-flight re-routing
If conditions change mid-transfer, so does the path.
RayaChain can hold, split, or re-route a transfer based on broadcast signals.
- → Wallets you already use
MetaMask, Rabby, Phantom, WalletConnect, Ledger.
No new signing ceremonies. No new trust assumptions.
Every pair. Every second. Public.
Route Health is a public dashboard of every chain-pair RayaChain serves. Latency, liquidity depth, validator health, historical incidents — instrumented and open.
We publish the numbers that decide your route.
Route Health is not a marketing dashboard. It's the same data the RayaChain router uses to make quoting decisions. If it's degraded, you'll see it before the router does.
The feed that doesn't wait for an exploit.
OmniRisk observes 600+ protocols for anomalous behaviour. RayaChain broadcasts those signals — versioned, signed, and subscribable — so any contract, router, or vault can react before the incident is on Twitter.
Risk is a data type, not a vibe.
Each broadcast has a schema, a severity, an affected surface, and a confidence score. You don't subscribe to "Twitter-grade" rumours — you subscribe to topic channels with hard semantics.
oracle.deviationprice feed drift > σ thresholdbridge.latencysettlement time exceeds p99validator.churnunusual exit rate on a light-clientcontract.drainTVL anomaly with directional flowgov.capturegovernance quorum riskNot a governance token. A coordination primitive.
RYA is the unit of account for route pricing, the collateral for risk-broadcast validators, and the settlement asset for cross-chain rebalances. Its supply is unified, its utility is mechanical, not rhetorical.
Three lines to move value. Zero lines to listen to risk.
The SDK is deliberately small. Transfers, quotes, and a broadcast subscription. If you already know how to call an RPC, you already know how to use RayaChain.
// Route-aware transfer across 7 chains import { raya } from '@rayachain/sdk' const quote = await raya.quote({ from: 'base', to: 'solana', asset: 'RYA', amount: 12_500n, }) // quote.risk = { score: 12, grade: 'A' } // quote.eta = 38s await raya.transfer(quote, { signer })
// Subscribe to typed risk signals import { broadcast } from '@rayachain/sdk' broadcast .topic('oracle.deviation') .filter({ chain: 'arbitrum', minSev: 2 }) .on('signal', (s) => { // s.severity, s.surface, s.confidence vault.pauseIf(s.confidence > 0.85) })
The short answers.
Longer ones live in the documentation. The team also hosts an open office hour every Thursday.
01Is RayaChain a bridge?+
No. RayaChain uses LayerZero OFT as transport for RYA, but that's infrastructure, not the product. The product is the interpretation layer on top — risk and credit semantics produced by OmniRisk, structured and scored, ready for downstream protocols to act on. A bridge moves tokens. RayaChain moves context.
02How is RYA supply unified across 7 chains?+
There is no wrapping. RYA on every chain settles against a single canonical supply maintained by a light-client set. When you move RYA from Base to Solana, the global supply is unchanged — only the chain-local balance shifts.
03Who decides what counts as a risk signal?+
OmniRisk publishes the schema and severity criteria openly. Signals are signed and versioned, and the set of monitored surfaces is an on-chain list anyone can propose additions to. Consumers choose which topics and severity thresholds they care about.
04What wallets are supported?+
MetaMask, Rabby, Frame, WalletConnect v2, Phantom, Backpack, and Ledger via WebHID. For institutions: Fireblocks, Safe, and GK8 via the raya-enterprise SDK.
05Is this audited?+
Contracts are audited by Spearbit and Trail of Bits. Route Health data is independently mirrored by two archival nodes. The risk broadcast set is open-source on GitHub.