Counterparty and Custodial Risk

COUNTERPARTY TAXONOMY

Asset Issuers:
├── Stablecoin issuers (Circle, Tether, etc.)
├── Wrapped asset issuers (WBTC custodian)
├── Synthetic asset protocols
├── Token creators
└── Risk: Asset becomes worthless if issuer fails

Protocol Operators:
├── Protocol team/DAO
├── Governance participants
├── Multisig signers
├── Admin key holders
└── Risk: Protocol changes or compromises

Infrastructure Providers:
├── Oracle operators
├── Keepers/liquidators
├── MEV searchers
├── Node operators
└── Risk: Infrastructure failure breaks protocol

Bridge Operators:
├── Cross-chain bridge teams
├── Validator sets
├── Custodians on each side
└── Risk: Bridge hack = total loss

Other Users:
├── Liquidity providers (exit liquidity)
├── Borrowers (in lending protocols)
├── Trading counterparties
└── Risk: Behavioral correlation in crisis
```

COUNTERPARTY MAPPING FRAMEWORK

For each position, identify:

1. What assets am I holding?

2. What protocol am I using?

3. What external data is needed?

4. How did assets get here?

5. Who provides liquidity?

6. What backing exists?

EXAMPLE: USDC/ETH LP on Uniswap

Assets:
├── USDC: Issued by Circle
├── ETH: Native (no issuer counterparty)
└── UNI LP token: Issued by Uniswap

Protocol:
├── Uniswap: Governance via UNI token
├── Upgradeable? (Check version)
└── Admin powers?

Infrastructure:
├── Oracles: None for basic AMM
├── Keepers: None required
└── Minimal infrastructure dependency

Bridges:
├── If USDC from bridge: Additional counterparty
├── Native USDC on Ethereum: Just Circle
└── Cross-chain USDC: Circle + Bridge

Backing:
├── USDC: Cash and treasuries (custodian + auditor)
├── ETH: No backing needed
└── Trust in Circle's reserve management

COUNTERPARTY COUNT: 3-5 major counterparties
Each requires assessment.
```

COUNTERPARTY RISK ASSESSMENT

For each counterparty, evaluate:

Reputation (30%):
├── Track record length
├── Historical incidents
├── Industry standing
├── Regulatory compliance
├── Score: 1-10

Transparency (25%):
├── Regular attestations/audits
├── Public reserve reports
├── Clear documentation
├── Responsive communication
├── Score: 1-10

Legal/Regulatory (20%):
├── Jurisdiction (regulated = usually better)
├── Licenses held
├── Legal structure
├── Compliance history
├── Score: 1-10

Technical Security (15%):
├── Smart contract audits
├── Security track record
├── Bug bounty programs
├── Incident response history
├── Score: 1-10

Financial Stability (10%):
├── Capital adequacy
├── Revenue model sustainability
├── Funding/backing
├── Insurance coverage
├── Score: 1-10

COUNTERPARTY SCORE:
= (Reputation × 0.30) + (Transparency × 0.25) +
(Legal × 0.20) + (Technical × 0.15) + (Financial × 0.10)

---

STABLECOIN RISK TAXONOMY

Category 1: Fiat-Backed (Custodial)
├── Examples: USDC, USDT, RLUSD
├── Mechanism: 1:1 backed by fiat reserves
├── Counterparty risk: Issuer, custodians, banks
├── Regulatory risk: Subject to regulation
├── Risk level: MODERATE (established issuers)
└── Key concern: Reserve quality and attestation

Category 2: Crypto-Backed (Overcollateralized)
├── Examples: DAI, LUSD, sUSD
├── Mechanism: Overcollateralized by crypto
├── Counterparty risk: Protocol, oracles, collateral
├── Liquidation risk: During rapid price drops
├── Risk level: MODERATE to MODERATE-HIGH
└── Key concern: Collateral quality and ratio

Category 3: Algorithmic
├── Examples: UST (failed), FRAX (partial)
├── Mechanism: Algorithmic supply adjustment
├── Counterparty risk: Protocol design
├── Peg risk: Can de-peg catastrophically
├── Risk level: HIGH to EXTREME
└── Key concern: Death spiral potential (see Lesson 4)

