SIMULATEDSimulated Starknet

Privacy

SIMULATED

Hold and move hstXDC confidentially

STRK20 encrypts movement inside the pool. Sender, receiver, amount and token are hidden for every in-pool transfer — and the edges, where value enters and leaves, stay public. Both halves of that sentence matter.

Private actions

Running against the local simulation.

Switch to Live and connect an STRK20-capable wallet to submit for real. Nothing here touches key material — the wallet holds the viewing key, discovers notes, and generates the proof.

SIMULATED

Public balance

Visible on chain

120,000.00

hstXDC in your wallet

Shielded balance

Encrypted

0.00

0 notes · 0.00 spendable

Shield early, transact later

Shielding and transferring in close succession can link you to your public activity — an observer who sees a deposit and then a pool transaction of similar size moments later can reasonably connect them. Distinctive amounts weaken the anonymity set for the same reason. Shield when you have no immediate need to move, and the crowd you hide in grows on its own.

Private transfer

Institution to institution, with no public leg at all. Nothing about this appears on the explorer.

Private stake

Stake from your shielded balance through the Helix anonymizer. Observers see the pool call a helper, and the helper call the vault. They do not see who initiated it.

Simulate builds and proves the transaction without submitting it — the cheapest way to catch a calldata-shape error before it costs a fee.

The same transfer, seen two ways

What the chain shows

What you and your auditor see

Counterparty
0x0496…f38e
Amount
40,000.00 hstXDC
Token
hstXDC
Notes spent
note-3, note-7
Timing
14:22:07 UTC
14:22:07 UTC
Pool interaction
Yes — someone transacted
Yes

Shielding and unshielding are the exceptions: those legs are fully public — address, token and amount — because value is crossing the pool boundary. Inside the pool, only timing and the fact that someone transacted are visible.

Why this is not a mixer

SIMULATED

Escrowed viewing keys

At registration your viewing key is encrypted to a designated auditor's public key and stored on chain. A lawful request unwraps one user's history — not everyone's. There is no bulk-surveillance mode.

Viewing is not spending

A viewing key reads history. It cannot move funds. The scheme also supports threshold auditor keys, so disclosure need not rest with a single party.

Screening at the point of entry

Every deposit is screened and signed before it enters the pool, and the contract verifies that signature on chain. It is protocol-level and applies on every route — this is the property a mixer cannot offer.