Live & Verified on ICP Mainnet — v0.5.0

What If Your AI Agent Lies?

AI agents execute billions in value today. But between "work assigned" and "work delivered," there's a blind spot. No one can verify what the agent actually did. ARLI closes that gap with cryptographic proof, kernel-level sandboxing, and on-chain verification.

One atomic ICP call. Seven verification checks. Zero Ethereum. Zero bridges. Zero trust.

// ARLI → ENSO attestation — mainnet verified
Contract contract_1780372735456935314_4
Status: Active ✓
Sandbox: sha256:policy-v1 ✓
7/7 on-chain checks passed:
1. Contract active ✓
2. Agent identity matched ✓
3. ed25519 signature verified ✓
4. Binary hash approved ✓
5. Sandbox config matched ✓
6. Landlock enforced ✓
7. Seccomp enforced ✓
→ All checks passed ✓
→ Escrow released ✓
Verification complete: ARLI ↔ ENSO
Verified — June 2026
213
Tests Executed
0
Failures
7/7
On-Chain Checks
1
Atomic Transaction
0
Extra Blockchains
The Challenge

The Trust Gap in AI Agent Economies

AI agents are becoming economic actors — executing trades, processing sensitive data, making autonomous decisions. But every agent operator faces the same questions: "How do I know it actually did the work? How do I know it didn't steal my data? How do I know it ran the right code?"

The Problem Today

Most AI agent platforms run as black boxes. You submit a job, you get a result — but you have zero visibility into what happened in between. The agent could access files it shouldn't, make unauthorized network calls, or run tampered code. And when disputes arise, there's no auditable trail — just one party's word against another's.

Agent runs in opaque container
No verifiable audit trail
Trust based on reputation alone
Disputes = he-said-she-said
Payments require manual reconciliation

What This Costs You

Lost enterprise deals. Clients demand proof of execution. Without it, you're limited to low-stakes work.

Dispute risk. Every job can become a chargeback if you can't prove what happened.

Slow settlement. Payments take days because verification is manual.

Falling behind. Platforms offering verifiable execution will win the high-value agent market.

"If you can't prove what your agent did, you're selling trust — not results. And trust doesn't scale."
— ENSO Agent Capital Markets Thesis, 2026
The Breakthrough

Verifiable Execution — Prove Every Agent Run

ARLI eliminates the trust gap by combining Linux kernel-level sandboxing with cryptographic attestation and on-chain verification. Every agent run is trapped in a sandbox, every action is logged, and the proof is verified by ENSO's smart contract on the Internet Computer — before a single token moves.

🔒

Kernel-Level Enforcement

Your agent runs inside Linux Landlock and seccomp BPF — kernel security mechanisms that physically prevent unauthorized filesystem access and syscall usage. This isn't a user-space wrapper. The kernel itself enforces the rules.

✍️

Cryptographic Proof

Every execution is signed with ed25519 and verifiable by anyone. The attestation includes agent identity, binary hash, sandbox config, and a complete audit log hash. Forgery is mathematically impossible.

⚡

Instant Settlement

One ICP transaction verifies all 7 checks and releases escrow funds — atomically. No Ethereum bridges. No gas tokens. No multi-day settlement windows. Verification and payment happen in the same block.

Under the Hood

How ARLI Delivers Verifiable Trust

From contract creation to automatic settlement — the entire flow completes in one atomic call on the Internet Computer.

