Name: Private Vault
Brand: DEPLOYR
Price: 20 USD
Availability: InStock

Two ways to own it

What you get

Base$20

Ready now

The working app on your own wallet and git, one-click deploy, and the step-by-step guide that makes you the verifiable developer.

You choose: App name
You choose: Logo and accent color

Customfrom $300

Built around you

Reshape it entirely: new features, your flows, your brand end to end, integrations you need. We scope it with you.

Everything in Base
Custom features and design
Priority build

What you own

The whole app, not a starter kit.

The complete Private Vault app: people paid onchain create a private account and prove every payment in their own browser on Miden, so strangers see commitments instead of their income, with a paywall, owner console and vault assistant built in.

Base price · $20

The user app, complete

Every buyer gets the same finished app. Basic branding and copy changes come through a quick form.

Three step onboardingHome

Shown once: public chains made income public, proved on this device, public only when you choose.

Progress and next actionHome

Account, paid, collected and glass check, with balance, notes to collect and readable count.

Private or public paymentsPay

Pick a payee and make each payment a private note or public on purpose, with a warning.

Local proving with device choicePay

Prove on this laptop, an old phone or an optional delegated prover that always asks first.

Out of memory recoveryPay

When a phone stalls the proof is split into smaller transactions, still on the device.

Two views of every paymentPay

What the payer sees next to what a stranger on the explorer sees.

Contacts and scheduled paymentsPay

Saved payees and payments proved on the due morning. Gated behind Pro.

Collect incoming notesCollect

Find private notes addressed to you and consume them so they become spendable.

Receipts and historyReceipts

Commitment, nullifier and block onchain; amount, memo and recipient stay on the device.

Accountant exportReceipts

One encrypted file of the year's payments. Gated behind Pro.

Sunday glass checkGlass

A weekly look at what strangers can read, with a streak and share card.

Plans and settingsMe

Pricing from the owner paywall with crypto checkout, private account toggle, backup and reminders.

Open the full app demo

Add-on

Owner console

Your admin side: revenue, paywall editor, users, rules and the agent log.

Revenue and paywall editorRevenue

MRR from Pro and Team, payouts, incoming USDC, payment methods and live editing of tiers, prices and gates.

Team treasury requestsTeams

Set up private treasuries for collectives and DAOs, decline requests to pool other people's funds.

Rules, agent log and roadmapRules

Delegated prover on or off, ask first, split on low memory, block age check, public warnings; plus the Agent log and priced Roadmap.

Top-up

Growth and referrals

Referral and growth mechanics, switched on when you are ready to grow.

Collective nights and referralsGrowth

Run a collective night, see payer to payee loops and simulate referrals.

The money path, built in

How it earns for you

Private payments proved on your own device are free. People paid onchain every week pay for Pro tools, and small teams and DAOs pay a setup fee plus monthly for private treasuries.

Free$0Private account, private payments, local proving, weekly glass check

Pro$6 a month (owner sets $4 to $9)Saved contacts, scheduled private payments, encrypted export for accountants, priority delegated proving with consent

Team$49 a month plus setupPrivate treasury accounts for small teams and DAOs that pay contributors without publishing every salary

Proving runs on the user's device at no compute cost to the owner. Miden network fees are small; check current terms before charging.

Prices are yours to set. Illustrative, not a promise of income.

Growth loops, built in

How it spreads

Every private payment invites the recipient to collect it in their own vault
The glass share card that travels in freelancer and privacy groups
Collective nights where a group pays each other privately
Early listing on Miden ecosystem directories
Payer to payee referrals worth a free Pro month

Roadmap · build the next phase with us

Where it goes next

v1 included

The private vault

Private account and private notes on Miden
Local proving with split on slow phones
Collect incoming notes
Receipts, glass check, encrypted backup
Paywall, owner console, vault assistant

Included

Invoices and team treasuries

Private invoices with pay links
Team treasuries with roles
Recurring payroll, proved each morning
Viewing keys for accountants

Add-on from $300

Mobile app and bridges

Native mobile app with secure enclave keys
Bridge in from Base and Arbitrum
Selective proofs of income for landlords
Merchant checkout

Add-on from $800

For investors and grant reviewers

The pitch, ready

Ordinary financial privacy for people paid onchain, proved in their own browser on Miden.

Problem: Public chains made paying people easy and made everyone's income readable. A freelancer paid in stablecoins can have her rates, clients and rent added up by anyone with an explorer.

