Policy enforcement for smart accounts
Programmable permissions for onchain accounts.
Define what operators and automation may do. Matador compiles those rules and evaluates actions routed through a supported account integration.
The permission problem
Delegation should define the job—not hand over the account.
Manual approvals slow routine work. Broad keys let operators and bots do more than the workflow requires. Matador puts the agreed boundary in the execution path.
Enforcement applies to actions routed through the configured account integration.
Policy as code
Write. Compile. Enforce.
Keep policy authoring separate from account execution, with a clear path from readable intent to an onchain decision.
- 01
Write
Express authorized actors, targets, functions, values, and conditions in readable policy source.
- 02
Compile
Turn the policy into compact bytecode that the onchain interpreter can evaluate.
- 03
Enforce
Install it through a supported account integration. Actions outside the policy revert.
Where it fits
Built for delegated execution.
Start with the operating job you need to delegate, then define the narrowest authority that job requires.
DeFi automation
Let keepers rebalance, harvest, and unwind within explicit call, value, and state constraints.
Explore use caseAsset management
Give portfolio operators room to execute without granting authority outside the mandate.
Explore use caseDAO treasury operations
Move routine payments within approved recipient, function, amount, and budget boundaries.
Explore use caseTrust starts with precision
Control means being clear about the boundary.
Matador can make configured constraints executable. It does not guarantee liveness, replace careful policy design, or detect every possible exploit.
Enforcement is scoped
Matador governs execution paths routed through a configured, compatible account integration.
Custody stays with the account
The interpreter evaluates policy. It does not take custody of the account's assets.
Rejections fail closed
Failed policy checks, empty policies, and malformed callable bytecode revert instead of passing silently.
The security model stays visible
Policy correctness, adapter context, authorization, chain support, and external data sources still matter.
For builders
When you are ready for the machinery.
Matador separates policy authoring from account execution. Inspect each layer, its interfaces, and the integration trust boundary.
Author
Policy language
Express callers, targets, selectors, values, and conditions.
Transform
Compiler
Convert readable policy source into callable bytecode.
Evaluate
Interpreter
Evaluate compiled policy against supplied execution context.
Connect
Account integrations
Route supported smart-account execution through policy checks.
Choose your next step
Define the boundary. Let the work move.
Start with the workflow you need to govern, or bring the architecture to the people who will implement it.