WAVE
The engine

The WAVE Money Engine

One engine for getting everyone paid — people and agents, on the same rail. The payments, identity, and compliance behind every WAVE stream, so value moves as easily as the video does.

Built once — for every party

Verification, settlement, identity, compliance, and metering are handled by the engine itself. People pay with cards and keys; agents pay over HTTP-402. Same rail, same enforcement.

x402 facilitator

Live

An HTTP-402 facilitator implementing the EIP-3009 “exact” scheme — the payer signs an EIP-712 authorization, the facilitator binds the payer and settles USDC on Base. Live on mainnet.

On-chain settlement

Live

Sign → verify → settle → replay-rejected, proven end-to-end on Base mainnet with real USDC. Atomic replay protection on every settled credential.

Agent identity

Live

Signed platform identity at /.well-known/did.json (did:wave-platform, Ed25519) — so an agent can prove who it is before any charge.

Compliance

Live

OFAC sanctions screening on the credential source address, with per-agent spend tiers — money moves inside guardrails, not around them.

Per-dimension metering

Building

One usage meter across egress, stream-minutes, frames, samples, and reconnects — so every transport is measured and billed the same way. Deployed; rolling out behind a flag.

Signed receipts

Building

A signed, retrievable receipt for every settlement — verifiable proof of what was paid, for both sides. Deployed; rolling out behind a flag.

Fiat on/off-ramp

Building

Fiat rails via Bridge — USD ACH/wire, EUR SEPA, GBP Faster Payments, MXN SPEI, BRL PIX — so a stablecoin rail has a fiat edge on both ends.

WAVE Account

Planned

A did:wave-keyed account that holds a balance and tops up, spends, and pays out across rails — the foundation of the WAVE Wallet. Non-custodial by composition.

WAVE Wallet

Planned

Every party — creator, viewer, and both their agents — holds a wallet on one rail. The 4-party network that makes micropayments for video native.

Every party, one engine

P1Creatorearns + pays out · Bridge · Stripe Connect
P2Creator’s agenttransacts on the creator’s behalf · x402, tier-capped
P3Viewerpays for access + content · Stripe Link
P4Viewer’s agentdiscovers + pays per use · x402 micropayments

Composed, not locked in

The Money Engine composes the best rails rather than locking you in. WAVE’s own x402, OFAC screening, and replay protection are live today; Stripe, Bridge, and Privy compose in under one did:wave account as the WAVE Account and Wallet land. Open protocol where it earns trust; metered where it earns revenue.

See the facilitator