What Is Radiant (RDNT)? The Cross-Chain Lending Token

Radiant Capital is a cross-chain lending protocol designed to unify liquidity across multiple networks and make borrowing and lending seamless across chains. Its native token, RDNT, sits at the center of an “omnichain” architecture powered by LayerZero messaging, enabling deposits on one chain and borrow actions that can settle on another. As cross-chain interoperability moves from experimental to mainstream in 2025, Radiant’s approach offers a pragmatic path to composable DeFi without forcing users to manually bridge assets every time they want to borrow or repay.

This guide explains how Radiant works, what RDNT does, the risks to consider, and how self-custody fits into a cross-chain strategy.

Key Concepts: Omnichain Money Markets

Traditional lending markets are siloed on single chains. If you deposit collateral on Arbitrum, you generally borrow on Arbitrum. Radiant instead targets “omnichain” liquidity:

• Users supply assets on supported networks and accrue yield.
• Borrowers can receive liquidity on different chains while their debt remains secured by collateral where it was deposited.
• Cross-chain messages and liquidity transfers are powered by LayerZero and Stargate, two widely used interoperability primitives (see LayerZero docs and Stargate for technical background).
  References: LayerZero Docs, Stargate

Radiant launched on Arbitrum and expanded to BNB Chain, prioritizing high-throughput EVM environments with deep liquidity and fair fees. You can explore the live markets and supported assets via the Radiant app and documentation.
References: Radiant App, Radiant Docs

How Radiant Works

• Supply and borrow markets: Users deposit blue-chip assets (e.g., ETH, WBTC, stablecoins) to earn interest. Borrowing rates dynamically adjust by utilization and risk parameters, similar to other money markets.
  Reference: Radiant Docs

• Cross-chain actions: When borrowing “to” another chain, Radiant routes liquidity using Stargate liquidity pools while coordinating state via LayerZero’s messaging. This allows the protocol to maintain accurate debt accounting and liquidation logic on the collateral chain, while users receive funds on their chosen destination network.
  References: LayerZero Docs, Stargate

• Price oracles: Protocols like Radiant typically rely on decentralized oracle networks for asset pricing. Chainlink is a common choice across DeFi for robust, tamper-resistant feeds.
  Reference: Chainlink Price Feeds

RDNT: Utility, Emissions, and Omnichain Design

RDNT is Radiant’s native token, implemented as an Omnichain Fungible Token (OFT) so it can move across supported chains without relying on wrapped representations.
Reference: LayerZero Docs

RDNT’s roles and tokenomics:

• Emissions and incentives: Suppliers can earn RDNT incentives, subject to sustainability constraints and protocol-defined requirements. Radiant’s v2 tokenomics introduced mechanisms to reduce mercenary liquidity and incentivize long-term alignment, including locking models tied to protocol fees.
  Reference: Radiant Docs

• Fee sharing: A portion of protocol fees may be distributed to long-term participants who lock as specified by governance. This can include real-yield components (e.g., ETH or stablecoins) rather than only inflationary token emissions, aiming to improve capital efficiency over time.
  Reference: Radiant Docs

• Governance: RDNT holders can participate in governance processes that shape market parameters, listing decisions, emissions schedules, and chain expansions. Active proposals are typically managed on Snapshot.
  Reference: Radiant Governance on Snapshot

For market data and liquidity trends, consult third-party analytics to cross-verify TVL and activity:
Reference: DefiLlama – Radiant

To understand RDNT’s circulating supply, listings, and historical performance, use reputable aggregators:
Reference: CoinMarketCap – Radiant (RDNT)

Supported Networks and Assets

Radiant currently operates on Arbitrum and BNB Chain, with asset lists curated to balance demand and risk. Supported assets can vary by chain based on liquidity depth, oracle coverage, and governance decisions. Always verify current chain support and asset caps directly in the official app and docs.
References: Radiant App, Radiant Docs, Arbitrum, BNB Chain

Fees, Rewards, and User Flows

