Programmable Security for On-Chain Assets
Move beyond rigid multi-sigs. Define granular, trustless permissions with a human-readable DSL.
The Permission Interpreter
Matador is the operating system for on-chain permissions. It replaces rigid multi-sig signing ceremonies and opaque custom smart contracts with a flexible, programmable Permission Interpreter.
By separating logic (the policy) from execution (the smart account), Matador unlocks a new era of automated, trustless asset management.
Why Matador?
Traditional on-chain security forces a trade-off between security (slow, manual multi-sigs) and efficiency (risky, unrestricted EOA keys). Matador eliminates this trade-off.
1. Trustless Delegation
Don't trust the manager. Trust the math.
In a traditional setup, you either hold the keys yourself (bottleneck) or give them to a manager (risk). Matador allows you to define exactly what a manager can do, when they can do it, and how much they can touch.
"You can trade Uniswap V3, but only for ETH/USDC, only if the price is within 5% of the oracle, and never more than 10% of the TVL per day."
This isn't a legal agreement. It's bytecode enforced by the Ethereum Virtual Machine (EVM).
2. Infinite Granularity
Logic beyond allow-lists.
Most permission systems are binary: "Allow" or "Deny." Matador is expressive. Using our Domain Specific Language (DSL), you can write policies that understand the nuance of DeFi:
- Parameter Checks: "Allow
swap, but only ifrecipient == vault." - Stateful Guards: "Allow
withdraw, but limit to100 ETHper week." - Oracle Integration: "Allow
liquidateonly ifhealthFactor < 1.05."
3. Operational Velocity
Governance at the speed of software.
DAOs and institutions move slowly because every decision requires a signing ceremony. With Matador, you approve the strategy once, then let the operators execute freely within those bounds.
- Before: 5-of-8 signers must wake up to rebalance a pool.
- With Matador: The rebalance script runs automatically. The transaction only succeeds if it adheres to the pre-approved safety policy.
The Revolution: Matador vs. The Rest
| Feature | 🐢 Multi-Sig | 📝 Traditional RBAC | 🐂 Matador |
|---|---|---|---|
| Speed | Slow (Manual Signing) | Fast | Instant |
| Expressiveness | Low (Binary) | Medium (Role-based) | High (Turing-complete logic) |
| Trust Model | Trust the Signers | Trust the Admin | Trust the Code |
| Upgradability | N/A | Hardcoded | Hot-swappable Policies |
| Gas Cost | High (Signatures) | Medium | Optimized Bytecode |
Solutions & Use Cases
Matador isn't just a dev tool; it's a business enabler.
DeFi & Yield
Automate complex strategies like delta-neutral farming without exposing funds to theft.
DAO Treasury
Move from 'vote-to-execute' to 'vote-to-authorize'. Streamline grants and ops.
Institutional Finance
Bake regulatory compliance (KYC, AML, nav limits) directly into the asset's bytecode.
Structured Products
Build on-chain ETFs, options vaults, and managed indices with cryptographic safety.
Get Started
Ready to write your first policy?