Frequently Asked Questions

What is Radiant Capital?

Radiant aims to be a "one-stop shop" money market, where users can deposit & borrow assets across multiple chains, seamlessly.

The Radiant DAO utilizes the native utility token, $RDNT. By interacting and providing utility to the platform, users can capture the added value from the communities’ engagement through the native utility token $RDNT from borrowers and platform fees

Where are the verified contracts and were they audited?

The verified contracts may be viewed here.

Radiant Capital is audited by Blocksec, PeckShield, and Zokyo. No critical or major security flaws were found.

Was there a seed round, presale or VC investment?

Funding for Radiant was bootstrapped entirely by the core contributors. All expenses have been paid out-of-pocket: development, multiple audits, marketing, salaries etc.

There was no private sale, IDO, or VC involvement, which aligns with our ethos of decentralization with no bias.

Why is my health factor declining on borrowed assets?

Borrowed assets accrue interest that is paid from deposited collateral. Over time, this may lower one’s health factor.

It is recommended to monitor your health factor and ensure it stays above 1. Deposit more funds or repay loans to increase your health factor and avoid liquidation.

For more information, please review the Health Factor page.

What is looping & locking and what is the process to unwind a loop?

Looping is an automated process that provides an opportunity to earn a yield on a greater collateral value by repeating the deposit and borrow function with up to 4x leverage.

The loop and lock function of Radiant may not execute if the selected leverage would cause your health factor to drop below 1.11. If the loop transaction fails to execute, lower your leverage using the sliding scale.

Additionally, the loop & lock feature automatically ensures dLP eligibility. If a user is already eligible, zero ETH will be borrowed. As you can see in the video below, there will be zero ETH borrowed if a user is NOT required to add more dLP.

If a user is ineligible for RDNT emissions, the loop & lock tool will automatically borrow the ETH necessary to zap into a locked dLP position to maintain the minimum 5% dLP requirement for activating RDNT emissions. Slippage is fixed at 5%. If a user wishes to reduce slippage, it is recommended to manually create dLP by visiting the Balancer Pool directly.

Lastly, the dLP will be locked for your Default Locking Length, which can be updated under the Manage page.

Unwinding a loop is a manual process that requires the repayment of outstanding loans. This may require a few cycles of withdrawing deposited collateral to repay the loan while ensuring your health factor remains above 1. Alternatively, deposit more collateral, improve your health factor, then begin the manual unwind process.

What is the difference between vesting and locking RDNT?

RDNT emissions from lending and borrowing must undergo a 90-day vesting process.

Users must actively initiate the vesting period in the “Manage Radiant” section.

Users can claim their vested RDNT early for a 25-90% exit penalty at any point during the vesting process. Remember that you can not partially exit early– all currently vesting RDNT will be withdrawn with their respective exit penalties applied.

Locked RDNT liquidity providers receive 60% of protocol fees and cannot be unlocked until the locking period has ended.

For a full breakdown, visit the Manage Radiant section of the GitBook.

What is zapping dLP?

Zapping allows you to form a locked RDNT liquidity position in one click using RDNT and ETH/BNB in your wallet, or borrowed from the money market.

How is daily revenue distributed?

Platform fees are distributed linearly over a 7-day period as they are earned.

Daily revenue will fluctuate based on platform fees (borrowers paying interest on loans) and flash loan fees.

How is "Max dLP Lock APR" calculated from the Markets page?

How is the "Maximum Lock APR" calculated? - Definition: Maximum APR when dLP is locked for 1 year - Calculation: 1 month lock APR * 1 year lock multiplier (25x)

Example: 1 month locking APR: - Definition: Current locking APR for 1 month - Calculation: (Total 1 Month Lockers’ Share of Annualized Protocol Fees) / (Total 1 Month Lockers’ Share of dLP Pool Size)

How is "Your Share" of dLP calculated?

(User share of dLP * user avg. dLP Multiplier) / (Total Protocol dLP * Global Protocol avg. multiplier)

How is "Average Multiplier" for locked dLP calculated?

The average multiplier is based on your lock length selected each time you perform a lock/relock or zap/auto-compound into dLP.

Calculation: For example, User 1: - Total: 2 dLP locked / 13x Avg. Multiplier - 1 dLP Locked for 1 year (25x multiplier) - 1 dLP Locked for 1 month (1x multiplier)

How are "Total Annual Platform Fees" calculated?

Amount of projected protocol fees received by a user over the course of 365 days, based on an extrapolated 24h sample of Global Protocol Fees Calculation: (User Daily Protocol Fees * 365)

How is "Your Current Lock APR" calculated?

Definition: User Specific Lock APR depending on Avg. Multiplier Calculation: (Global 1 month Locking APR * User Avg Multiplier)

I claimed my revenue but only received rTokens, how do I retrieve my claimable fees? Where did the funds go?

rTokens are interest-bearing tokens represented as 'rXXXX' in your wallet (example: rUSDC for USDC).

rTokens represent your deposited collateral within Radiant Capital.

To convert them to the underlying asset, they may be withdrawn from the lending dashboard.

It is recommended to not attempt to transfer or trade rTokens.

What is the difference between APY & APR?

For a more detailed explanation of the difference between APY and APR, watch this video.

For further details on the calculation of APY, please refer to Aave's documentation:

Why does the website occasionally not display certain data?

Like many companies, the Radiant DAO relies on Cloudflare to supply front-end data to the website. Unfortunately, Cloudflare has been subject to intermittent outages in recent weeks with its IPFS connectivity. This may cause the website to partially load, or not display certain data correctly at times. This has no effect on the actual protocol, funds, or smart contracts themselves.

We recommend that anyone who has display issues periodically ctrl+F5 refresh the page cache and force a reload.

Last updated