Intent → observe → prove → release
If one step fails, money does not leave. That is the system we ship.
We build on the blockchain
On-chain systems that actually settle.
Waves builds blockchain systems — smart contracts, wallets, deposit rails, and proof engines — for operators who already move value and need the chain to behave.
- Contractsescrow, release, policy
- Railswatch, match, alert
- Walletskeys never in the UI
- Proofhash bound to a ticket
Smart contracts
Escrow and release with a small surface. No mystery minting.
Deposit rails
Watchers that match an on-chain payment to a ticket in real time.
Wallet systems
Custodial or hybrid. Operators see a trail. Users never see a seed.
Token & ledger work
Internal tokens, private books, and a daily reconcile against chain.
Alerts
Wrong network, wrong amount, dust — paged to a human before cash moves.
How a chain build runs
States first. Then code.
- 1
Map the spine
Intent, observe, prove, release. We write the states on a wall before Solidity or Go.
- 2
Threat model
Wrong network, dust, replay, key leak. If we cannot name the failure, we do not ship the rail.
- 3
Build small
Tiny contracts, typed watchers, a ledger that reconciles. No mystery mint, no extra admin god-mode.
- 4
Prove it live
Testnet, then a limited mainnet with dual control. You see a ticket match a hash before we scale.
What stays with you
A rail your treasurer can explain.
States first. Then contracts. You keep the keys — the interface never does.
-
01
Tiny contracts and watchers
Escrow, release, and a watcher that matches a payment to a ticket. No mystery mint.
-
02
Key ceremony notes
Who holds what, how a key is rotated, and a written rule that the UI never stores a seed.
-
03
Book versus chain
A daily reconcile your treasurer can run before anyone goes home.
-
04
Ticket bound to a hash
Every release leaves a proof an auditor can open without a decoder ring.
Tell us the rail you wish existed.
We map the states and the keys before a single contract is written.