Solution: The Miden web client runs in the page: accounts are private by default, payments are private notes, and STARK proofs are made on the user's device. The chain checks the proof and stores commitments, never the amounts.

Why now: Miden brings client side proving to the browser for the first time, and freelancers are increasingly paid in stablecoins.

Market: Freelancers, creators and small teams paid onchain who want the privacy a bank statement gives them.

The ask: Launch in the first wave of Miden apps and pilot with two freelancer collectives.

Funding is never guaranteed. Check each program's rules.

For hackathons and demo days

Your 2 minute demo

Home: meet Valentina in Bogota on a rain night, paid by a Lisbon studio.
Pay: pay Lucia privately on the laptop and compare her screen with the explorer view.
Pay: switch to the old phone, watch it stall at 61% and split the proof.
Collect: take in three incoming notes.
Glass: run the Sunday glass check and share it; hit the Pro paywall on contacts and pay in USDC.
Owner Agent: the two failures and how the assistant adapted without delegating.
Owner Revenue and Teams: change the Pro price and set up a collective treasury.
Owner Growth and Roadmap: run a collective night, then request private invoices.

Many hackathons require code written at the event. See the Regatta Boardfor each race's rule.

Make it entirely yours

Custom work from $300: your branding, a different payee flow, accountant integrations or a team treasury setup. Scoped on a call.

Custom from $300

BLUEPRINT

Why it matters and how it really works

The need

Public chains made paying people easy and made everyone's income readable. A freelancer paid in stablecoins can have her rates, her clients and her rent added up by anyone with an explorer. People who simply want normal financial privacy, the kind a bank statement gives them, have few easy options that do not depend on trusting a server.

What exists and what is new

Miden itself provides private accounts, private notes and client-side proving, and its own wallet and SDK already let developers create accounts and prove transactions in the browser. Other privacy systems such as Aztec and Zcash shielded wallets also exist. Private Vault is not a new privacy mechanic. What it adds is packaging: a plain, owner-branded app on Miden that makes the private choices the default, shows side by side what you see and what a stranger sees, asks before any delegated proving, and builds a weekly habit around collecting notes. It is a builder-status app for Miden first, and the value is in the experience, not novel cryptography.

The data it runs on

Account state, private notes and the memo live in the user's browser storage and an optional encrypted backup the user holds. The chain stores account state commitments, note commitments, nullifiers and the verified proof. Public notes, when the user chooses them, put the amount and accounts onchain. The app keeps no server copy of balances or recipients.

1.The mission

Make ordinary financial privacy the default for people paid onchain, proved on their own device, with nothing to trust but math they can check.

2.Why people can't resist it

The stranger's view Every payment shows two windows: your screen and what an explorer shows. Seeing 'amount hidden' next to your real payment is the moment people get it.

Six seconds, on your desk A visible proof dial in the browser tab turns a hard idea into something you watch happen locally, which builds trust fast.

The Sunday glass check A weekly two minute ritual: collect incoming private notes and see a score of how many payments a stranger could read. People keep the streak.

3.How it works for real

Miden client in the browser: The Miden web client SDK (WebAssembly) runs in the page: it creates the account, stores state locally and executes transactions in the Miden VM inside the tab.

Private accounts and notes: Accounts are created as private by default, so only a state commitment is onchain. Payments use private notes; public notes are an explicit opt-in per payment with a clear warning.

Client-side proving: STARK proofs are generated on the user's device. On low-memory phones the app splits work into smaller transactions. A delegated prover is optional, off by default, and always asks first because that server sees the inputs.

Note sync and collection: The client syncs commitments and nullifiers from a Miden node and finds notes addressed to the user, then consumes them so they become spendable. Optional note transport for private notes follows Miden's current tooling.

Encrypted backup: Local state can be exported as an encrypted file or saved to a backup the user controls, so a cleared browser does not mean lost notes.

Notifications: A small worker sends a weekly reminder by email or push with no payment details, only 'you have notes to collect'.

Hosting: A static Next.js app on Vercel or any static host. No backend database holds balances or recipients.

4.Cost per use and pricing

Proving runs on the user's device, so the owner pays no proving compute for local proofs. Network fees on Miden are small; check current testnet and mainnet fee terms before charging, as the network is young and terms can change. Hosting a static app costs about $0 to $20 a month. A delegated prover, if offered, is the main variable cost: a small cloud machine around $30 to $80 a month. Example month with 500 active users: hosting $20, notifications about $5, optional prover $50, so roughly $75.

