DECENTRALIZED AI INFERENCE PROTOCOL
TESTNET — BUILDING IN PUBLIC

AI quota ran out?
Use someone else's.

Veil connects you to idle AI capacity worldwide. Pay per token. No subscription needed.

Project Status — Testnet
[x]Protocol design + whitepaper
[x]Core implementation (36/36 tests)
[x]E2E: Consumer → Relay → Provider
[x]Streaming + envelope encryption
[ ]Multi-provider support
[ ]On-chain settlement (Solana)
[ ]TOKEN economics + Points
[ ]RBOB build system live
Scroll to Explore
>PROVIDE & EARN

Share idle AI capacity. Earn USDC + TOKEN rewards.

$ npx veil init --provider
Then run: veil provide start
>USE AI

Access top AI models. No KYC. Pay with crypto (staged).

$ npx veil init
Then run: veil start
>RUN A RELAY

Earn relay fees with a $3/month VPS. No GPU needed.

$ veil relay start --public

✓ Registered with bootstrap
✓ Earning relay fees...
Anyone with a VPS can relay traffic and earn
Solana///QUIC///WASM///Rust///TypeScript///E2E Encryption///Optimistic Settlement///Fraud Proofs///TEE (SGX/SEV)///Merkle Trees///Ed25519///ChaCha20///X25519///Solana///QUIC///WASM///Rust///TypeScript///E2E Encryption///Optimistic Settlement///Fraud Proofs///TEE (SGX/SEV)///Merkle Trees///Ed25519///ChaCha20///X25519///
01

Protocol Design

Three roles. One network. No central authority. Providers share idle AI capacity through relays. Consumers access models through accountless, privacy-preserving routing. Settlement evidence stays on the main path.

Request Flow Architecture
CONSUMER / clawd
1
RELAY
VERIFYSTRIPWITNESS
5
PROVIDERWASM SANDBOX
Settlement Layer
SETTLEMENT (staged)
1Consumer encrypts prompt, sends to Relay
2Relay verifies identity + balance
3Relay strips identity, forwards to Provider
4Relay records settlement witness
5Provider processes in WASM sandbox, returns result
6Result returned to Consumer via Relay
Providers Online
1 (testnet)
Relays
Community-run
Tests Passing
36/36
Models Available
12
veil@protocol:~
bash 5.2.15
Boot Sequence
_
System Overview

Protocol Core

Decentralized inference layer with cryptographic privacy guarantees.

>Cost:Usage-based (quote units)
>Latency:Low overhead vs direct API
>Privacy:Split visibility across roles
>Encryption:X25519 + ChaCha20
02
Trust architecture. Privacy-preserving by design.

Security and Privacy

LIVE

Open source. Security by math and economics, not obscurity. Four layers. Each works even if providers modify their code. Identity coupling reduced through role separation. Split visibility across roles.

Layer Inspector
LayerLayer 1
NameCRYPTOGRAPHY
Bypass DifficultyImpossible
Depends OnMathematics
Components> E2E Encryption> Ed25519 Signatures
01
Baseline
Math + Economics
02
Open Source
MIT License
03
Trust Model
Role separation
04
Auditable
By Anyone
03
Decentralized access

Network & Install

LIVE

clawd is the only way to access Veil. No public API gateway. No API keys. A local OpenAI-compatible gateway that Cursor, Windsurf, or any tool can connect to.

C
R
R
P
R
R
P
R
P
C
C = ConsumerR = RelayP = Provider
Nodes Online2 (testnet)
ThroughputAdaptive
Latency p99<50ms
Packet Loss0.001%
veil@protocol ~ install
# Share idle AI capacity

$ npx veil init --provider
$ veil provide start

> Provider registered.
> Wallet: 7xK2...3mNp (auto-created)
> Models: claude-sonnet, claude-opus
> Status: ONLINE
> _
ProtocolQUIC
TransportE2E TLS
LatencyLow
BandwidthAdaptive
04
Sustainable incentives

Token Economics

Seven phases: Points, TGE, Staking, Pricing, Settlement, Burn, DAO. 1B fixed supply with deflationary burns. Revenue-proportional elastic release prevents death spirals.

Phase 0: Points + USDCStage 1/7
1  // Phase 0: Points + USDC (Month 0-3)
2  provider.reward = {
3    usdc: transaction.amount * 0.80,
4    points: consumer.usdc_spent * RATE
5  }
6  relay.reward = { points: witness_count * RATE }
7  genesis_bonus = first_30_days ? 5x : 1x
8  max_monthly = 500_000 // per provider
Pipeline Info
PointsDAO
Revenue Split80% / 10% / 10%
ReleaseElastic (Revenue)
Supply1B Fixed
Anti-SybilPoints = USDC spent
05
Emergent development

Build

Satoshi didn't design mining pools. He wrote a few rules. Pools, farms, exchanges, Lightning Network — all emerged on their own.

Linux wasn't planned by a committee. Wikipedia wasn't designed by an architect. Bitcoin wasn't managed by a CEO.

They were given rules. The rest emerged.

Veil Build works the same way.

VEIL BUILD PROTOCOL — 4 RULES
R1Code that passes verification can be merged.
R2Merge requires K independent stake signatures.
R3Protected modules require higher threshold.
R4Surviving code earns future revenue share.
INFERENCENetwork generates revenue
TREASURYFunds accumulate
BUILD REWARDSContributors earn share
BETTER PROTOCOLCode improves

Two lungs. One organism.

The inference network funds development. Development makes the inference network better.

← cycle repeats →
veil build — autonomous development
$ veil build
Scanning veil-protocol repos...
Found: 2 failing tests, 1 desired state
[1] core — relay timeout not handled
[2] core — TODO at src/provider.ts:42
[3] core — DESIRED: provider reputation (500 PTS) *
Select (or 'auto'): auto
Working...
✓ All tests passing
PR #42 created → awaiting verification

Linux wasn't planned. Wikipedia wasn't designed. Bitcoin wasn't managed.

They were given rules. The rest emerged.

Start Building
Rules4
VerificationAutomated
StakeProgressive
RevenueAnchored
>
Interactive

Terminal

Explore the protocol. Type commands to interact with the Veil network.

veil@protocol ~ interactive
Welcome to Veil Protocol Terminal v1.0.0
Type "help" for available commands.
 
$