With LlamaRisk leaving Curve, the DAO needs replacement coverage for risk assessment and ongoing market monitoring across Curve primitives.
The priority is to secure reliable risk coverage for Curve’s core markets and ensure that useful tooling, models, documentation, and monitoring assets remain available to the DAO after the mandate ends. Candidate teams should propose which responsibilities they can take on, what KPIs they would commit to, and what budget would be required.
Mandate Objectives
The mandate should help the Curve DAO make better risk-adjusted decisions across crvUSD peg-stability mechanisms and mint markets, as well as Llamalend isolated markets.
The selected team should aim to:
- Minimize preventable losses, bad debt, and market impairment.
- Help the DAO understand whether Curve is being properly compensated for the risks it takes.
- Monitor active markets for deteriorating conditions and escalate material risks early.
- Support sustainable DAO revenue by assessing markets through a risk lens.
- Improve transparency through regular public reporting and reusable risk infrastructure.
The selected team should begin by reviewing existing LlamaRisk handoff materials, reports, simulations, models, dashboards, and repositories, and assess what is reusable, what should be deprecated, and what should be rebuilt.
The selected team is responsible for the quality of its risk analysis, models, alerts, and recommendations; the DAO and eDAO remain responsible for final decisions and execution.
The core question is: Is the Curve DAO taking the right risk-adjusted approach, and are those risks being monitored properly?
Scope
The scope is split into two main areas. Teams may propose to cover one or both.
1. crvUSD / Mint Markets Risk
This covers crvUSD mint markets and related Curve infrastructure, including PegKeepers and DAO credit lines where relevant.
Expected responsibilities may include:
- Assessing new crvUSD mint markets and PegKeeper pools before DAO approval.
- Recommending risk-driven parameters for the deployment of new markets
- Reviewing collateral quality, liquidity, oracle dependencies, market depth, and failure modes.
- Monitoring active mint markets and PegKeepers for market health, liquidity conditions, oracle behavior, bad debt risk, collateral deterioration, and abnormal activity.
- Recommending risk-driven parameter changes where needed.
- Recommending the addition, adjustment, or removal of crvUSD mint markets and PegKeeper pools where risk conditions justify it.
- Supporting Llamalend v1 deprecation and Llamalend v2 rollout from a risk-monitoring perspective.
- Supporting governance posts and executable payloads where appropriate.
- Detecting and escalating critical market stress conditions with timely recommendations to the DAO and eDAO.
- Publishing biannual public updates on crvUSD market health, risks, recommendations, and unresolved issues.
2. Llamalend / Isolated Markets Risk
This covers Llamalend markets and related LLAMMA infrastructure.
Expected responsibilities may include:
- Producing collateral-risk and market-risk reports for new Llamalend markets before DAO vote.
- Recommending risk-driven parameters for the deployment of new markets
- Reviewing collateral quality, oracle dependencies, liquidity depth, liquidation assumptions and market-specific failure modes.
- Monitoring active lending markets for utilization, liquidity health, oracle behavior, bad debt risk, solvency and abnormal activity.
- Recommending risk-driven parameter changes where needed.
- Supporting Llamalend v1 deprecation and Llamalend v2 rollout from a risk-monitoring perspective.
- Supporting governance posts and executable payloads where appropriate.
- Detecting and escalating critical market stress conditions with timely recommendations.
- Publishing public updates on lending market health, risks, recommendations, and unresolved issues.
Operating Expectations
Teams should explain how they would:
- Monitor active markets on an ongoing basis.
- Review new market proposals before DAO votes.
- Identify and escalate material risks.
- Define alert thresholds and incident-response procedures.
- Coordinate with relevant Curve contributors, including Swiss Stake and the backend team where monitoring infrastructure is involved.
- Document models, alerts, assumptions, limitations, and runbooks so they can be reused by Curve contributors.
The DAO receives a perpetual license and operational access to the models and code; the team retains the right to commercialise the tooling to other DAOs, TradFi, and DeFi actors.
Optional Scope
Teams may also propose additional responsibilities, including:
- Reviewing gauge proposals.
- Identifying stale, inefficient, extractive, or low-quality gauges.
- Analysing whether CRV emissions remain justified by revenue, liquidity, strategic value, or market share.
- Analysing and recommending pool parameter improvements.
- Supporting BD with asset pre-screening, new market opportunities, and liquidity synergies.
- Helping define public dashboards, monitoring tools, frontend risk indicators, yield sources breakdowns, and user-facing risk disclosures.
These areas are valuable, but secondary to the immediate need for risk assessment and market monitoring.
KPI Framework
Teams should propose their own KPIs. Suggested examples include:
- Review coverage for in-scope proposals before DAO vote.
- Monitoring coverage for active in-scope markets.
- Response time for critical market-risk alerts.
- Quality and follow-through of risk escalations.
- Frequency and completeness of public DAO reports.
- Delivery of reusable models, dashboards, alerts, documentation, or runbooks.
KPIs should be measurable, realistic, and tied to the proposed scope.
Proposal Requirements
Interested teams should submit:
- Scope they are willing to cover: crvUSD / mint markets, Llamalend / isolated markets, or both.
- Optional responsibilities they can take on.
- Proposed KPIs and reporting cadence.
- Team background and relevant experience.
- Tooling, models, monitoring approach, and expected dependencies.
- Operated services during the mandate.
- DAO-owned or DAO-accessible deliverables after the mandate.
- Code/model ownership, access terms, documentation, and handoff plan.
- Expected coordination needs with Curve contributors.
- Budget request, payment structure, and proposed trial or review period.
Teams may propose either a full-service model, a tooling-and-handoff model, or a hybrid model where monitoring is shared with existing Curve contributors.
There is no fixed budget at this stage. Teams should propose the responsibilities they can realistically take on, along with the budget required to execute them properly.
If teams have questions or topics they’d prefer to discuss privately before submitting proposals, they can reach out to Swiss Stake via Discord or Telegram. All other discussion is expected to happen in this thread.
Teams are encouraged to submit proposals within two weeks of this post. Later proposals may be considered at the DAO’s discretion, but timely submissions will be prioritized.
After discussing the CFP with several contributors, I’d like to clarify one point that wasn’t explicit enough.
The DAO is looking for lean, focused proposals. The priority is robust risk assessment and market monitoring, not recreating the previous mandate in its entirety.
Teams are encouraged to propose the smallest scope that delivers meaningful value, with optional responsibilities clearly separated. Reusing existing work and leaving behind reusable tooling, models, documentation, or other DAO-owned assets is strongly encouraged.
The DAO has intentionally not set a fixed budget. Teams should propose the scope they can realistically deliver, along with the corresponding budget.
Thanks to everyone who submitted a proposal.
The proposals vary significantly in scope, operating model, readiness, team size, ownership terms, and cost. It would therefore make sense to put them on a more comparable basis before moving to DAO votes.
Swiss Stake will coordinate a structured review of the proposals, with the goal to assess technical and operational fit. We will then publish our findings. The final appointment and funding decision remains with the DAO.
Next steps
Swiss Stake will prepare a concise standardized comparison of the proposals, focusing on key differences in scope, capabilities, readiness, team capacity, ownership, and cost.
We will post a common set of clarification questions, alongside any proposal-specific questions, where we will appreciate if each proposer can reply in a timely manner.
After reviewing the responses, Swiss Stake will publish a comparison and operational assessment, including strengths, concerns, and trade-offs, and potentially a shortlist. Depending on how the review went, we might also recommend a specific package.
We would then move to the process of selecting a finalist. The exact process for this is tbd, currently a Snapshot-based solution seems to be sufficient.
After a finalist is picked by the DAO, we will move to an onchain vote to confirm.
Expectations for proposers
We will share a standardized set of clarification questions shortly.
We are open to teams exploring collaboration where it makes sense, particularly if capabilities are complementary. Any such collaboration should aim for clear accountability, a well-defined division of responsibilities, minimal overlap, and a coherent budget and operating structure. If this is explored by any of the teams, Swiss Stake can help with introductions.
We appreciate the time and effort that has gone into these submissions and look forward to reviewing the next round of clarifications together with the DAO.