Base Level Locks
Create, fund, draw down, and cancel. All operations are authorised by the protocol itself. Funds can only move to pre-defined destinations.
The settlement rail agents choose. Security by default. Control on demand.
Agent-to-agent settlement is failing at the layer it depends on most. Smart contracts were designed for human-supervised transactions, but autonomous agents transact continuously and without oversight, which exposes every weakness in the custody model they rely on.
Concordium handles it at the protocol level through cryptographic credentials and zero-knowledge proofs, linking every agent to an accountable human or entity while keeping that identity private.

Funds sitting in a smart contract are funds exposed. A bug or hack can drain them entirely. Agents shouldn’t have direct access to funds, only release or cancel a locked amount.
When a smart contract is compromised, the blast radius is unlimited. Every user of that contract is affected.
Smart contracts assume a predetermined path. Agents operating unsupervised act dynamically, as opposed to the strict rules of a smart contract.
Smart Contracts | Protocol-Level Locks | |
|---|---|---|
Custody model | Funds held by the contract | Funds stay in user custody, ring fenced by the protocol |
Failure risk | A single exploit can drain every user | Bounded by design, no honeypot to attack |
Control boundaries | Defined in contract code, enforced by code | Enforced by the protocol itself, with optional contract logic on top |
Suitability for autonomous agents | Designed for pre-deterministic flows | Built for continuous, dynamic agent activity |
Concordium's Protocol-Level Locks hold funds in protocol-enforced escrow.
Create, fund, draw down, and cancel. All operations are authorised by the protocol itself. Funds can only move to pre-defined destinations.
Layer business logic on top via smart contracts: spending limits, daily allowances, counterparty restrictions, time-based conditions.
Funds never leave your custody. It’s the combination of base level locks and enhanced locks that shield the funds from chain level threats and rogue agents.
Every agent payment on Concordium follows the same flow, with two possible outcomes at the end.
Agent initiates.
The agent acts on behalf of its verified principal, within an authorised scope.
Conditions set.
Spending limits, approved counterparties, and delivery requirements are attached to the transaction.
Funds locked.
The amount is ring-fenced in a Protocol-Level Lock. Custody stays with the principal.
Counterparty acts.
The counterparty either delivers against the agreed conditions or fails to.
Settlement resolves.
If conditions are met, funds are released to the counterparty. If not, funds return to the principal. No honeypot, no recovery process.
Protocol-Level Locks are what make unsupervised agent payments viable. Combined with sponsored transactions and x402 integration, Concordium becomes the settlement layer agents choose.



Protocol-Level Locks are coming soon. Explore the technology or talk to us about agent settlement for your use case.
The basics about TMMFs on Concordium.
The process by which two autonomous agents exchange value on-chain without a human approving each transaction. It requires a settlement layer that can hold funds, enforce conditions, and resolve outcomes without supervision.
Smart contracts hold custody of funds, which turns every contract into a honeypot exposed to a single exploit.
Through Protocol-Level Locks that ring-fence funds in protocol-enforced escrow rather than handing custody to a contract. Funds stay with the principal, release only when conditions are met, and revert automatically if they are not.
Three layers working together: verified identity so counterparties know who is transacting, protocol-level settlement so funds are never exposed in honeypots, and compliance-ready rails so regulators can audit when required. Concordium provides all three at the base layer rather than as application-level add-ons.