Category 4: Hybrid
├── Examples: FRAX
├── Mechanism: Partially collateralized + algorithmic
├── Mixed risk profile
├── Risk level: MODERATE-HIGH
└── Key concern: What happens under stress
```

FIAT-BACKED STABLECOIN FRAMEWORK

Issuer Assessment:

USDC (Circle):
├── Jurisdiction: US-regulated
├── Reserves: Cash + short-term treasuries
├── Attestation: Monthly by accounting firm
├── Track record: 6+ years, no major issues
├── Bank risk: Multiple banking relationships
├── Regulatory: Pursuing licensing
├── Risk score: 8/10
└── Consideration: Freeze capability exists

USDT (Tether):
├── Jurisdiction: BVI (less regulated)
├── Reserves: Mixed (cash, treasuries, loans, other)
├── Attestation: Quarterly, limited details
├── Track record: 10+ years, some controversies
├── Transparency: Lower than USDC
├── Risk score: 6/10
└── Consideration: Largest by volume, concentration risk

RLUSD (Ripple):
├── Jurisdiction: NY regulated (NYDFS)
├── Reserves: Cash + short-term treasuries
├── Attestation: Regular third-party
├── Track record: New (2024 launch)
├── Issuer: Ripple (established company)
├── Risk score: 7/10 (higher for short track record)
└── Consideration: Ripple ecosystem benefits, new product

ASSESSMENT FACTORS:
├── Reserve composition (cash > other assets)
├── Attestation frequency and quality
├── Regulatory status
├── Issuer track record
├── Freeze/blacklist capabilities
└── Banking relationship stability
```

CRYPTO-BACKED STABLECOIN FRAMEWORK

Key Risk Factors:

Collateralization Ratio:
├── 150%+: Standard, some safety margin
├── 200%+: More conservative
├── 120-150%: Tighter, higher liquidation risk
├── Below 120%: Elevated risk
└── Higher ratio = more resilient

Collateral Quality:
├── ETH, BTC: High quality, liquid
├── Major altcoins: Medium quality
├── Volatile/illiquid tokens: High risk
├── Diversified collateral: Better
└── Single collateral: Concentrated risk

Oracle Dependency:
├── Chainlink/decentralized: Lower risk
├── Single oracle: Higher risk
├── Liquidation depends on oracle accuracy
└── Oracle failure = potential bad debt

Liquidation Mechanism:
├── Proven liquidation system: Lower risk
├── Untested under stress: Unknown
├── Historical performance in crashes: Check
└── March 2020, May 2021, 2022: How did it perform?

EXAMPLE: DAI Assessment
├── Collateral: Primarily ETH, USDC, other
├── Ratio: 150% minimum, varies by asset
├── Oracle: Chainlink
├── Track record: Survived multiple crashes
├── Risk score: 7/10
└── Concern: Significant USDC collateral exposure
```

STABLECOIN ALLOCATION GUIDELINES

Single Stablecoin Limits:
├── Maximum per issuer: 40% of stablecoin holdings
├── Algorithmic stablecoins: Maximum 10%
├── New stablecoins (< 1 year): Maximum 20%
└── Diversification reduces issuer risk

Portfolio Recommendations:
├── Core (60-70%): USDC or equivalent regulated
├── Secondary (20-30%): Alternative established (USDT, DAI)
├── Tactical (0-10%): Newer options (RLUSD, etc.)
└── Avoid: Heavy algorithmic exposure

XRPL-Specific Considerations:
├── RLUSD: Primary XRPL stablecoin option
├── Gateway stablecoins: Additional counterparty (gateway)
├── Cross-chain stablecoins: Bridge + original issuer risk
└── Native vs bridged matters for counterparty count
```

---

BRIDGE RISK ASSESSMENT

Why bridges matter:
├── Cross-chain assets depend on bridges
├── Bridges custody original assets
├── Bridge failure = wrapped asset worthless
├── ~$2 billion lost to bridge hacks
└── Among highest-risk counterparties

Bridge Types:

Trusted Bridges (Custodial):
├── Centralized entity holds assets
├── Issues wrapped tokens on destination
├── Single point of failure
├── Risk: Custodian hack or fraud
├── Examples: WBTC (BitGo), centralized exchange bridges
└── Risk level: MODERATE to HIGH

Multisig Bridges:
├── Multiple parties must agree
├── Threshold security (3/5, etc.)
├── Better than single custodian
├── Risk: Collusion or compromise of threshold
├── Examples: Many older bridges
└── Risk level: MODERATE

Validator Bridges:
├── Distributed validator set
├── Economic security via staking
├── More decentralized
├── Risk: Validator collusion, smart contract bugs
├── Examples: Axelar, LayerZero
└── Risk level: MODERATE (varies significantly)

