Figment vs Radiant Capital

Figment delivers staking-as-a-service infrastructure designed specifically for institutional asset managers, exchanges, custodians, and decentralized protocol foundations. The platform maintains active, monitored validator nodes across more than thirty leading proof-of-stake protocols, encompassing major networks such as Ethereum, Solana, Polkadot, Avalanche, Near, and various Cosmos application chains. Organizations can deploy dedicated private validator nodes or direct delegations toward public enterprise clusters depending on balance size and architectural preferences.

Beyond standard bare-metal validator operations, Figment equips institutional engineering teams with developer tooling, including robust API endpoints and webhooks for automated staking, validator lifecycle tracking, and programmatic rewards harvesting. The Figment App serves as a centralized operational dashboard, offering institutional clients granular visibility into active stakes, historical reward distributions, commission deductions, and node uptime metrics across multi-chain portfolios.

For enterprise platforms embedding staking into consumer or custodial products, Figment acts as the underlying execution layer. Custody providers and financial institutions integrate Figment staking infrastructure directly into their existing custody environments without transferring control of funds, maintaining a clean technical separation between key storage and transaction validation.

Radiant Capital operates as a decentralized, non-custodial money market that leverages LayerZero messaging formats to facilitate omnichain borrowing. Instead of restricting collateral and loan origination to a single isolated network, Radiant enables a user to deposit a supported blue-chip token on one chain, such as Arbitrum, and borrow an entirely different asset on another network, like Ethereum mainnet or BNB Chain. This architecture aims to reduce the friction, execution delays, and bridge wrapping steps typically associated with moving assets manually between separate decentralized finance ecosystems.

The asset catalog focuses primarily on high-liquidity foundational tokens. Supported collateral and borrowable assets commonly include stablecoins such as USDC, USDT, and DAI, alongside major cryptocurrencies including wrapped Bitcoin, wrapped Ethereum, and native network tokens. Each asset pool operates with distinct risk parameters, loan to value ratios, and liquidation thresholds determined by governance models. The primary utility and governance asset, RDNT, functions alongside the core money markets to distribute protocol fee shares to users who lock dynamic liquidity pairs, establishing an incentive layer that supplements standard pool utilization interest.

Figment utilizes a protocol commission model where fees are typically deducted directly from gross on-chain staking rewards rather than invoiced as flat monthly infrastructure costs. Standard protocol commission rates vary across supported blockchains, reflecting individual network tokenomics, hardware requirements, and custom client volume tier agreements. For dedicated institutional validator clusters, customized fee agreements or software-as-a-service infrastructure fees may apply depending on technical configuration, custom service level agreements, and support requirements.

Because Figment does not custody digital assets, all principal deposits and generated staking rewards settle directly to client-controlled wallet addresses or whitelisted institutional custody accounts according to protocol rules. Figment does not apply proprietary withdrawal charges, spread markups, or liquidity exit penalties beyond native network transaction fees and protocol commission percentages agreed in enterprise contracts.

Yield realization timelines, unbonding schedules, and payout frequencies depend strictly on the underlying network protocol mechanics. For instance, Ethereum rewards distribute on-chain according to consensus rules, while networks like Cosmos or Polkadot enforce native unbonding windows ranging from two to four weeks. Stakers must account for these native blockchain rules when modeling portfolio liquidity.

Fees on Radiant Capital are fundamentally algorithmic, reflecting real-time supply and demand dynamics across individual asset pools. Suppliers earn variable interest rates driven by pool utilization, meaning rates rise automatically as borrowing demand increases. Borrowers pay variable interest rates corresponding to the utilization curve of the borrowed pool. In addition to variable base interest rates, transactions on Radiant require native blockchain gas fees on the originating and destination chains to execute smart contract operations and LayerZero cross-chain messages.

To access RDNT emission rewards and receive a share of protocol platform fees, participants must interact with the Dynamic Liquidity Provision mechanism. Users lock liquidity pool tokens, typically RDNT paired with ETH or BNB, representing at least a specified percentage of their total supplied collateral value. Protocol revenue generated from borrower interest and liquidation penalties is distributed to eligible locked liquidity providers in primary assets like stablecoins and native tokens. Withdrawing supplied liquidity remains non-custodial and flexible, provided the user maintains an account health factor safely above the liquidation threshold, while locked liquidity tokens remain subject to predefined vesting and locking terms.

Security architecture at Figment centers strictly on non-custodial operations, ensuring that clients retain full ownership and administrative control over their cryptographic private keys and staking withdrawal credentials at all times. Figment operates validation nodes and signs blocks on behalf of delegators, but never maintains access to funds or holds authorization to transfer principal assets out of client-managed custody vaults.

