Skip the trail of reused addresses and public balances. When you need to transfer value on Ethereum without linking a payment to someone’s primary wallet, Umbra provides a clear, repeatable flow. As a sender, you start with a recipient’s published viewing key, pick the asset and amount, and let an Umbra-enabled tool derive a fresh destination account that only the two of you can associate with the recipient. The tool wraps the derivation data in ciphertext and posts a small note to Umbra’s contract. On-chain, observers see a normal payment to a new account; off-chain, you retain a private record of what was sent. This works for Ether and standard tokens, so you can settle invoices, tips, or bounties without exposing counterparties.
For recipients, the routine is just as direct. Publish a viewing key once, then monitor for Umbra announcements with a wallet, script, or notification service. When a match appears, decrypt the note, reconstruct the spend key for that one-time account, and move funds where you want them—ideally to a long-term vault or hot wallet of your choosing. No ETH on the temporary account? Use a relayer: sign a meta-transaction that authorizes a withdrawal and pay the fee in the token you just received. You never have to pre-fund the stealth account with gas. Good hygiene: sweep promptly, tag withdrawals in your personal records, and keep viewing keys backed up separately from spending keys. more
Creators, freelancers, and teams can make Umbra part of everyday operations. Add a “private pay” button to a profile, share a viewing key on invoices, and let clients settle without exposing your main address to scraping or clustering. HR or DAO treasurers can run payrolls and grants through a simple batch: import a CSV of viewing keys and amounts, have a script derive unique destination accounts per recipient, send funds, and publish the encrypted notes. Employees or grantees withdraw at their convenience with token-funded fees. If you need to prove a payment later (for audit or support), share the relevant ciphertext and decryption data directly with the counterparty—no need to reveal everything publicly.
Developers can integrate quickly. Offer users a way to publish or import a viewing key; call an Umbra library to derive the destination account client-side; submit the asset transfer and the encrypted payload to the contract; and run an indexer or webhook to alert recipients when notes arrive. Provide a withdrawal helper that constructs meta-transactions so receivers can pay gas in the token they hold. Test on a public testnet, handle chain IDs, EIP-1559 fees, and reorg safety, and never persist raw spend keys server-side. For better privacy, rotate viewing keys per user group, jitter send times, and avoid correlating amounts across batches. With these patterns, you can add privacy-preserving payments to wallets, marketplaces, subscription services, or payout systems with minimal friction.
Comments