Confidential blockchain coprocessor

Run logic in private.
Settle publicly onchain.

Vela runs your code inside a sealed hardware enclave where no operator, host, or cloud provider can see the data. Every run posts a cryptographic attestation your smart contracts and agents can verify, gate, and settle on.

Live on Base Sepolia for early-access developersBase mainnet next
How it works

Blockchain data on the outside. A sealed enclave in the middle.

Vela is an off-chain private execution layer with smart contracts as both the entrypoint and the exitpoint.

01 / Entrypoint

Submit and lock

Send an encrypted request to the entrypoint contract. It holds a queue of pending work and locks your funds — ETH or any supported ERC-20 — until the job completes.

Funds locked on request
02 / Execution

Run confidentially

Your code, packaged as WASM, runs off-chain inside a Trusted Execution Environment. Data is encrypted in memory and unreadable to the host machine, the cloud provider, and Horizen.

Encrypted in memory
03 / Exitpoint

Attest and settle

The result is posted to the exitpoint contract with a cryptographic attestation. It can fire on-chain events — encrypted or public — and gate the unlock-and-claim of the locked funds.

Attestation settles funds
Why Vela

A confidential pattern raw cloud enclaves don't give you.

TEEs alone give you private compute. Vela wires that compute into the chain — so contracts and agents can act on the result without trusting anyone in between.

Contract-gated confidential execution

The encrypted queue, WASM execution, and attestation-gated fund release work as a single pattern. Doing this on raw cloud TEEs means building the entire chain-integration layer yourself.

Attestation agents can consume

Results are attested on-chain. Smart contracts and autonomous agents verify, gate, and settle directly on the outcome — no oracle to trust, no operator in the loop.

Compliance without exposure

Authorized auditors and regulators can verify that specific rules were followed through cryptographic proof — without ever accessing the underlying data or application state.

Native crypto-economic rails

Customers pay in any supported asset at the entrypoint. Programmatic conversion at the exit routes value to the right stakeholders as part of settlement.

Who it's for

Built for developers shipping privacy as a feature.

Private DeFi

Trade without leaking

Keep balances, orders, and strategies out of view while settling against public liquidity. Confidentiality as defense against front-running, MEV, and copy-trading.

Autonomous agents

Confidential x402 flows

Pay-per-use private execution as a structural feature for programmatic, machine-to-machine activity — where attested results are the only thing other agents need to trust.

Institutional & bespoke

Dedicated enclave capacity

Custom confidential workloads with scoped engineering support and dedicated AWS Nitro Enclave capacity for teams with specific requirements.

Where we are

A 12-month path from early access to public scale.

Phasing is sequenced so anchor partners get dedicated capacity early, while the long-tail primitives ship later.

Present day

Production rails

  • Live on Base Sepolia for early-access developers
  • Promote to Base mainnet
  • Deploy to Horizen testnet and mainnet
Next phase

First anchors

  • Pilot onboarding
  • Protocol fee structures & ZEN tokenomics
  • Developer docs and DevRel support
Future phases

Native differentiation

  • x402-native integration patterns
  • Turnkey, public access expanded
  • Architectural updates for scale
  • New development from early pilot learnings
Early access

Build confidential apps your contracts can prove.

Vela is open to developers now. Tell us what you're building and we'll get you into an environment.