LlamaRisk

• Name: LlamaRisk
• URL: https://www.llamarisk.com/
• Category: DeFi risk-governance company / parameter-advisory operator / verification-tooling company
• Summary: LlamaRisk belongs in companies/ because the practical authority is not a neutral protocol or one reusable onchain mechanism. The useful question is who writes the collateral and market-risk frameworks, monitors live systems, recommends caps and intervention thresholds, and packages those judgments into products like LlamaGuard and SAVE that governance participants may start treating as risk truth. That company-shaped control surface matters more than any standalone LlamaRisk protocol label.
• What it does:
  • Serves as a named risk service provider inside DeFi governance processes, especially for lending, stablecoin, RWA, and collateral-onboarding decisions
  • Publishes detailed frameworks for asset evaluation, market risk, smart-contract risk, oracle dependencies, governance, access control, and parameter calibration
  • Packages ongoing monitoring, verification, and enforcement tooling through LlamaGuard rather than stopping at memo-style recommendations
  • Maintains technical repos such as the Aave-focused framework materials and SAVE, a structured attestation and verification engine for signed claims and reserve-style checks
  • Sits in the loop where protocols decide what collateral, caps, liquidation parameters, proof requirements, or intervention thresholds are acceptable in production
• Key claims:
  • The homepage says LlamaRisk designs risk frameworks, monitors system health, and operates verification infrastructure for DeFi protocols
  • The official split across Advisory, Risk Intelligence, and LlamaGuard shows a company packaging ongoing judgment and monitoring workflow rather than only publishing occasional research
  • The About page says LlamaRisk started in the Curve ecosystem and built its profile around stablecoin, liquid-staking, and RWA due diligence, which helps explain why it now appears as a repeat governance-side authority surface
  • The Aave V3 framework explicitly covers asset fundamentals, market risk, oracle setup, dependency risk, governance, access control, recursive looping, caps, liquidation design, and interest-rate-model goals, showing that LlamaRisk can influence real market behavior rather than merely comment on it
  • SAVE extends the company boundary beyond advisory into signed-attestation and verification plumbing, which is analytically useful because it turns the firm’s judgment into machine-consumable workflow
  • The Aave governance renewal thread confirms LlamaRisk as an institutionalized DAO risk provider rather than only an outside analyst
• Whitepaper: No separate company whitepaper is the point here. The strongest primary materials were already captured in ../whitepapers/llamarisk-primary-sources-2026-05-07.md.
• Sources:
  • https://www.llamarisk.com/
  • https://www.llamarisk.com/about
  • https://github.com/llama-risk
  • https://raw.githubusercontent.com/llama-risk/aave-research/main/frameworks/aave_v3_framework.md
  • https://raw.githubusercontent.com/llama-risk/save/main/README.md
  • https://governance.aave.com/t/arfc-renew-llamarisk-as-risk-service-provider-epoch-4/24446
  • ../whitepapers/llamarisk-primary-sources-2026-05-07.md

Internal linkages

• Project-layer alias: llamarisk.
• Strongest adjacent operator-risk reads: chaos-labs, gauntlet, steakhouse-financial, and block-analitica.
• Governance-consumer surfaces worth keeping nearby: aave, spark, and curve.

Protocol / company boundary

• There is no especially clean standalone LlamaRisk protocol doing the analytical work here.
• The meaningful surface is the named organization that writes risk frameworks, maintains monitoring and verification products, participates in governance forums, and helps decide what risk posture major protocols should accept.
• That is why this note belongs in companies/: the practical authority question is who authors and operates the risk-policy workflow, not what immutable mechanism supposedly replaces that judgment.

Control surface

• Practical leverage sits in what LlamaRisk chooses to measure, which risks it foregrounds, how it calibrates recommendations, what thresholds or caps it argues are safe, and how its verification products encode those views for downstream consumers.

• The firm does not need an admin key to matter. If governance delegates, risk committees, or protocol operators begin treating LlamaRisk frameworks and alerts as default risk truth, real authority accumulates in those advisory and monitoring pipelines.

• LlamaGuard and SAVE sharpen that point rather than weakening it: once the company packages judgment into always-on monitoring or signed-attestation workflow, the interpretation layer itself becomes part of the control plane.

• Read LlamaRisk as an operator-managed risk-policy and verification surface, not as a neutral protocol primitive.

• Last reviewed: 2026-08-09 UTC