Light Client Bridges:
├── Verify proofs trustlessly
├── Most decentralized
├── Technically complex
├── Risk: Implementation bugs, chain attacks
└── Risk level: LOWER (when mature)

BRIDGE RISK SCORING:
├── Single custodian: 3/10
├── Small multisig (3/5): 5/10
├── Large multisig (5/9+): 6/10
├── Validator set (small): 5/10
├── Validator set (large, staked): 7/10
├── Light client (mature): 8/10
└── Adjust for track record and audit quality
```

BRIDGE HACK LESSONS

Ronin Bridge ($625M, March 2022):
├── 5/9 validator multisig
├── 4 keys controlled by one entity (Axie)
├── Attacker compromised 5 keys
├── Social engineering attack
└── Lesson: Validator diversity matters

Wormhole ($320M, February 2022):
├── Signature verification bug
├── Attacker minted wrapped ETH
├── Smart contract vulnerability
└── Lesson: Bridge code is high-risk

Nomad ($190M, August 2022):
├── Upgrade introduced bug
├── Anyone could drain funds
├── Mass exploitation by hundreds
└── Lesson: Bridge upgrades are risky

Harmony Horizon ($100M, June 2022):
├── 2/5 multisig compromised
├── Private key theft
└── Lesson: Low thresholds are dangerous

BRIDGE DUE DILIGENCE:
├── What's the security model?
├── What's the validator/signer setup?
├── Has it been audited? By whom?
├── Any previous incidents?
├── How much is secured? (track record)
└── Can you verify on-chain?
```

XRPL GATEWAY ASSESSMENT

What are gateways:
├── XRPL entities that issue IOUs
├── You trust gateway to honor redemption
├── Like a bank deposit receipt
├── Gateway failure = IOU worthless
└── Counterparty risk in issued assets

Gateway evaluation:

Reputation:
├── How long operating?
├── Track record of redemptions?
├── Community standing?
└── Any past issues?

Transparency:
├── Reserve disclosure?
├── Audit/attestation?
├── Clear redemption process?
└── Accessible support?

Regulatory:
├── Licensed where applicable?
├── KYC/AML compliance?
├── Legal jurisdiction?
└── Regulatory risk exposure?

Technical:
├── Cold storage practices?
├── Security track record?
├── Multi-signature?
└── Insurance coverage?

GATEWAY RISK MITIGATION:
├── Prefer Ripple-issued RLUSD (institutional issuer)
├── Limit exposure to single gateway
├── Verify redemption process works
├── Monitor gateway announcements
└── Diversify across gateways if possible

---

COUNTERPARTY CONCENTRATION LIMITS

Single Counterparty Limits:

Stablecoin issuer:
├── Maximum: 40% of DeFi portfolio
├── Rationale: Issuer failure ≠ crypto failure
├── Diversify across 2-3 major issuers
└── Algorithmic: Max 10%

Protocol:
├── Maximum: 25% of DeFi portfolio
├── Same as position concentration
├── Protocol failure is total loss
└── Covered in portfolio limits

Bridge:
├── Maximum: 30% of cross-chain assets
├── Bridge hacks are total losses
├── Prefer native assets when possible
└── Diversify bridge exposure

Oracle provider:
├── Maximum: 40% dependency on single oracle
├── Most protocols use Chainlink
├── Hard to diversify in practice
└── Accept some concentration

PORTFOLIO-LEVEL LIMITS:
├── Total exposure to any single counterparty: 25%
├── This includes indirect exposure
├── Map all positions to counterparties
└── Check aggregate exposure
```

AGGREGATE EXPOSURE CALCULATION

Step 1: List all positions

Step 2: For each position, identify counterparties

Step 3: Calculate exposure per counterparty

Example Portfolio:
├── Position 1: 30% in USDC/ETH LP
│ ├── Circle (USDC): 15% exposure
│ ├── Uniswap: 30% exposure
│ └── No ETH counterparty
│
├── Position 2: 25% in DAI/USDC LP
│ ├── Circle (USDC): 12.5% exposure
│ ├── MakerDAO (DAI): 12.5% exposure
│ └── Protocol: 25% exposure
│
├── Position 3: 25% in USDC lending
│ ├── Circle (USDC): 25% exposure
│ └── Lending protocol: 25% exposure
│
└── Position 4: 20% in XRP/RLUSD LP
├── Ripple (RLUSD): 10% exposure
└── DEX protocol: 20% exposure

Aggregate Counterparty Exposure:
├── Circle (USDC): 15% + 12.5% + 25% = 52.5% ← EXCEEDS LIMIT
├── Uniswap: 30%
├── MakerDAO: 12.5%
├── Lending protocol: 25%
├── Ripple: 10%
└── DEX protocol: 20%

ACTION NEEDED: Reduce Circle/USDC exposure below 40%
```