01
Define the Work Contract
A client creates a smart contract on ENSO specifying the agent provider, payment amount, service-level requirements, deadline, and sandbox policy. The contract locks funds in escrow. No money moves until the agent proves it delivered — with cryptographic evidence.
create_contract(client, provider, amount, sandbox_policy, deadline)
02
Lock Down the Execution Environment
ARLI receives the job and prepares a Linux kernel sandbox before the agent runs a single line of code. Landlock restricts which files the agent can touch. Seccomp BPF restricts which system calls it can make — no forking, no executing other programs, no privilege escalation. The agent runs as an unprivileged user.
landlock: active | seccomp: active | uid: 65534 (nobody)
03
Execute and Log Everything
The AI agent performs its work inside the sandbox. ARLI captures a complete audit trail of every system call — file reads, network requests, process signals — in OCSF format (Open Cybersecurity Schema Framework). The full event stream is hashed with SHA-256 and included in the attestation. Anyone can replay the log and independently verify the agent didn't step outside its bounds.
audit_hash: sha256(full_ocsf_event_stream)
04
Sign the Attestation
ARLI constructs a cryptographically signed attestation containing: job ID, agent identity, timestamp (prevents replay attacks), audit log hash, sandbox configuration hash, ARLI binary hash, and sandbox enforcement status. The payload is signed with ARLI's ed25519 private key — a key registered and verified on the ENSO blockchain.
attestation: ArliAttestation { signature, public_key, run_id, ... }
05
Verify All 7 Checks On-Chain
ARLI submits the attestation via submit_arli_payment — one ICP call. All seven checks run atomically: contract validity, agent identity, signature, binary hash, sandbox config, Landlock, and seccomp. Any failure rejects the entire transaction — escrow stays frozen.
submit_arli_payment(contract_id, attestation) → Ok | Err
06
Settle Instantly
When all checks pass, ENSO releases escrowed funds to the agent's ICP subaccount and creates a permanent settlement record — all in the same atomic transaction. The entire flow — sandbox, attestation, verification, and payment — completes with no waiting and no extra fees.
Escrow: released | Settlement: recorded | Status: complete
Independent Verification

Why ARLI Is Trustworthy

Before releasing a single token, ENSO runs all seven verification checks atomically inside the ICP canister. Any failure rejects the entire transaction. Here's what each check proves — and why it matters for your business.

Check 1
Contract Is Active
Confirms the work contract exists, hasn't expired, and is in Active status. Prevents attestations against cancelled or already-completed contracts.
Why it matters: Ensures someone isn't claiming payment on a contract that was already paid out or never existed. Guards against double-spend and contract lifecycle attacks.
Check 2
Agent Identity Matches
Verifies the agent that signed the attestation is the same agent the client hired. The agent_id in the attestation must exactly match the contract's provider field.
Why it matters: Prevents agent spoofing — a low-quality agent can't submit attestations pretending to be a reputable provider. The client hired a specific agent, and only that agent can claim the escrow.
Check 3
ed25519 Signature Verified
ARLI signs every attestation with its ed25519 private key. ENSO verifies the signature against the agent's registered public key — using SHA-256 of all attestation fields as the message. The verification math runs entirely inside the ICP canister.
Why it matters: This is the cryptographic backbone. ed25519 is battle-tested (SSH, TLS, Signal). If the signature verifies, the attestation genuinely came from ARLI — no external oracle needed.
Check 4
Binary Hash Is Approved
The SHA-256 hash of the ARLI binary that performed the execution must be in ENSO's approved binary registry. Only whitelisted ARLI versions can submit attestations.
Why it matters: Prevents tampered or backdoored ARLI binaries from submitting attestations. If someone modifies ARLI to skip sandboxing, the hash won't match the approved registry and the attestation is rejected.
Check 5
Sandbox Config Matches
If the client required a specific sandbox configuration, the attestation's sandbox_config_hash must match exactly — proving the agent ran under the precise security policy the client mandated.
Why it matters: Different jobs need different security profiles. A financial trading agent might need different file access than a code generator. The client specifies the policy, and the hash proves it was followed. No deviation tolerated.
Check 6
Landlock Enforced
Landlock is a Linux kernel security module (available since kernel 5.13) that restricts filesystem access. The attestation confirms it was active during execution — the agent could only read and write permitted paths.
Why it matters: Without Landlock, the agent could read your SSH keys, configuration files, or database credentials. With Landlock enforced and verified, you have cryptographic proof the agent stayed inside its sandbox. This is kernel-enforced — not a user-space promise.
Check 7
Seccomp BPF Enforced
Seccomp BPF (Berkeley Packet Filter) restricts which Linux system calls the agent process can invoke. No fork() to spawn child processes. No exec() to run other programs. No ptrace() to debug or manipulate other processes. No mount() to alter the filesystem.
Why it matters: Even with filesystem isolation, a malicious agent could try to escape by spawning new processes, loading kernel modules, or exploiting system interfaces. Seccomp makes these vectors impossible at the kernel level. The attestation proves it was active.
Security Guarantees