Free $0

Private account, private payments, local proving, weekly glass check.

Pro $4 to $9 a month

Saved contacts, scheduled private payments, encrypted export for accountants, priority delegated proving with consent.

Team Setup fee plus monthly

Private treasury accounts for small teams and DAOs that pay contributors without publishing every salary.

5.Growth loop

Every private payment needs a recipient, and the recipient is invited to collect the note in their own vault. The share card ('0 of 31 payments readable by strangers') travels in freelancer and privacy groups. Being early in the first wave of Miden apps puts it on ecosystem lists when they go up.

6.Risks and guardrails

Legal and misuse: Privacy tools can be misused. Keep clear terms, never market it for evading law enforcement or sanctions, add basic screening where local rules require it, and check rules before charging.

Young network: Miden is early and its APIs, fees and network status will change. Budget time for upgrades and say plainly which network a payment is on.

Lost local state: If the browser is cleared without a backup, private notes can become hard to recover. The app nags for an encrypted backup before the first payment.

Delegated prover leakage: A delegated prover sees transaction inputs. It is off by default, asks every time, and is labelled on the receipt.

Weak devices: Old phones can run out of memory while proving. The app splits transactions and checks block age first, and says honestly when a device is too slow.

7.Build order

Create a private account in the browser with the Miden web client
Send and receive a private note between two test accounts
Add the side by side 'your screen vs stranger' view
Add encrypted export and a backup nag before the first send
Handle low-memory devices by splitting transactions
Add the weekly note collection reminder and glass check
Optional delegated prover behind an explicit consent step

8.Where this is going

Now
A clean private wallet on Miden for freelancers and early users, proving on their own devices.
Next
Scheduled private payments and invoices, so recurring work and rent run privately.
Later
Team treasuries and payroll where contributors are paid without publishing every salary.
The big one
Paying and being paid onchain feels as private as a normal bank account, with proofs instead of trust.

Costs and tools are estimates at the time of writing. General information only, not legal or financial advice.

OWNER PLAYBOOK

Own it, then chart your voyage

Nine routes from one vessel. Tap a port to open its chart.

Why own Private Vault

Most wallets send your activity to someone's server before it ever reaches the chain. Own Private Vault and you run a client side proving app on Miden from your own wallet and repo, which makes you one of the early verifiable builders on a young chain. The brand, the users and the onchain record of shipping are yours.

What’s stopping you?

“Miden is young. What if it changes?”

It will change. That is the deal with early chains: you get to be early, and you will need to update the app when the network upgrades. Watch the Miden release notes and budget an hour a month for updates.

“Will privacy get me in trouble?”

Private accounts are not the same as mixing stolen funds. Keep a clear terms page, do not market it for hiding from law enforcement, and check your local rules if you plan to charge.

“I can't code.”

You do not need to. Private Vault arrives working, deployed from your own wallet with a written guide for every step. You will click, paste and fill in names. If you ever want a change you cannot make, the custom option or a freelancer can handle it, but the first launch needs no code.

“Is it really mine?”

Yes. The contract is deployed from your wallet on Miden, the code sits in your own git repo, and the name and brand are yours. DEPLOYR does not hold your keys or take a cut of what Private Vault earns. If you stop paying anyone tomorrow, the app keeps running on your wallet.

“What if nobody uses Private Vault?”

That is the most likely early outcome, and it is fixable. The paths below start with you as the first user, then ten real privacy minded crypto users you can name today. If ten people you message do not care after you have shown it to them, you have learned something useful in a week instead of a year.

The million-dollar ladder

Free accounts with paid extras: a pro tier for power users (saved contacts, scheduled private payments, export), and a setup fee for teams and DAOs that want private treasury accounts. This ladder is a target, not a promise.

$40

$1,080

$17,100

$85,000

First 10 users

10 early pro users

$4 each

Proof it works

120 pro users

$9 each

Real business

900 pro users and small teams

$19 each

The million dollar run rate

2,500 pro users, teams and DAO treasuries

$34 each

Write one plain explainer of client side proving and pin it everywhere
Offer a team tier for DAOs that pay contributors privately
Show proving time and a 'nothing left your device' badge on every transaction
Ship in the first wave of Miden apps so you are listed when the ecosystem pages go up

Illustrative stages, not a forecast. Results depend on you and the market; nothing here is guaranteed.