To mitigate technical and operational vulnerabilities, Figment maintains independent SOC 2 Type II compliance and ISO 27001 certifications covering its infrastructure management and operational workflows. Node deployment utilizes distributed cloud and bare-metal environments across diverse geographical data centers, incorporating robust hardware security modules, multi-region failover, and active anti-DDoS mitigations to sustain high validator uptime and prevent double-signing events.

Figment provides commercial slashing coverage policies for eligible institutional clients, designed to protect against potential financial losses resulting from validator downtime penalties or accidental infrastructure errors. While these operational measures significantly diminish technical failure risks, delegators still operate within the broader regulatory and software failure risks inherent to public distributed consensus protocols.

Because Radiant Capital is an autonomous decentralized finance protocol, custody of deposited funds remains governed entirely by smart contracts rather than a centralized intermediary. Users retain self-custody through their connected Web3 wallets, interacting directly with open-source smart contract pools. The protocol relies heavily on LayerZero omnichain messaging contracts to track balances, collateral ratios, and cross-chain execution states. This multi-layered architecture introduces composite risk, as security depends not only on Radiant core contracts but also on external bridging infrastructure and network oracles.

To manage operational risk, Radiant implements automated liquidation mechanisms supported by third-party price oracles like Chainlink. When collateral values drop or accrued interest pushes an account health factor below the liquidation threshold of 1.0, external liquidators can repay a portion of the notable debt in exchange for seized collateral at a liquidation penalty discount. Users must proactively monitor collateral ratios through self-directed controls and alerts, particularly during periods of steep market volatility. Smart contracts undergo external security reviews, yet interaction inherently involves risk exposure to potential software bugs, oracle latency, and cross-chain messaging vulnerabilities.

Headquartered in Canada and operating globally, Figment structures its products to comply with international enterprise standards, serving hedge funds, venture funds, registered investment advisers, public companies, and global fintech institutions. The company maintains strict enterprise onboarding workflows, executing standard Know Your Customer and anti-money laundering due diligence before provisioning dedicated validator infrastructure or enterprise API services.

Customer support for enterprise clients includes dedicated technical account managers, specialized integration engineers, and around-the-clock infrastructure monitoring. Service level agreements provide intended to provide response times, proactive incident notifications, and scheduled operational reviews, catering specifically to institutional expectations that standard retail community channels cannot satisfy.

Comprehensive tax and accounting support represents a core component of the platform. Figment provides downloadable, auditable reporting tools that export reward histories, cost-basis calculations, and protocol event logs in formats compatible with major institutional crypto accounting platforms, easing quarterly financial reporting and internal audit requirements for corporate treasuries.

Access to Radiant Capital is permissionless at the smart contract level, enabling users globally to connect compatible Web3 wallets directly to the decentralized application. However, the user interface hosted on web domains may apply geographic restrictions or screening policies to comply with regulatory standards across specific jurisdictions. Users are solely responsible for ensuring that their use of decentralized lending products aligns with local financial laws, tax reporting mandates, and token trading regulations in their home region.

Customer support on Radiant follows standard decentralized finance conventions, functioning primarily through community-driven channels rather than dedicated enterprise help desks. Assistance is available through structured documentation, community forums, and official communication platforms such as Discord. Because the protocol is autonomous and non-custodial, support staff and community moderators cannot intervene in transactions, reverse failed transfers, recover lost private keys, or alter liquidation outcomes. Users are expected to maintain technical proficiency regarding transaction signing, gas estimation, slippage tolerances, and self-custody wallet management before executing complex omnichain loan positions.

Delegating to Figment validators mitigates operational node failure risks through enterprise-grade DevOps, but it does not eliminate systemic blockchain network vulnerabilities. All proof-of-stake delegators remain exposed to smart contract bugs, sudden hard forks, and native protocol governance changes that could alter yield rates or unbonding periods. While Figment provides commercial slashing protections under qualified institutional contracts, such policies cover specific operational faults rather than market-wide asset depreciation or underlying blockchain consensus failures.

Organizations must evaluate native protocol lockup schedules and liquidity constraints before allocating balance sheet capital. Figment maintains redundant failover infrastructure and continuous monitoring to prevent validator double-signing and downtime penalties, yet market participants should account for protocol-level slashing conditions that arise from broader decentralized network events outside validator operational control.

Participating in cross-chain money markets involves distinct risk layers beyond standard single-chain decentralized lending. Radiant Capital interacts with cross-chain communication relays, decentralized oracles, and multiple blockchain virtual machines simultaneously. A software fault, oracle mispricing, or exploit within any connected layer can impact pool solvency. The decentralized nature of the protocol means there are no government deposit protections, insurance schemes, or centralized chargeback mechanisms. Collateral positions carry continuous market risk, where sudden market downturns can trigger swift liquidations before a user can bridge additional funds or repay notable balances. Users must carefully manage position sizing and maintain conservative collateralization buffers to mitigate unexpected liquidation events.