Sender
Your wallet
- Your everyday address is the onchain destination
- Your balance and full history are one lookup away
- Each payment links you to every other counterparty
Live on Stacks mainnet
Get paid without exposing your wallet.
Anyone can pay your normal Stacks address or .btc name. Privara settles the funds to a fresh one-time address that only you can find, so your everyday wallet never appears as the destination.
The problem
On a public chain, every payment points at your wallet.
Share one address to get paid and anyone can look up your balance, your history, and everyone you transact with. Privara keeps the address people know separate from the address that receives funds.
Sender
Fresh address
- The sender still types your normal address or .btc name
- Funds settle to a new one-time address for every payment
- Only your privacy keys can recognise and spend it
How it works
Three steps. No special address to share.
Senders use the address they already know. Recipients set up once and keep every incoming payment off their everyday wallet.
- 01
Create your privacy identity
Privara generates spending and viewing keys in your browser. You export an encrypted backup, prove it restores, and only then register the two public keys against your normal address.
Registration stays locked until the backup is restore-verified.
- 02
Get paid at your normal address
A sender enters your address or .btc name. Their browser derives a fresh one-time address from your public keys, they sign the exact payment, and a relayer settles it through the asset's router.
Every number on the review screen is the number that gets signed.
- 03
Scan, then spend
Your browser reads the router's encrypted announcements and recognises the payments meant for you. Pay someone directly from the one-time balance or withdraw to an address you choose.
Matching and key derivation happen locally — nothing private is uploaded.
See it in 78 seconds
From bob.btc to a fresh address.
Plays from YouTube when you press play. Open on YouTube
Features
Privacy that doesn't make payments harder.
Every safeguard is built into the normal flow, so the private path is also the easy one.
Pay any address or .btc name
Senders type what they already know. BNS names resolve to an exact address that is pinned for review — if ownership changes before signing, submission stops.
A fresh address for every payment
Each payment derives a new one-time Stacks address from the recipient's public keys, so incoming funds never land on the same address twice.
Discovery that stays on your device
Your browser scans public announcements and derives spending keys locally. The relayer and indexer never see your seed or keys.
Spend sBTC without holding STX
A sponsor pays the Stacks network fee and you approve one exact fee in the token you're moving. The quote is frozen before you sign.
You sign exactly what you review
SIP-018 intents bind the recipient, amount, fee, nonce, expiry, and router. Random unordered nonces mean a stuck payment never blocks the next.
Backups before receiving
You can't register until your encrypted recovery file restores successfully, and importing a different identity can never silently replace yours.
No deposit workflow
Privara checks your router balance and asks for one wallet approval covering only the exact shortfall — then continues the payment automatically.
Private payouts for teams
Pay DAO contributors in sBTC as individual private settlements, each to its own fresh address, from one reviewed batch.
Assets & fees
One privacy identity. Three assets.
Each asset settles through its own pinned router, and every one shares the same keys and scanner. Fees are shown exactly before you sign — senders choose to add the fee on top or include it in the amount.
₿
sBTC
Bitcoin on Stacks- Router
- Dedicated SIP-010 router
- Settlement fee
- 1% · paid by sender
- Spending
- Sponsored · 200 sats fee
- Network fee
- Paid by the sponsor in STX
Live · completed mainnet acceptance
$
USDCx
Dollars on Stacks- Router
- Dedicated SIP-010 router
- Settlement fee
- 1% · paid by sender
- Spending
- Sponsored · exact quoted fee
- Network fee
- Paid by the sponsor in STX
Live · small-value acceptance
S
STX
Native Stacks- Router
- Dedicated native-STX router
- Settlement fee
- 1% · paid by sender
- Spending
- Direct · no sponsor fee
- Network fee
- Self-paid in STX
Live · small-value acceptance
Privacy, stated precisely
We tell you exactly what's private — and what isn't.
Privara makes one specific guarantee and keeps it. Knowing the boundary is how you stay private in practice.
What Privara protects
- Your long-term wallet is never the onchain settlement destination
- Your privacy seed and private keys never leave your browser
- Every incoming payment lands at its own fresh address
- Approved intents and sponsor quotes can't be changed after you sign
What stays public onchain
- Payment amounts, the token, and timing
- The payer's activity and router interactions
- Relayer and network metadata
- Links created by later spending or withdrawals
For developers
Private payments, as a TypeScript SDK.
Add recipient privacy to your wallet, DAO tool, or payroll app. The SDK covers SIP-018 intents, stealth identities and recovery, local scanning, BNS resolution, native STX, and sponsored spending.
$ npm install @privara-stacks/sdkimport {
resolveMainnetRecipient,
generateIdentity,
} from "@privara-stacks/sdk";
// Resolve a .btc name to the exact address that gets pinned
const bob = await resolveMainnetRecipient("bob.btc");
bob.address; // "SP…"
// Create a privacy identity entirely client-side
const identity = generateIdentity();
identity.spendingPublicKey; // P — registered publicly
identity.viewingPublicKey; // V — registered publicly166automated tests
25test files
0.1.0stable SDK · MIT
5mainnet contracts
Verifiable on Stacks mainnet
Deployer on explorer- Stealth registryprivara-stealth-registry
- sBTC routerprivara-router-m2-sbtc
- USDCx routerprivara-router-m2-usdcx
- Native STX routerprivara-stx-router-v1
- Sponsored-spend helperprivara-sponsored-spend-v2
Does the recipient need to share a special address?
No. The sender enters the recipient's normal Stacks address or mainnet BNS name. Privara resolves it, reads their registered public privacy keys, and derives a fresh one-time destination automatically.
Is the payment amount private?
No. The amount, token, timing, settlement address, and transaction activity remain visible onchain. Privara protects the recipient's long-term wallet from appearing as the settlement destination.
Who controls the funds at a one-time address?
The recipient's independent Privara privacy seed derives its spending key. Leather, Xverse, or a hardware wallet does not control or recover those funds — keep your encrypted backup and its password safe and separate.
Do I need to deposit before paying someone?
There's no separate deposit step. Privara checks your router balance and asks for one wallet approval covering only the exact shortfall, waits for it to confirm, and continues.
Who pays the network fees?
The relayer pays for settlement. For sBTC and USDCx spends from a one-time address, Privara's sponsor pays the Stacks fee in STX and you approve a displayed fee in the token. A one-time STX address pays its own network fee with no sponsorship fee.
Can the sponsor change the fee after I approve it?
No. The approved quote is pinned into the transaction you sign. If the destination, amount, asset, fee recipient, sponsor, or fee changes, submission fails and you review a new quote.
Does scanning expose my keys?
No. The scanner reads public announcements; ownership checks and spending-key derivation happen locally in your browser. Private key material is never sent to the relayer or indexer.
Is Privara audited?
Not yet. Automated regression coverage, mainnet infrastructure, and small-value real-sBTC acceptance are complete, and an independent tester reproduced recovery, scanning, and sponsored withdrawal. An independent audit is recommended before larger-value use — start with small amounts.