• Supply APY: Earn interest from borrowers plus potential RDNT incentives if eligibility criteria are met.
• Borrow APR: Pay variable rates. Cross-chain borrowing can incur additional bridging fees and slippage.
• Locking models: Long-term locks can qualify users for fee sharing and improved emissions, but introduce liquidity trade-offs. Review lock durations, penalties, and vesting carefully in the docs.
  Reference: Radiant Docs

Risks to Consider

• Cross-chain risk: Bridges and message layers expand a protocol’s attack surface. Security assumptions differ from single-chain designs. Vitalik’s canonical write-up on cross-chain security trade-offs is worth reviewing.
  Reference: Vitalik on Cross-Chain Risks

• Oracle risk: Manipulated prices can lead to bad debt or cascading liquidations if not adequately mitigated. Rely on assets with robust liquidity and proven oracle coverage.
  Reference: Chainlink Price Feeds

• Liquidation risk: Borrowing against volatile collateral can trigger liquidations during market stress. Maintain healthy buffers, monitor health factors, and avoid over-leverage.

• Tokenomics and emissions: Incentive structures can change via governance. Short-term yield strategies may underperform if lock requirements or emission rates evolve.
  Reference: Radiant Governance on Snapshot

• Smart contract risk: Even audited protocols can face unforeseen vulnerabilities. Review recent audits, disclosures, and post-mortems; diversify across protocols and chains where appropriate.
  Reference: Radiant Docs

2025 Context: Cross-Chain Moves From Novelty to Norm

In 2025, the industry’s focus has shifted from “which chain?” to “how well does it compose across chains?” The maturation of interoperability stacks and broader liquidity on L2s created conditions for omnichain money markets to scale. For users, this means:

• Fewer manual bridges: You can borrow on a destination chain while keeping collateral where it’s most liquid.
• Improved UX: Debt accounting and risk management remain intact, while liquidity routing is handled under the hood.
• Governance-led expansion: Chain support and asset listings tend to progress through community proposals. Stay updated via governance portals and official docs.
  References: Radiant Docs, Radiant Governance on Snapshot

Getting Started

• Choose your chain: Arbitrum or BNB Chain, based on fees and liquidity for your target assets.
  References: Arbitrum, BNB Chain

• Supply collateral: Pick liquid, well-oracled assets. Review supply caps, collateral factors, and borrow limits.
  Reference: Radiant Docs

• Borrow across chains: If you need liquidity elsewhere, explore cross-chain borrow routes in the app UI. Confirm any additional fees.

• Manage risk: Monitor health factor, consider partial repayments during volatility, and set alerts.

Self-Custody and Security: Why It Matters

Cross-chain strategies add complexity. Protecting private keys and minimizing signature risk is a must, especially when interacting with multiple networks and bridges.

If you hold RDNT or interact with Radiant on Arbitrum or BNB Chain, a hardware wallet can materially improve your security posture. OneKey is an open-source, multi-chain hardware wallet that integrates smoothly with popular EVM workflows, supports Arbitrum and BNB Chain, and is designed to keep your private keys offline while you sign transactions. For users actively managing collateral and borrow positions across chains, one-click confirmations and clear transaction prompts help reduce mistakes during complex operations.

Final Thoughts

Radiant (RDNT) targets a key DeFi pain point: fragmented liquidity and clunky bridging. By combining money markets with omnichain messaging, it lets users retain collateral on one chain while borrowing on another. As with any cross-chain system, success depends on robust risk controls—sound oracles, careful liquidation design, and resilient messaging and bridge infrastructure.

Before supplying or borrowing, read the official documentation, examine governance updates, and track liquidity trends. And if you’re going to hold RDNT or manage positions across chains, consider using a hardware wallet like OneKey to keep your keys offline and reduce operational risk when interacting with omnichain protocols.
References: Radiant Docs, Radiant App, LayerZero Docs, DefiLlama – Radiant, CoinMarketCap – Radiant (RDNT)