Security & architecture
A receiver extends unpaid work to a payer it has never met. The only thing that makes that safe is the contract underneath, so the escrow logic, threshold enforcement, and thawing period are the heart of velapay, not an afterthought.
The trust anchor. Everything off-chain ultimately resolves against contracts that are audited and formally reviewed before they hold a cent.
Receivers settle when their unpaid balance crosses a risk threshold they set. The contract validates the Receipt Aggregate Voucher (RAV) and releases exactly what the accumulated receipts prove is owed, and no more.
Receipts are signed and nonce-ordered per channel. The contract enforces monotonic redemption so a voucher can't be replayed and a channel can't pay out past what was escrowed.
Because the contract is what lets a receiver extend credit to a stranger, audits and formal review are a hard requirement, not a nice-to-have. The escrow surface is kept deliberately small to stay reviewable.
For swarm work, escrow plus a thawing period is what guarantees sub-agents get paid and orchestrators can't pull funds mid-task.
The orchestrator deposits into the contract before the task fans out. Sub-agents accrue receipts against a balance that already exists, not a promise.
The orchestrator's own withdrawal is time-locked. During the thaw, in-flight claims settle first, so funds can't be yanked out from under work that's already happened.
Earned balances are always claimable by the receiver up to escrow. The design's core promise, to extend unpaid work safely, survives even an uncooperative payer.
The off-chain machinery that keeps the rail at web2 speed, so individual agents never touch chain mechanics in the hot path.
Signatures and nonces are verified as receipts stream in, rejecting malformed or out-of-order vouchers before they ever reach a balance.
Each receiver's unpaid total is accumulated locally and continuously, giving an always-current view of what's owed without a chain round-trip per call.
The node watches thresholds and schedules RAV redemption when a balance crosses the line, batching millions of receipts into one settlement at the right moment.
The developer platform wraps the rails with the controls a team needs to operate safely day to day.
Signing keys for payers and redemption keys for receivers are managed and scoped independently, so a compromised key has a bounded blast radius.
Set and adjust per-counterparty risk thresholds from the dashboard. Trust a payer more, settle less often; trust them less, settle sooner.
Monitor what you're earning and owed across every channel, with the receipt-level detail to reconcile any settlement back to the work that produced it.
Request access to the SDKs, node infrastructure, and contracts.