# Demo narration

This is a replay of our completed two-wallet mainnet test, using the wallet's actual interface. Start with ZEN and a little Ether on Horizen, then open the private wallet.

Wallet A reviews privacy activation, then signs and submits. Check progress until it is confirmed. This registers the wallet's encryption key once, using the same address for public and private ZEN.

Wallet B completes the same activation before receiving a private payment. With private receiving active in both wallets, we can move on to the transfer.

Back in Wallet A, choose Shield and enter zero point one ZEN. First, review the approval and sign it. Approval gives the pilot permission to move that exact amount; the ZEN has not been shielded yet.

Now select Review shield, check the transaction, and sign. After confirmation, Wallet A has zero point one private ZEN. The shield deposit and its amount are public on chain.

Choose Send privately. Enter zero point one ZEN and Wallet B's address, then review and sign the payment. After confirmation, Wallet A's private balance is zero. The request is visible on chain, but the payment amount and recipient are encrypted.

In Wallet B, open the private wallet. The private balance is now zero point one ZEN, while the public ZEN balance is still zero. There is no separate private address to copy.

Select Unshield and enter zero point zero four ZEN. Review, sign, and check progress. Only that amount is released: zero point zero six stays private, and zero point zero four is ready to claim publicly.

Select Review claim and sign the claim transaction. Once confirmed, zero point zero four ZEN is in Wallet B's public balance. The remaining zero point zero six ZEN stays private.

That completes the flow in the existing wallet: shield, private send, partial unshield, and claim. This replay compresses the waiting time. The accompanying report contains the original mainnet transaction links and evidence.