# \#665 Canton Risk Engine: governed risk parameters for lending and vaults, seeking a champion

**URL:** <https://forum.canton.network/t/665-canton-risk-engine-governed-risk-parameters-for-lending-and-vaults-seeking-a-champion/9453>\
**Category:** \#sig-defi-liquidity\
**Created:** [November 4, 2026, 11:30am UTC](https://forum.canton.network/t/665-canton-risk-engine-governed-risk-parameters-for-lending-and-vaults-seeking-a-champion/9453 "2026-11-04T11:30:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![woof-software](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/woof-software/32/7662_2.png) [@woof-software](https://forum.canton.network/u/woof-software)\
**Post date:** [November 4, 2026, 11:30am UTC](https://forum.canton.network/t/665-canton-risk-engine-governed-risk-parameters-for-lending-and-vaults-seeking-a-champion/9453/1 "2026-11-04T11:30:05Z")

</div>

Hi all, Mykola from Woof. We build and run DeFi infrastructure for Compound, and we’re proposing to bring the risk-management patterns we run there to Canton and Zenith: the Configurator pattern for governed parameter changes, the CAPO approach to correlated-asset prices, and reserve-growth tracking. #665 is not yet funded.

The deliverables would be MIT and Apache-2.0, and nothing depends on a service Woof runs:

- Milestone 1: an on-chain risk-parameter Registry in Solidity. Each namespace has its own governance and timelock, risk-reducing changes apply after approval while loosening ones wait the full timelock, there is an emergency pause, and no registry-wide admin.
- Milestone 2: an ERC-4626 vault and a lending market integrated with the Registry on Zenith testnet, plus a Daml governance example with a risk-observer role on a local Canton ledger.
- Milestone 3: an open simulator (historical replay, stress tests) and a self-hostable dashboard.

Price feeds stay with the oracle layer; the CAPO approach shapes how the simulator and the risk parameters treat oracle-induced risk, not a price feed of our own. The proposal does not build a security-monitoring stack.

We’re requesting 1,560,870 CC across three milestones. Milestone 3, 30% of the budget, is paid only after an external Canton DeFi team integrates the Registry in a test environment and confirms it publicly.

Proposal: [Proposal: Canton Risk Engine by Noosphere-314 · Pull Request #665 · canton-foundation/canton-dev-fund · GitHub](https://github.com/canton-foundation/canton-dev-fund/pull/665)

We’re looking for a Tech & Ops Committee member willing to champion it.