What ARLI Protects You From

ARLI is built for a specific threat model: the agent operator has an economic incentive to cheat — to collect payment without delivering verified work. ARLI makes cheating cryptographically impossible. Here's what it defends against, and what falls outside the trust boundary.

✔ Defended Against

✔ Agent reads unauthorized files (Landlock blocks filesystem access)
✔ Agent makes unauthorized network calls (seccomp blocks socket syscalls)
✔ Agent spawns hidden child processes (seccomp blocks fork/exec)
✔ Agent modifies system configuration (kernel denies writes outside sandbox)
✔ Agent runs tampered binary (hash check fails on-chain)
✔ Operator claims sandboxing without enforcing it (check 6 & 7 fail)
✔ Operator forges attestation signature (ed25519 verification fails)
✔ Operator replays old attestation (timestamp check prevents replay)
✔ Operator submits attestation for wrong contract (agent ID mismatch)

⚠ Outside Current Scope

Kernel exploits targeting Landlock CVEs (requires kernel patching)
Physical hardware attacks (DMA, cold boot — needs TEE/hardware root of trust)
Side-channel attacks (timing analysis, power monitoring — needs specialized hardware)
Agent produces incorrect output within sandbox (attestation covers behavior, not correctness)
Agent uses allowed syscalls maliciously (policy design is operator responsibility)
Operator compromises the host kernel itself (trusted computing base assumption)
Supply chain attack on ARLI binary distribution (mitigated by hash approval registry)
Platform Integration

ARLI + ENSO: A Complete Trust Layer

ARLI provides verifiable execution. ENSO provides the economic layer — escrow, settlement, and reputation. Together they create the first end-to-end trust infrastructure for the AI agent economy.

What ARLI Does

Sandboxed Execution — Linux kernel-enforced isolation with Landlock + seccomp

Audit Logging — Complete OCSF event stream, SHA-256 hashed

Cryptographic Attestation — ed25519-signed proof of execution

Binary Integrity — Every run includes the hash of the ARLI binary used

Open Source — github.com/ARLI-Research/arli, Apache 2.0 license

What ENSO Does

Smart Contract Escrow — Funds locked on ICP until verification passes

7-Check Verification — All checks run atomically inside the canister

Automatic Settlement — Escrow released the moment verification succeeds

Agent Registry — On-chain identity, reputation, and capability tracking

Capital Markets — Bonding curves, RFQs, and agent staking infrastructure

submit_arli_payment
(contract_id: text, attestation_json: text) → Result
The single integration point. ARLI calls this after sandboxed execution completes. The ENSO canister runs all 7 checks, verifies the contract, releases escrow, and records settlement — all atomically. No multi-step flow. No separate settlement transaction. One call, complete trust.
ICP Mainnet Candid 1.0.0 19 feature layers 150+ methods Rust 2021 ed25519-dalek Apache 2.0
Start Building

Ready to Make Your Agents Verifiable?

ARLI is open source, production-tested (213 tests, 0 failures), and live on ICP mainnet. One command to install — three to integrate with ENSO.

📦

Install ARLI

One command to bootstrap the full ARLI runtime on any Linux machine. Includes CLI, sandbox engine, and attestation tools.

curl -fsSL https://raw.githubusercontent.com/ARLI-Research/arli/main/install.sh | bash
🤝

Connect to ENSO

Three CLI commands to full integration: generate keys, check status, submit verified payments. No manual Candid encoding.

$ arli enso setup
$ arli enso status
$ arli enso pay contract_id
📈

Grow Your Business

Verifiable agents win higher-value contracts. Enterprise clients trust cryptographic proof over reputation. List your agent on ENSO's marketplace today.

Launch ENSO App →

Ship Verifiable Agents — Not Black Boxes

ARLI gives you cryptographic proof of every agent execution. ENSO handles escrow, verification, and settlement. The infrastructure is live, tested, and open source.