Add crypto
Bring USDC from Base Sepolia. Aura verifies the deposit before adding it to your Private Balance.
AURA · PRIVATE BALANCEPrivate mode for your crypto.
Private mode for your crypto.
Pay without exposing your main wallet.
Your wallet can reveal more than the payment. AURA puts a private balance between your main wallet and the people you pay — so they see the payment, not your financial history.
One private balance between your wallet and the people you pay.You use AURA. They don't have to. Prepare once; AURA checks timing and amount before you send.
YOUR WALLETPRIVATE BALANCEPAY ANYONE
Product promiseKeep your main wallet out of the direct payment path.
Current proof · testnetBase Sepolia → Zcash Testnet → Solana DevnetThe chains prove the route. The product is the Private Balance and the check that runs before a payment leaves.Demo custody: server-operated testnet · Production direction: user-controlled keys.
AURA
PRIVATE BALANCE
Private Balance$107.82
PAYMENT STATEREADY TO EXPLAIN
Public entryBase Sepolia
Private middleZcash Testnet
Public exitSolana Devnet
Ready to spend
$107.82Privacy policy · Ready under the active privacy policy
A private balance is not enough. AURA checks whether your timing and amount are about to reconnect the payment before you send.
THE PRODUCT IN ONE LINE
A private spending balance for crypto.
Move the crypto you want to spend into Private Balance. Then pay without using your main wallet as the direct source.
Your wallet stays your wallet. AURA does not replace it — it gives you a separate balance for private spending.
WITHOUT AURAYour Wallet → RecipientYour main wallet is the direct payment source.
WITH AURAYour Wallet → Private Balance → RecipientPay from the balance you prepared for private spending.
Why this matters · use case, privacy check, and honest limits
Keep your main wallet out of the payment.
You have $50,000 in your main wallet and need to pay someone $100. Why expose the wallet you paid from? Keep only your spending money in Private Balance and pay from there.
Stablecoins are becoming a real business payment rail, but onchain activity is still public by default. AURA turns the private middle into a product feature instead of making people manage cryptography themselves.
Private spending needs a check before it needs a button.
AURA combines payment-time warnings with a spending rule: timing, amount, and full-balance clues can be flagged before publication. Zcash is the private settlement layer underneath, and its confirmation rules become a plain-language check; the user never has to manage ZEC manually.
Track-specific value: someone who already uses a familiar USDC wallet should be able to reach a private working balance without learning Zcash operations. The demo shows the real Zcash step; live asset conversion is a production goal, not a claim of this testnet route.
Honest boundary: the MVP displays a ZEC-backed USD value, so it can move with the ZEC price. The production direction is a stable-value private spending path; this demo reduces simple clues but does not claim perfect unlinkability or operator-level privacy.
01 — What Can the Recipient See?
5-Second Comparison: Why You Need AURA
Your wallet should not become your public financial identity. AURA creates a simple path: Your Wallet → Private Balance → Recipient.
Normal Crypto Payment
Main WalletRecipient
A recipient can inspect the public balance and history tied to the wallet you paid from.
Anyone you pay can inspect the balance and transaction history tied to the wallet you used, including incoming and outgoing addresses.
Public-chain activity remains visible on the wallet you paid from.
AURA Private PaymentTESTNET ROUTE
Main WalletPrivate BalanceRecipient
The payment comes from Private Balance, not directly from your main wallet.
The recipient gets the payment. Your main wallet is not the direct sender, although public timing and amount data may still make the route linkable.
The demo keeps a Zcash-backed Private Balance between entry and exit. Timing and amounts may still link activity.
What can the recipient see?
What the recipient sees in this testnet demoAmount receivedThe recipient can see the amount paid
VISIBLEAsset receivedSOL on Solana Devnet in this demo
VISIBLEDestination walletThe recipient sees their own wallet address
VISIBLEYour main wallet addressAURA does not send from your main wallet to the recipient
NOT DIRECTLY SHAREDYour total balanceNot shared as part of the payout
NOT DIRECTLY SHAREDWhere the money came fromPublic entry, exit, timing, and amount can still create a link
MAY BE INFERREDYour transaction historyNot handed to the recipient, but public-chain analysis may reveal patterns
MAY BE INFERRED02 — How it worksAdd. Keep. Pay.
Add. Keep. Pay.
Three clear steps.
Aura turns a complicated cross-chain route into one simple balance. The current jury demo keeps the public entry and exit visible while the middle is backed by AURA's pre-funded Zcash Testnet inventory.
Keep it private
The balance is backed by a confirmed private Zcash Testnet step. Aura handles the technical work behind the interface.
Pay out
Send SOL on Solana Devnet. The recipient gets the payment, and every completed step shows its real testnet receipt.
Anyone who pays from a public wallet.Prepare a working balance once, then pay without making your main wallet the direct public payment source.
What's next — networks and product directionsCurrent route · expansion map
03 — Current route & what's next
Current testnet route. One route is enabled.
The current testnet route is scoped to Base Sepolia → Zcash Testnet → Solana Devnet. Other networks and product surfaces are clearly marked as coming next.
Current route & expansion map
● SUPPORTED ROUTE · TESTNET · EXPANSION NEXTPrivate BalanceSUPPORTED ROUTE
Base Sepolia deposit · AURA-operated private Zcash inventory
Business ControlsCOMING NEXT
Working-balance, approval, and selective audit/export controls for teams
The current core is Private Balance → Pay → Receive. Business controls and API are the only next-stage directions; they are not enabled in this demo.
Works now · scoped testnet routesPrivate Pay · AURA Request
Coming next · not enabled in this demo
Business ControlsTeam balances, approvals, and audit exports.
More NetworksExpand the same Private Balance flow beyond this testnet route.
API & CommerceMerchant checkout and programmable payment controls.
04 — How the demo is verified
Follow the real route.
The demo records every confirmed step. A visual animation is never presented as blockchain proof.
Public entryBase SepoliaUSDC deposit receipt
Private BalanceZcash TestnetPre-funded Zcash jury inventory
Public exitSolana DevnetFinalized payout signature
How AURA can become a businessBusiness logic · no invented pricing
The current demo proves the product loop. The business expands from the same Private Balance rather than from a new wallet or speculative token.
Market context, not AURA TAM: McKinsey/Artemis estimated actual stablecoin payments at approximately $390B in 2025, including approximately $226B in B2B payments. This frames the payment rail; it is not a claim about AURA market share.
Today · AURA service feePrivate Balance payments
Later · merchant, business, and API expansionAura Pay Checkout · working-balance tools · privacy payment infrastructure
These are monetization paths, not current revenue, user counts, percentages, or live pricing.
Technical details and privacy modelPolicies · architecture · FAQ
05 — Privacy Check settings
Choose how quickly your balance is ready to use.
A longer wait may reduce simple timing clues between adding and spending funds. Public transactions can still be correlated; no wait guarantees unlinkability.
FastestNo added wait
Fast
Use the balance after the required Zcash and recipient-network confirmations.
Extra waitNone
VaultZcash Shielded Pool
Timing cluesLess delay between actions
Recommended1-day buffer
1-day buffer
Wait 24 hours after the shielded deposit is confirmed. This may reduce simple timing clues, but does not guarantee unlinkability.
Policy1-day balance-age buffer
VaultAURA testnet route
Timing separationMay reduce simple timing clues
Longer wait3-day buffer
3-day buffer
Wait 72 hours after the shielded deposit is confirmed. This may reduce simple timing clues, but amount and public-chain data can still reveal links.
Policy3-day balance-age buffer
Privacy noteNo unlinkability guarantee
Timing LinkMay reduce simple timing clues
06 — Client-Authorized Keystore Architecture
Local Action Signing. Server-Operated Testnet Wallets.
Client-side signatures authorize actions, while this testnet demo uses server-operated relayers and a Zcash test wallet. This is not a self-custody guarantee.
01 / LOCAL KEYSTORE
Client Intent Signing
Your client authorization credentials and recovery phrase are generated locally in your browser. Every spend intent requires your explicit local cryptographic signature.
02 / ZCASH TESTNET
Shielded Zcash Inventory
The demo uses the matching ZEC amount from AURA's pre-funded Zcash Testnet inventory. AURA records the route; the private balance is read independently from the Zcash wallet.
03 / TESTNET ROUTE
Public Exit, Clear Boundary
This demo routes from Base Sepolia through the private Zcash Testnet step to Solana Devnet. Additional networks can be added later; the product promise is the Private Balance and the payment check.
07 — Frequently Asked Questions
Honest Privacy. Simply Explained.
What the current testnet demo does — and does not — protect.
When you fund the demo on Base Sepolia, AURA verifies the payment and uses its pre-funded Zcash Testnet jury inventory for the private step. The testnet keys are operated by AURA, and public entry and payout activity may still be linked using timing or other metadata.
Fund publicly.
Hold privately.
Send SOL on Solana Devnet.
AURA was built on the conviction that financial privacy is a fundamental human right. You shouldn't need a cryptography degree just to protect your personal net worth.
“AURA demonstrates a shielded testnet step between a deposit and a payout.”
AURA demonstrates a Base Sepolia to Solana Devnet test flow. Public deposits and payouts remain visible; the demo does not guarantee that they cannot be linked.