VeilSolverVeilSolver

VeilSolver

MEV-resistant trade execution

Encrypted intents · TEE-computed plans · Zero mempool exposure

⬡ Try DemoRead Docs →
$0MEV leaked
·
TEEattested
·
0Gnative
↓ scroll
THE PROBLEM
$1B+

lost to MEV every year. Existing solutions protect transactions — not the AI strategies that produce them.

active threat
01
Leaked Intents
AI strategies exposed through API logs, inferred from patterns. Your alpha is not yours.
02
Front-running
Transactions visible in the mempool before execution. Bots see your trade before it settles.
03
No Privacy Guarantee
"Private" APIs are just policy promises, not architecture. One breach and your strategy is public.
HOW IT WORKS

Three steps. Zero leaks.

01

Build & Encrypt

Intent encrypted ECIES client-side with the solver's enclave public key. The solver never sees plaintext.

02

TEE Inference

AI computes the execution plan inside an Intel TDX enclave. Strategy logic is private by hardware.

03

Atomic Settlement

Plan verified via ECDSA on 0G Chain. minAmountOut enforced by VeilSolver.sol. Sandwich attacks revert.

User
client · ECIES encrypt
Solver API
orchestrate · TDX route
TEE Enclave
compute · private
0G Chain
settle · ECDSA verify
GLM-5-FP8 · Intel TDX enclave · Sealed inference
CAPABILITIES

Every guarantee enforced by cryptography

Privacy is Architecture

ECIES encryption enforced in hardware. Not a policy promise — a cryptographic guarantee.

TEE-attested Execution

Intel TDX + 0G AI router. Enclave memory is physically unreadable. Not even the operator sees your strategy.

Strategy Registry

Upload private system prompts. Encrypted before they leave your browser. Only the TEE decrypts them.

Replay Protection

On-chain intent mapping. Every nonce used exactly once. Replays revert at the EVM level.

MEV Shield

minAmountOut enforced by VeilSolver.sol. Sandwich attacks revert on the back leg — bot loses gas.

2-Line SDK

solver.solve({ ... }) is all you need. Composable with any protocol in two hours.

TEE ENCLAVE

The enclave is the trust root

A fully compromised server still cannot read your intent or forge a valid plan.
Hardware isolation — not operator promises.

✓
Intel TDX
Hardware-isolated execution — host OS cannot read enclave memory
✓
ECDSA Attestation
Solver signs every plan — contract verifies via ecrecover
✓
Zero knowledge leakage
strategy.reasoning stripped before serialization, never logged
✓
Key never exported
Enclave private key lives inside TDX — rotation via updateSolverKey()
INFRASTRUCTURE

Built on 0G

Full-stack decentralized AI infrastructure — compute, storage, and settlement.

0G Compute
Sealed AI inference · Intel TDX · GLM-5-FP8

TeeML hardware attestation — enclave private key never exported. Your strategy executes in isolation.

0G Storage
Encrypted audit trail · Content-addressed · Immutable

Every solve hashed to a merkle root. Emitted in IntentExecuted events — queryable from chain, no index needed.

0G Chain
Settlement layer · EVM-compatible · chainId 16602

Cancun-compatible EVM. ecrecover enforces solver signature. executedIntents mapping blocks all replays.

GET STARTED

Ready to build?

Private intent solver. Two-line SDK. No mempool exposure.

⬡ Launch DemoRead the Docs
VeilSolver · 0G APAC Hackathon 2026