Institutional Compliance
Control Framework
Mapping internal controls to on-chain policies.
The Control Framework
For an institution, a "Policy" isn't just code—it's the implementation of a Risk Control Framework.
Mapping Controls to Code
| Internal Control | Matador Implementation |
|---|---|
| "No payments to sanctioned entities" | check SanctionsOracle.isSanctioned(recipient) == false |
| "CFO approval required > $50k" | if amount > 50000 check sender == CFO |
| "Only trade on approved venues" | allow target in [Coinbase_Prime, Uniswap_V3] |
| "Daily loss limit" | check state.daily_outflow < LIMIT |
Segregation of Duties (SoD)
Matador supports role-based logic natively.
- Operator: Can initiate routine rebalancing.
- Risk Manager: Can update risk limits (e.g., max leverage).
- Compliance: Can update the KYC whitelist.
- Admin: Can upgrade the system (Time-locked).
Auditability
Every time a transaction is attempted, Matador emits events. Even failed transactions leave a trace.
- Success: "Policy X allowed Operator Y to send 100 USDC."
- Failure: "Policy X blocked Operator Y (Reason: Limit Exceeded)."
This data can be ingested directly into ERP systems or audit software.