TESTNET DEMO · VERIFIED RUN AVAILABLEPublic entry and exit remain visible · view privacy limits
AURA
AURA · ARCHITECTURE

How Privacy Works

The simple version: your main wallet funds a Private Balance, then AURA checks the payment before it leaves. The demo proves that middle step with a real private Zcash Testnet transaction. The public entry and payment can still be visible, so this is not a promise of perfect unlinkability or self-custody.

PUBLIC WALLETPRIVATE BALANCEPAYMENT
Normal Public Crypto

Direct Wallet Exposure

A direct payment exposes the wallet address you paid from, so a recipient can inspect the public balance and transaction history tied to that address.

Main WalletDirect TransferRecipient
Permanent link recorded on public block explorers.
Aura Private Balance

Decoupled Payment Flow

The recipient gets the payment; your main wallet is not the direct sender. Public timing and amount data may still make the route linkable.

Main WalletPrivate BalanceRecipient
The recipient gets the payment; your main wallet is not the direct sender.

What can the recipient see?

What the recipient sees in this testnet demo
No direct wallet handoff
Amount receivedThe recipient can see the amount paid
VISIBLE
Asset receivedSOL on Solana Devnet in this demo
VISIBLE
Destination walletThe recipient sees their own wallet address
VISIBLE
Your main wallet addressAURA does not send from your main wallet to the recipient
NOT DIRECTLY SHARED
Your total balanceNot shared as part of the payout
NOT DIRECTLY SHARED
Where the money came fromPublic entry, exit, timing, and amount can still create a link
MAY BE INFERRED
Your transaction historyNot handed to the recipient, but public-chain analysis may reveal patterns
MAY BE INFERRED
01 / Public EntryMay be visible

Your source address, deposit amount, timestamp, and route deposit address exist on the public entry chain.

02 / Private BalancePrivate balance + Zcash inventory

AURA presents a Private Balance between the public wallet and the payment. In this demo it is backed by a confirmed Zcash Testnet step; custody and privacy limits are explained below.

03 / Public ExitMay be visible

The recipient gets the payment. Your main wallet is not the direct sender, while the recipient-chain amount and time remain public.

What Can Still Correlate You

  • Immediate pass-through (depositing and exiting within seconds).
  • Identical transaction amounts (e.g. depositing $500 and paying exactly $500).
  • Reusing the exact same public address or payment link.
  • Network-level and IP metadata at provider boundaries.

What This Prototype Actually Does

  • Tracks the balance in AURA's records and checks it against the live Zcash Testnet inventory.
  • Optional 1-day and 3-day waits before a recorded balance can be spent.
  • Creates single-use Receive Requests with a fresh Zcash Testnet receiver.
  • Shows warnings about visible amounts and timing before supported payments.
  • These steps do not establish user custody or prove transaction unlinkability.
“AURA tracks the balance in its records and checks it against the live Zcash Testnet inventory. The testnet wallet is operated by the server; perfect unlinkability is not proven.”

Client Authorization & Demo Data Handling

Client authorization keys and intent signatures are generated locally in your browser. The current demo settles through a server-operated Zcash Testnet wallet; local authorization does not make this testnet flow self-custodial or guarantee zero tracking.