DIVERSIFICATION STRATEGIES

Stablecoin diversification:
├── Primary: USDC (30% of stables)
├── Secondary: USDT (25%)
├── Tertiary: DAI (25%)
├── XRPL: RLUSD (15%)
├── Other: 5%
└── No single issuer > 40%

Protocol diversification:
├── No single protocol > 25%
├── Spread across protocol types
├── Different governance structures
├── Different technical approaches
└── Reduces correlated failure risk

Bridge diversification:
├── Prefer native assets
├── If bridging, use different bridges
├── Native > canonical > third-party bridges
├── Limit any single bridge to 30%
└── Accept some concentration may be necessary

Geographic/Jurisdictional:
├── Mix US and non-US entities
├── Different regulatory regimes
├── Reduces single jurisdiction risk
└── Consider in counterparty selection
```

---

COUNTERPARTY MONITORING

Stablecoin Issuers:
├── Reserve attestation releases
├── Regulatory announcements
├── Peg deviation (> 1% = warning)
├── Redemption reports
├── Banking relationship changes
└── Check monthly

Bridges:
├── Security incidents
├── Validator/signer changes
├── Upgrade announcements
├── TVL changes
├── Community concerns
└── Check weekly for active positions

Protocols:
├── Governance proposals
├── Upgrade announcements
├── Team changes
├── Security advisories
├── Covered in governance monitoring
└── Check per governance schedule

ALERT THRESHOLDS:
├── Stablecoin > 1% off peg: Review
├── Stablecoin > 3% off peg: Consider exit
├── Bridge security incident: Immediate review
├── Issuer negative news: Review exposure
├── Counterparty downgrade: Rebalance
```

COUNTERPARTY RISK MAP

Create a table:

Position	% Portfolio	Counterparties	Risk Level	Exposure
Pos 1	25%	Circle, Uni	Med	25% Uni
Pos 2	20%	Circle, Aave	Med	20% Aave
...	...	...	...	...

Aggregate by counterparty:

Counterparty	Total Exposure	Limit	Status
Circle	35%	40%	OK
Uniswap	25%	25%	At Limit
Aave	20%	25%	OK
Bridge X	15%	30%	OK
...	...	...	...

Review quarterly, update with portfolio changes.

---

✅ Counterparty failures cause major losses. Bridge hacks, stablecoin de-pegs demonstrate real risk.

✅ Concentration amplifies risk. Heavy exposure to single counterparty = catastrophic if it fails.

✅ Counterparty risk is additive. Each layer of counterparties adds to total risk.

⚠️ Counterparty correlation. How correlated failures are across counterparties.

⚠️ Tail risk assessment. Probability of major counterparty failure is hard to estimate.

⚠️ Recovery rates. What you get back when counterparty fails varies widely.

📌 "Decentralized = no counterparty." Every DeFi position has counterparties.

📌 Ignoring indirect exposure. Counterparty of counterparty is still your counterparty.

📌 Concentration in "safe" counterparties. Even best counterparties can fail.

---

Assignment: Create comprehensive counterparty risk map for your DeFi portfolio.

Requirements:

1. List all positions with % allocation
2. Identify all counterparties for each position
3. Score each counterparty (1-10)
4. Calculate aggregate exposure per counterparty
5. Compare to concentration limits
6. Identify positions exceeding limits
7. Create rebalancing plan if needed

Time investment: 2 hours

---

1. You have 50% of your DeFi portfolio in USDC-based positions. What's the concern?
A) No concern—USDC is safe B) Exceeds 40% single counterparty limit for stablecoin issuer C) Only concerning if > 75% D) USDC has no counterparty risk

Correct Answer: B

2. What makes bridge risk particularly severe?
A) Bridges are slow B) Bridge hack = total loss of bridged assets C) Bridges charge high fees D) Bridges are unregulated

Correct Answer: B

3. For XRPL gateway-issued assets, what's the key counterparty risk?
A) XRPL network failure B) Gateway failure or fraud = IOU worthless C) XRP price volatility D) Transaction fees

Correct Answer: B

---

End of Lesson 8