Developers
Build on Veilo
Veilo is infrastructure before it is an app. The privacy layer is designed to be built on by wallets, dApps and developers who never want to touch a circuit.
What Veilo exposes as infrastructure
The reason a wallet can offer private transfers, private swaps, private positions and private card spending without writing any cryptography is that all of it reduces to the same three operations against the pool.
| Primitive | What an integrator gets |
|---|---|
| Deposit | Move value from a public wallet into a private balance, with an optional gasless path. |
| Spend with a proof | Authorise a destination and amount from a private balance, without revealing the source. |
| Reissue | Return value from an external interaction back into a private balance. |
| Private execution | A private balance acting on an external protocol, the pattern behind every venue in Private execution. |
New venues, no new cryptography
Veilo SDK
Coming soon
A JavaScript and TypeScript SDK for integrating private transactions into your own application, so you can build privacy-preserving flows on Solana without implementing proof generation yourself.
Simple integration
A small API for deposits, transfers and withdrawals, designed to work alongside any Solana wallet adapter.
Client-side proof generation
Proofs generated in the browser via WebAssembly, so user secrets never leave the device.
TypeScript first
Full type definitions for type-safe development and IDE support.
Relayer integration
Relayer selection and submission handled for you, so a private action is one call.
The intended shape of the API, subject to change before release:
import { Veilo } from '@veilo/sdk'
const veilo = new Veilo(connection)
// Deposit into the privacy pool
await veilo.deposit({
recipient: '@alice',
amount: 1.5,
token: 'SOL',
})What to design against today
The concepts pages are the stable part of this documentation, and they are the right thing to design an integration against while the SDK lands.
How Veilo works
Proof-based ownership and the guarantees that follow from it.
Architecture
What each component is trusted with, and what it is not.
Private execution
The pattern to follow to reach a new venue privately.
Trust model
The assumptions your users will inherit from Veilo.
Compliance
Optional compliance features for regulated use cases are planned. They are designed as capabilities a user or integrator can choose to use, not as a mechanism through which anyone else can compel disclosure. See Trust model.
Stay updated