RLUSD for Treasury Operations
Learning Objectives
Explain RLUSD's architecture including reserve backing, issuance, and redemption mechanics
Identify optimal treasury use cases where RLUSD provides advantages over alternatives
Design operational workflows for RLUSD acquisition, custody, and deployment
Implement appropriate controls for RLUSD treasury operations
Compare RLUSD objectively against USDC and other stablecoin options
In Lesson 2, we established the stablecoin landscape and noted that RLUSD and USDC are both viable options for treasury operations. So why dedicate an entire lesson to RLUSD specifically?
The answer is integration and focus.
RLUSD is designed to work seamlessly within the Ripple ecosystem—with ODL, Liquidity Hub, and Ripple Custody. For treasury teams implementing multiple Ripple products, RLUSD provides operational efficiencies that justify deep understanding. Additionally, RLUSD's regulatory structure (NYDFS-supervised, BNY Mellon custody) represents a specific model worth understanding.
What this lesson is NOT:
This is not advocacy that RLUSD is always better than alternatives. In fact, we'll be explicit about when USDC or other options may be preferable. The goal is operational competence with RLUSD for situations where it's the right choice.
What this lesson IS:
A practical implementation guide. By the end, you'll know exactly how to acquire, hold, deploy, and redeem RLUSD in a treasury context—with all the operational procedures and controls required.
RLUSD TECHNICAL ARCHITECTURE:
TOKEN STANDARD:
Native issued currency
Issuer: Ripple's designated trust line
Precision: Up to 15 significant digits
Transfer: Standard XRPL payment transactions
Settlement: 3-5 seconds
ERC-20 token standard
Contract address: [Verify current address]
Precision: 18 decimals (standard ERC-20)
Transfer: Standard ERC-20 transfer
Settlement: ~12 seconds (1 block), finality ~12 minutes
DUAL-CHAIN DEPLOYMENT:
XRPL: Native integration with ODL, Ripple ecosystem
Ethereum: Broader DeFi compatibility, wider exchange support
Treasury choice: Depends on use case
Bridge mechanism available (verify current status)
Same underlying reserve backing
Fungible across chains (1 RLUSD = 1 RLUSD)
Conversion may involve fees/time
XRPL: If using ODL or Ripple-native workflows
Ethereum: If broader exchange access needed
Both: For maximum flexibility (adds complexity)
RLUSD RESERVE BACKING:
COMPOSITION:
US Dollar cash deposits
Short-term US Treasury securities
Other cash equivalents approved by NYDFS
Every RLUSD in circulation backed by $1+ in reserves
No fractional reserve
No algorithmic stabilization
Custodian: Bank of New York Mellon
Segregated accounts
Not commingled with Ripple operating funds
Protected from Ripple bankruptcy (in theory)
ATTESTATION:
Frequency: Monthly
Performed by: Independent accounting firm
Scope: Reserve balance ≥ RLUSD in circulation
Publication: Public attestation reports
Limitation: Attestation ≠ Full audit (point-in-time verification)
WHAT THIS MEANS FOR TREASURY:
Strengths:
✓ Clear reserve backing
✓ Tier-1 custodian (BNY Mellon)
✓ Regulatory oversight (NYDFS)
✓ Monthly transparency
Limitations:
⚠️ Attestation is not continuous audit
⚠️ Short track record (launched Dec 2024)
⚠️ Smaller reserve than USDC ($200M vs $32B+)
⚠️ Concentration in single issuer structure
```
RLUSD LIFECYCLE:
ISSUANCE (Minting):
- Authorized institutional participants
- Through Standard Custody & Trust Company
- KYC/AML required
- Onboard with Standard Custody (one-time)
- Wire USD to designated account
- RLUSD minted to specified wallet
- Typical timeline: Same day to T+1
Minimum: Verify current minimums (likely $100K+)
Fees: Verify current fee structure
REDEMPTION (Burning):
- Authorized participants (same as minting)
- Direct redemption rights for holders
- Submit redemption request
- Transfer RLUSD to burn address
- USD wired to designated bank account
- Typical timeline: Same day to T+2
Fees: Verify current redemption fees
Limits: May have daily/transaction limits
SECONDARY MARKET:
Verify current exchange listings
XRPL DEX native trading
Centralized exchanges (check availability)
Smaller than USDC (newer, smaller float)
Spreads may be wider
Large transactions may require OTC
TREASURY WORKFLOW RECOMMENDATION:
Acquire via secondary market (exchanges)
Faster, more flexible
Market pricing
Consider direct minting
Better pricing on large amounts
Requires authorized participant status
Secondary market for speed
Direct redemption for certainty
Plan for both options
RLUSD USE CASE EVALUATION:
CRITERIA FOR RLUSD SELECTION:
Strong Fit Indicators:
✓ Using other Ripple products (ODL, Liquidity Hub)
✓ Cross-border treasury operations
✓ Regulatory clarity important (NYDFS preference)
✓ BNY Mellon custody relationship valued
✓ XRPL-native operations
Weak Fit Indicators:
✗ Need maximum liquidity (USDC larger)
✗ DeFi integration primary use
✗ Longest track record required
✗ Widest exchange availability needed
✗ No other Ripple product usage
HONEST ASSESSMENT:
RLUSD is optimal when integrated with Ripple ecosystem.
USDC may be better for standalone stablecoin needs.
```
USE CASE 1: CROSS-BORDER LIQUIDITY POSITIONING
- Company has operations in US, Mexico, Philippines
- Need to position liquidity across regions
- Traditional wire transfers slow and expensive
- Hold RLUSD in central treasury
- Transfer to regional wallets as needed
- Convert to local currency via ODL or exchanges
- 24/7 availability, minutes vs. days
- Acquire RLUSD (exchange or mint)
- Hold in institutional custody
- Transfer to regional wallet when needed
- Convert to local currency
- Local operations receive funds
- Speed: Minutes vs. 1-3 days
- Cost: Lower than wire + FX
- Flexibility: Move funds 24/7
- Integration: Works with ODL
- Need custody in each region
- Local conversion liquidity varies
- Regulatory status in each jurisdiction
USE CASE 2: WORKING CAPITAL OPTIMIZATION
- $50M in short-term investments
- Need instant liquidity access
- Traditional MMF has T+1 settlement
- Allocate portion to RLUSD ($5-10M)
- Instant liquidity, no settlement delay
- Deploy for urgent needs immediately
- Convert portion of cash to RLUSD
- Hold in custody earning zero yield
- Deploy instantly when needed
- Replenish after need passes
- Instant availability (no T+1)
- 24/7 access (not banking hours)
- Precise amounts (no fund minimums)
- Zero yield (vs. MMF 4-5%)
- Opportunity cost calculation required
- Only makes sense for "instant access" tranche
- Not for all short-term investments
- 5-15% of working capital maximum
- Based on historical urgent funding needs
USE CASE 3: SUPPLIER PAYMENT ACCELERATION
- Key supplier offers 2% discount for payment in 3 days vs. 30
- Traditional wire takes 2-3 days to clear
- Miss discount window regularly
- Pay supplier in RLUSD (if they accept)
- Or: Convert RLUSD to local currency rapidly
- Capture early payment discounts
- Supplier invoices with early pay discount
- Approve payment immediately
- Send RLUSD or convert to supplier's currency
- Settlement in minutes/hours vs. days
- Capture discount
- 2% discount on $10M annual = $200K savings
- Strengthened supplier relationship
- Working capital optimization
- Supplier must accept or have conversion path
- Not all suppliers will participate
- May require supplier education
USE CASE 4: ODL INTEGRATION
- Using ODL for cross-border payments
- Want to optimize treasury around ODL corridors
- Reduce friction in payment flows
- Pre-fund ODL transactions with RLUSD
- Seamless integration (Ripple ecosystem)
- Unified reporting and reconciliation
- Hold RLUSD in Ripple-integrated custody
- ODL transactions draw from RLUSD balance
- Automated conversion through corridor
- Single platform for stablecoin + ODL
- Operational simplicity
- Native integration
- Unified counterparty (Ripple)
- Consolidated reporting
- Ecosystem lock-in
- Concentration with single vendor
- Compare to USDC + separate ODL
HONEST COMPARISON - WHEN TO USE USDC INSTEAD:
USE CASE: MAXIMUM LIQUIDITY DEPTH
- Largest possible trading volume
- Tightest spreads for large transactions
- Most exchange availability
→ USDC is better: $32B+ market cap vs. ~$200M RLUSD
USE CASE: DEFI INTEGRATION
- Yield generation (lending protocols)
- DEX liquidity provision
- DeFi treasury strategies
→ USDC is better: Deeper DeFi integration, more protocols
USE CASE: LONGEST TRACK RECORD
- Maximum operational history
- Proven stress-test survival (SVB depeg recovery)
- Longest audit trail
→ USDC is better: 6+ years vs. RLUSD's months
USE CASE: MULTI-CHAIN FLEXIBILITY
- Presence on 15+ blockchains
- Maximum deployment flexibility
- Chain-agnostic operations
→ USDC is better: Broader multi-chain deployment
BALANCED APPROACH:
- RLUSD for Ripple ecosystem operations
- USDC for broader stablecoin needs
- Diversification benefit
- Best tool for each job
RLUSD ACQUISITION - OPERATIONAL PROCEDURE:
METHOD 1: EXCHANGE PURCHASE
Prerequisites:
□ Approved exchange account (verify RLUSD listing)
□ Completed exchange KYC/AML
□ Withdrawal wallet address ready
□ Transaction within policy limits
1. Log into approved exchange
2. Verify RLUSD trading pair available
3. Check current price vs. $1.00 peg
4. Place limit order at target price
5. Execute trade
6. Verify RLUSD credited to exchange wallet
7. Initiate withdrawal to custody wallet
8. Confirm blockchain receipt
9. Update treasury records
10. File transaction documentation
Timing: 15-30 minutes typical
Cost: Exchange fee (0.1-0.5%) + network fee
METHOD 2: DIRECT MINTING
Prerequisites:
□ Authorized participant status with Standard Custody
□ Onboarding complete (one-time)
□ Wire transfer capability
□ Receiving wallet designated
1. Calculate RLUSD amount needed
2. Submit minting request to Standard Custody
3. Receive wire instructions
4. Initiate wire transfer (dual authorization)
5. Confirm wire receipt with Standard Custody
6. Receive RLUSD to designated wallet
7. Verify on blockchain explorer
8. Update treasury records
9. File documentation (wire, mint confirmation)
Timing: Same day to T+1
Cost: Wire fee + minting fee (verify current)
Minimum: Verify current minimum (likely $100K+)
DECISION MATRIX:
Amount < $100K → Exchange purchase
Amount $100K-$1M → Exchange or mint (compare costs)
Amount > $1M → Direct minting recommended
Urgency high → Exchange purchase
Cost optimization priority → Direct minting
```
RLUSD CUSTODY - OPERATIONAL PROCEDURE:
APPROVED CUSTODY OPTIONS:
Ripple Custody (Metaco)
Other qualified custodians supporting RLUSD
Bank custody (if available)
Approved exchanges
Maximum 48 hours
Maximum $500K
Approved hardware wallets only
Maximum $500K
Multi-signature required
CUSTODY PROCEDURE:
Select custody provider per policy
Complete custody onboarding/KYC
Establish wallet addresses
Configure multi-signature (if applicable)
Test with small transaction
Document wallet addresses in secure system
Establish backup/recovery procedures
Receive RLUSD to designated custody wallet
Verify receipt on blockchain explorer
Confirm custodian statement reflects balance
Reconcile daily (custody statement vs. blockchain vs. internal)
Report positions per reporting schedule
Document business reason for movement
Obtain required authorization per matrix
Initiate transfer from source custody
Verify receipt at destination
Update internal records
File movement documentation
SEGREGATION REQUIREMENTS:
- RLUSD held in company-controlled wallets
- Segregated from custodian's own assets
- Clear ownership documentation
- Backup key holders designated
RLUSD DEPLOYMENT - OPERATIONAL PROCEDURE:
DEPLOYMENT USE CASES:
A. Internal Transfer (Treasury to Subsidiary):
B. External Payment (Treasury to Vendor)
C. Conversion (RLUSD to Fiat)
D. ODL Funding (RLUSD to ODL Platform)
PROCEDURE A: INTERNAL TRANSFER
- Receive transfer request from subsidiary
- Verify request authorization
- Confirm receiving wallet belongs to subsidiary
- Check transaction against policy limits
- Obtain required approvals per matrix
- Execute transfer from custody
- Verify blockchain confirmation
- Notify subsidiary of completion
- Update intercompany records
- File documentation
PROCEDURE B: EXTERNAL PAYMENT
- Receive payment request with vendor wallet
- Verify vendor is approved counterparty
- Verify wallet address through secure channel
- Confirm payment amount and purpose
- Obtain required approvals
- Execute sanctions screening
- Execute transfer
- Verify blockchain confirmation
- Notify vendor and obtain acknowledgment
- Update AP records
- File documentation
PROCEDURE C: CONVERSION TO FIAT
Determine conversion amount
Check exchange liquidity/pricing
Transfer RLUSD to exchange
Execute sell order (RLUSD → USD)
Initiate USD withdrawal to bank
Verify bank receipt
Update records
Submit redemption request to Standard Custody
Transfer RLUSD to burn address
Confirm burn transaction
Await USD wire
Verify bank receipt
Update records
PROCEDURE D: ODL FUNDING
- Determine ODL funding requirement
- Transfer RLUSD to ODL-connected wallet
- Verify receipt in ODL platform
- Configure for ODL transactions
- Monitor utilization
- Replenish as needed
RLUSD REDEMPTION - OPERATIONAL PROCEDURE:
WHEN TO REDEEM:
- Exiting RLUSD position entirely
- Large conversion needs
- Testing redemption capability
- Counterparty preference for fiat
REDEMPTION PROCEDURE:
Pre-Requisites:
□ Authorized participant status verified
□ Bank account designated for USD receipt
□ Redemption terms understood
□ Transaction within any limits
- Calculate redemption amount
- Submit redemption request to Standard Custody
- Receive confirmation and burn address
- Obtain internal approvals per matrix
- Execute RLUSD transfer to burn address
- Verify burn transaction on blockchain
- Retain transaction hash for records
- Await USD wire (typically same day to T+2)
- Verify USD receipt in bank account
- Reconcile: RLUSD burned = USD received (less fees)
- Update all records
- File complete documentation
FEES AND TIMING:
Redemption Fee: Verify current (may be 0-0.1%)
Wire Fee: Standard incoming wire fee
Timing: Same day to T+2 typical
Minimum: Verify current minimum
CONTINGENCY:
Document delay and communications
Escalate per counterparty issue procedure
Assess alternative liquidation (exchange)
Report to management
Document resolution
Understand reason
Assess if curable
Escalate to legal if needed
Consider regulatory complaint if appropriate
Document fully
CONTROL FRAMEWORK FOR RLUSD:
ACQUISITION CONTROLS:
Compare purchase price to $1.00 peg
Automatic flag if >0.1% deviation
Escalation required for >0.5% deviation
Purpose: Avoid buying depegged stablecoin
Only approved exchanges/sources
Verify exchange regulatory status quarterly
No P2P or unverified sources
Purpose: Counterparty risk management
Per-transaction limits enforced
Daily aggregate limits monitored
Monthly volume tracked
Purpose: Concentration risk management
CUSTODY CONTROLS:
Whitelist approved addresses only
New address requires dual approval
Test transaction required for new addresses
Purpose: Prevent misdirected transfers
Daily: Blockchain vs. custodian statement
Weekly: All sources reconciled
Monthly: Full position verification
Purpose: Detect unauthorized movement
Role-based access to custody platform
Multi-factor authentication required
Quarterly access review
Immediate revocation on role change
Purpose: Prevent unauthorized access
TRANSACTION CONTROLS:
All transactions >$500K require two approvers
Approvers cannot be transaction initiator
Digital signatures required
Purpose: Prevent unauthorized transactions
All external transfers screened
OFAC SDN list checked
Wallet address screening
Purpose: Regulatory compliance
Complete audit trail required
Purpose, authorization, execution documented
Retained per retention policy (7+ years)
Purpose: Audit support, regulatory defense
RLUSD MONITORING REQUIREMENTS:
REAL-TIME MONITORING:
Track all wallets for unexpected activity
Alert on any unauthorized movement
Monitor for large transactions
Tool: Blockchain analytics platform
Track RLUSD price vs. $1.00
Alert if deviation >0.5%
Source: Exchange price feeds, aggregators
DAILY MONITORING:
Total RLUSD holdings
By custody location
By blockchain (XRPL vs. Ethereum)
Change from prior day
Blockchain balance vs. records
Custodian statement vs. records
Investigate any breaks
WEEKLY MONITORING:
Transactions executed
Volumes by type (acquisition, deployment, redemption)
Any exceptions or issues
Current exposure vs. limits
Counterparty exposure vs. limits
MONTHLY MONITORING:
Complete RLUSD holdings detail
Cost basis and valuation
Activity summary
Review latest RLUSD attestation
Compare to prior months
Note any concerns
Position and activity summary
Any issues or escalations
Recommendations
QUARTERLY MONITORING:
Test sample of transactions
Verify control operation
Document results
Exchange/custodian status verification
Regulatory status confirmation
Scorecard update
RLUSD TAX AND ACCOUNTING TREATMENT:
ACCOUNTING TREATMENT:
If readily convertible to known amount
If insignificant risk of value change
Consult auditor for confirmation
Cash and cash equivalents (if qualifying)
Or: Short-term investments
Disclosed in notes
At $1.00 (if stable)
Fair value if significant deviation
Document valuation methodology
TAX TREATMENT:
Exchange of USD for RLUSD
No gain/loss if at par
Document cost basis
No taxable event while holding
No interest/yield to report
Exchange of RLUSD for USD/goods
Minimal gain/loss if stable
Document fair value at disposition
Date and time of all transactions
Amount in RLUSD and USD
Cost basis
Purpose
Counterparty
REPORTING REQUIREMENTS:
Disclose digital asset holdings
Disclose valuation methodology
Risk disclosures in notes
Form 8949 if any gains/losses
Corporate return integration
State filings as required
Complete transaction history
Custody confirmations
Valuation support
Control documentation
RISK ASSESSMENT - RLUSD:
RISK 1: DEPEG RISK
Description: RLUSD trades below $1.00
Probability: Low (regulated, 100% backed)
Impact: Direct loss on holdings
Historical: No significant depeg events (short history)
- Monitor peg continuously
- Diversify across stablecoins
- Set position limits
- Establish depeg response procedure
- Assess magnitude and cause
- If temporary (<2%): Hold, monitor
- If significant (>5%): Consider redemption
- If systemic: Execute contingency plan
RISK 2: ISSUER/REGULATORY RISK
Description: Standard Custody or Ripple faces regulatory action
Probability: Low-Medium
Impact: Potential redemption delays, reputational
- Monitor regulatory developments
- Diversify across issuers (USDC as backup)
- Maintain redemption capability
- Document regulatory due diligence
RISK 3: OPERATIONAL RISK
Description: Custody failure, key loss, transaction error
Probability: Low (with proper controls)
Impact: Potential loss of funds
- Institutional custody
- Multi-signature requirements
- Tested backup/recovery
- Insurance where available
RISK 4: LIQUIDITY RISK
Description: Unable to convert RLUSD to USD quickly
Probability: Medium (smaller float than USDC)
Impact: Delayed access to funds
- Maintain exchange relationships
- Direct redemption capability
- Position limits relative to liquidity
- Stress test liquidation scenarios
RISK 5: CONCENTRATION RISK
Description: Over-reliance on single stablecoin
Probability: N/A (policy choice)
Impact: Amplified impact if RLUSD issues
- Policy limits on single stablecoin
- USDC as alternative
- Regular review of concentration
RLUSD CONTINGENCY PROCEDURES:
SCENARIO 1: SIGNIFICANT DEPEG (>2%)
Trigger: RLUSD trades below $0.98
1. Alert Treasurer and CFO
2. Halt new RLUSD acquisitions
3. Assess cause (market vs. fundamental)
4. Calculate potential exposure/loss
- If temporary/market: Monitor, hold
- If fundamental concern: Initiate redemption
- If systemic: Execute full exit
- Update Investment Committee
- Prepare board notification if material
SCENARIO 2: REDEMPTION FAILURE
Trigger: Redemption request not fulfilled within 5 business days
1. Document all communications with issuer
2. Escalate internally to CFO and Legal
3. Assess alternative liquidation options
4. Calculate exposure at risk
- Day 5: Senior management notification
- Day 10: Legal engagement
- Day 15: Consider regulatory complaint
- Sell on secondary market (accept discount if needed)
- OTC sale to willing buyer
- Legal action as last resort
SCENARIO 3: CUSTODY INCIDENT
Trigger: Suspected unauthorized access or movement
1. Freeze all transactions if possible
2. Verify all wallet balances
3. Contact custody provider immediately
4. Document timeline and observations
- Blockchain forensics
- Access log review
- Third-party investigation if warranted
- Insurance claim if applicable
- Legal action if third-party fault
- Control enhancement post-incident
SCENARIO 4: REGULATORY CHANGE
Trigger: Material change in RLUSD regulatory status
- Understand nature of change
- Legal analysis of implications
- Impact on operations
- Continue with modified procedures
- Transition to alternative (USDC)
- Full exit from RLUSD
- Engage regulators/comment periods
---
✅ RLUSD has clear regulatory structure. NYDFS supervision and BNY Mellon custody provide institutional-grade framework.
✅ Integration with Ripple ecosystem is real. Native XRPL deployment, ODL compatibility, Ripple Custody integration.
✅ 100% reserve backing is verified. Monthly attestations confirm full backing.
✅ Redemption rights exist. Holders can redeem for USD through Standard Custody.
⚠️ Long-term track record not established. Launched December 2024—limited operational history.
⚠️ Liquidity depth in stress scenarios. Smaller float than USDC—untested under stress.
⚠️ Regulatory evolution. Federal stablecoin legislation could change landscape.
⚠️ Competitive positioning. USDC has significant advantages in liquidity and track record.
🔴 Over-concentration in RLUSD. Putting all stablecoin holdings in RLUSD creates single-issuer risk.
🔴 Assuming USDC equivalence. RLUSD is not drop-in replacement—different liquidity profile.
🔴 Ignoring operational complexity. Dual-chain deployment, custody setup, redemption procedures require proper implementation.
RLUSD is a legitimate institutional-grade stablecoin with clear regulatory structure and strong integration with Ripple products. For treasury teams using ODL or other Ripple products, RLUSD integration makes operational sense. However, RLUSD should typically be part of a stablecoin strategy that includes USDC for diversification and liquidity access. The short track record and smaller float warrant conservative position limits until more operational history accumulates.
Assignment:
Create an RLUSD implementation plan for your company (or hypothetical company from previous lessons).
Requirements:
Identify 2-3 specific use cases for RLUSD at your company
Quantify expected benefits for each use case
Explain why RLUSD vs. USDC for each use case
Note any use cases where USDC is preferred
Document acquisition procedure (exchange or mint)
Document custody arrangement (provider, setup)
Document deployment procedures for your use cases
Document redemption procedure
List specific controls for RLUSD operations
Define monitoring requirements
Create escalation procedures for key risks
Document reconciliation process
Top 3 risks specific to your RLUSD implementation
Probability and impact for each
Mitigation measures
Contingency triggers
Quality of use case justification (25%)
Completeness of procedures (30%)
Appropriateness of controls (25%)
Rigor of risk assessment (20%)
Time Investment: 3-4 hours
Value: This deliverable provides implementation blueprint for RLUSD operations.
Knowledge Check
Question 1 of 4RLUSD is deployed on which blockchain networks?
- Ripple: RLUSD documentation and attestation reports
- Standard Custody & Trust Company: Issuer information
- NYDFS: Stablecoin guidance
- Circle: USDC documentation
- Deloitte: Stablecoin accounting considerations
- Bank for International Settlements: Stablecoin reports
- AICPA: Digital asset audit considerations
- EY: Stablecoin treasury frameworks
- PwC: Crypto custody best practices
For Next Lesson:
Lesson 7 covers On-Demand Liquidity (ODL) implementation—how to use XRP as a bridge currency for cross-border payments and how ODL integrates with RLUSD treasury holdings.
End of Lesson 6
Total words: ~6,400
Estimated completion time: 55 minutes reading + 3-4 hours for deliverable
Course 57: Corporate Treasury with Ripple Products
Lesson 6 of 15
XRP Academy - The Khan Academy of Digital Finance
Key Takeaways
RLUSD excels in Ripple ecosystem integration.
Native XRPL, ODL compatibility, and Ripple Custody integration provide operational efficiency for users of multiple Ripple products.
Regulatory structure is institutional-grade.
NYDFS supervision and BNY Mellon custody meet institutional requirements.
Liquidity limitations are real.
Smaller float than USDC means position limits should reflect available liquidity.
Operational procedures matter.
Acquisition, custody, deployment, and redemption each require documented procedures and controls.
Diversification is prudent.
RLUSD + USDC typically better than either alone. ---