Security Review
How Adula's code is reviewed before release, and by whom.
Palladium Labs runs two separate teams: one builds Adula, and the other reviews its security. Adula's Daml contracts are reviewed by the security team, which works independently of the engineers who wrote the code.
This is an internal review by a separate team within Palladium Labs. It is not an independent third-party audit.
The security team
This is the same team that worked alongside Halborn on the audit of Alpend, Palladium Labs' money market on Canton. The findings and review methods from that engagement have been applied to Adula, from oracle handling and fee accounting to liquidation safety and parameter controls.
Scope
The review covers Adula's core contracts:
- Vaults: opening, minting, collateral changes, repayment and closing
- Fee accounting: origination fees, fixed-rate interest accrual and the liquidation reserve
- Liquidations: threshold checks, debt repayment from the Stability Vault, collateral seizure, conversion back to ONE and return of any surplus
- Stability Vault: deposits, withdrawals and yONE exchange-rate accounting
- Redemptions: routing to the highest-LTV vaults, the redemption fee, and the market-maker whitelist
- Oracles and administrative controls: price handling, parameter changes, pause flags and collateral onboarding
Areas of focus
Building on the Alpend engagement, the review pays particular attention to:
- Conservation of value. ONE supply always equals total vault debt, and every operation conserves collateral.
- Liquidation safety. A liquidation always improves the system's position, and a failed conversion never leaves the Stability Vault in a bad state.
- Oracle handling. Prices are checked for freshness, and prices that deviate too far from expected values are rejected.
- Accounting accuracy. Interest, fees and the yONE exchange rate stay correct across partial repayments, redemptions and liquidations.
- Authorization. Every action requires exactly the right parties to sign, and administrative actions go through DecMan.
Limits of a review
A security review reduces risk; it does not prove the code is correct. An internal review is not a substitute for an independent third-party audit. It covers code at a point in time, and does not cover oracle provider behaviour, economic parameter choices, key management, or the Canton Network itself.
Smart contract risk remains the primary risk of using Adula. See the Disclaimer.
Report a vulnerability
If you believe you have found a security issue in Adula, email contact@palladiumlabs.org with a description and steps to reproduce.
Please report privately and give the team reasonable time to fix the issue before disclosing it publicly. Do not test against other users' vaults or funds.