FAQ
Short answers to the questions people ask most about confidential tokens.
Short answers to the questions people ask most about confidential tokens.
Is my balance really hidden?
Yes — on-chain it exists only as an encrypted euint64 handle. Validators, indexers, and explorers see ciphertext, not a number. Only you, after signing a permit, can decrypt it. What stays public is the interaction graph: that your address touched a wrapper, and when.
Does decrypting cost gas?
No. Decryption uses an off-chain EIP-712 signature. There is no transaction and no gas — you're just proving to the Gateway that the ciphertext is yours.
Why is the wrapper always 6 decimals?
FHE works on 64-bit integers (euint64), which would overflow with 18-decimal amounts. Wrappers standardize on 6 decimals and scale automatically. See Decimal Scaling for the exact shield/unshield rule.
What happens if I close the tab mid-unshield?
Nothing is lost. The unwrap request is on-chain and the pending tx hash is saved locally. Next visit, ShadowLine detects it and offers a Resume action to finalize. See Shield & Unshield.
Can I use this without the ShadowLine site?
Yes. It's non-custodial and open-source — every operation maps to public contract calls. The REST API and the documented SDK hooks let you build your own interface against the same registry.
Where do the testnet tokens come from?
Sepolia registry pairs are Zama-deployed mock tokens with a public mint(). Grab free ones from the Faucet page, then shield them to try the full flow.
A wrapper approval is failing in my wallet — why?
Likely a USDT-style token that rejects changing a non-zero allowance directly to another non-zero value. Zero the allowance first, then approve the real amount. ShadowLine does this automatically; details are on Shield & Unshield.
