Making financial privacy a public good
Payments are the last piece of everyday finance that still leaks by default. We think confidentiality should be built into the rails, not sold as a premium add-on.
By the Orivan team · July 14, 2026 · 6 min read
Public ledgers were never meant to be public diaries
Open blockchains made settlement transparent, verifiable, and permissionless — and that transparency is a genuine advance. But it came with a side effect nobody signed up for: every transfer you make is a permanent, world-readable record. When you pay a contractor in USDG, both of you can see the other's entire balance history. When a fund rebalances a tokenized-stock position, anyone watching the chain can front-run the move. Transparency at the protocol layer quietly became surveillance at the human layer.
Privacy is not about hiding wrongdoing. It is the ordinary condition under which people conduct their financial lives — the same reason your bank statement is not posted on a billboard. On-chain, we lost that condition by accident. Our mission is to give it back without giving up the guarantees that made public chains worth using in the first place.
Why privacy belongs in the base layer
Bolt-on privacy tools tend to fail in the same way: they create small, isolated pockets of confidentiality that are easy to deanonymize the moment funds enter or leave. Real privacy is a property of the whole system, and it gets stronger with scale. The more people share a common shielded environment, the harder any single transaction is to trace. That is why we treat confidentiality as infrastructure — a public good that everyone benefits from and no single user has to pay to bootstrap.
Building on Robinhood Chain lets us put that infrastructure exactly where the assets already are: fully-backed USDG and tokenized equities, settling on a chain designed for throughput. Privacy that lives next to real assets is privacy people will actually use.
The shielded-pool approach
At the center of Orivan is a zero-knowledge shielded pool. When you deposit, your funds join a large common set and you receive a secret note that only you can spend. Transfers happen entirely inside the pool: a zk proof convinces the network that a spend is valid — the note exists, it has not been spent before, and amounts balance — without ever revealing who is paying whom, or how much.
Two pieces make this practical for everyday use. Stealth addresses let a recipient hand out a single public key while every payment lands at a fresh, unlinkable one-time address, so an observer cannot cluster a person's incoming funds. Gasless relayers let someone claim or send a shielded payment without holding native gas in a fresh wallet — the relayer submits the transaction and is compensated from inside the pool. Together they remove the two most common ways users accidentally deanonymize themselves.
Confidential without being opaque
Privacy and accountability are not opposites. A shielded pool can be designed so that users hold selective-disclosure keys: you can prove to an auditor, a counterparty, or yourself exactly what a given transaction was, without exposing it to the entire world. The default is confidentiality; disclosure is a choice you make, not a condition forced on you by the ledger. We would rather give people a precise scalpel than an all-or-nothing switch.
The roadmap
We are shipping in stages. First, shielded USDG transfers with stealth addressing and relayer-sponsored gas — private, everyday payments that feel like sending a normal transaction. Next, confidential transfers for tokenized stock, so a position can move without broadcasting intent to the market. From there, an open relayer network and public tooling so that anyone can run infrastructure, audit the circuits, and build on top of the pool.
None of this matters if it stays a research demo. The measure of success is simple: privacy that is on by default, cheap enough to ignore, and strong because everyone shares it. That is what turning financial privacy into a public good actually looks like.