The private account every wallet should have been.
A single account that holds private money. One balance. Many keys. No leakage of the graph between them. Every wallet on a public blockchain is a window — Lacuna is the room behind it.
Public blockchains were built for transparency, and transparency is their strength. It is also their largest unsolved cost. A wallet is not just a balance. It is a public dossier.
Every counterparty who has ever received from a wallet can see how much it holds, who else it paid, and which other wallets cluster with it. Salaries are visible. Treasury operations are visible. The shape of a household, a team, a fund, or a desk is visible to anyone with five minutes and a browser.
The standard defence is wallet hygiene — hold funds in a cold wallet, route through a sender wallet, never reuse addresses. This protects almost nothing. The moment a holder funds the sender on chain, an observer clusters them into one entity. The graph is rebuilt by the act of using it.
Privacy products today hide one transaction at a time. None of them give a user a private account.
Lacuna is a single account that holds private money. Any number of keys can be authorised to fund it. A controlled set of keys can spend from it. The owner can grant scoped, revocable visibility to anyone they choose. What enters, what sits, and what leaves are invisible to everyone outside the membership.
The relationships between the keys that fund the account and the recipients it pays are never published. The mental model is the Roman atrium — the inner courtyard where private affairs were conducted, with many doors leading in, one private interior, and visitors received at the threshold.
A single account with four properties no ordinary wallet has. Together they convert a public address into a private operating account.
Any number of keys can be authorised to deposit: hardware wallets, hot wallets, passkey wallets, a client paying an invoice, a payroll source. The balance is unified inside the account. The relationships between the depositing keys are never published.
An account only accepts deposits from keys the owner has explicitly approved. Random addresses cannot push funds in. Every dollar that enters can be tied to a key the owner chose — clean provenance, without a public ledger of who sent what.
Outbound payments leave the Lacuna account directly. They do not pass through any of the keys that funded it. A recipient sees an ordinary transfer arrive. They cannot see which key funded it, what the balance was, or anything else.
The owner can grant scoped viewing access to specific parties — an accountant, an auditor, a partner, a co-signer, an employee who sees only their own row of a payroll run. Each grant is independent, scoped to what is needed, and revocable in real time.
Holder wallets, a client paying an invoice, an employer paying salary, or anyone holding a deposit link issued by the owner can push funds into the account. Each deposit lands as part of a single private balance. The graph between depositors is not on chain.
The balance sits invisible to outside observers. Authorised members spend from it directly. Anyone, inside or outside the membership, can submit a payment request which an authority reviews and approves or rejects.
A spending key authorises a single outbound payment or a batch — payroll, vendor settlements, household disbursements. Each recipient gets an ordinary transfer at their normal address. They see what they were paid, and nothing else.
Anyone who currently runs a holder-to-sender wallet routine. The people most exposed to the graph problem. Lacuna replaces the routine. One account, many keys, no leaked network.
Operational treasuries that need to pay vendors, contributors, and grants without publishing the structure of the organisation. Payroll-style batch payouts and approval-gated requests in one account.
Capital that needs to settle on chain but cannot accept on-chain disclosure of positions, counterparties, or co-investors. Selective viewing keys satisfy auditors and partners without exposing the book.
Independent earners who receive from many clients and pay sub-contractors, who would prefer their gross income, client list, and payout schedule not be visible to every counterparty in the chain.
Public blockchains were never designed to be operating accounts. They were designed to be public. For payroll, savings, treasury, or any sum that matters, a window is the wrong shape.
Money requires a room.