OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Payments & Stablecoins

Umbra

Umbra is a privacy-preserving stealth-payment protocol for Ethereum and other EVM blockchain networks. It lets a payer send funds to a fresh address controlled by the intended recipient without sending directly to the recipient’s publicly associated address. The sender and recipient can identify the payment relationship, while outside observers inspecting the receiving address cannot determine it from that address al

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Umbra — OpenViST project profile in Payments & Stablecoins.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Umbra when a payment should avoid directly linking the recipient to the receiving address on-chain, such as contractor payments, donations, or EVM checkout. The recipient should plan withdrawals carefully because moving funds to a publicly identified address can weaken the privacy benefit.

Who it is for

  • EVM developers building privacy-preserving payment interfaces
  • Organizations considering private payroll or contractor-payment flows
  • Donation platforms that want each contribution sent to a separate recipient address
  • Merchants designing EVM checkout flows with fresh recipient addresses

Documented uses

  • Generate fresh recipient addresses for private payments
  • Receive funds through an address or ENS name without exposing the recipient’s usual receiving address
  • Scan Umbra Announcement events to identify incoming payments
  • Withdraw received funds to another address directly or through a relayer-based meta-transaction
Before you choose

Requirements & limits

The cited repository is public, active, and MIT-licensed. It is a TypeScript project with an application homepage at app.umbra.cash.

  • Umbra supports Ethereum and EVM networks through stealth addresses and smart contracts.
  • Recipient setup uses a signed message to derive spending and viewing keys.
  • Payers can use a recipient address or ENS name to look up the published public keys.
  • The privacy model is limited: Umbra does not provide full privacy like Aztec or Zcash and is not a mixer.
  • Withdrawal behavior matters; sending funds to an identity-linked address can expose the relationship.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Set up an Umbra recipient account

Prepare a recipient to receive private Umbra payments through an address or ENS name.

Before you start

  • An Ethereum or EVM-compatible wallet capable of signing a message.
  • An address or ENS name to associate with the Umbra account.
  • Access to the Umbra application or protocol implementation.

Steps

  1. Sign the setup message to generate spending and viewing keys.

  2. Publish the corresponding public keys on-chain as records associated with the recipient address.

  3. Give the payer the recipient address or ENS name so the payer can look up the public keys.

Expected outcome

The recipient has published the key material needed for a payer to generate a stealth payment address.

Guide limitations

  • This guide covers account setup only, not a completed payment or withdrawal.
  • The protocol’s privacy benefits can be reduced by poor withdrawal hygiene or publicly identifying the recipient.
Documentation 1 ↗Documentation 2 ↗
Evidence and transparency

Sources & review

Official repository ↗Guide documentation ↗
Source record details
Source availability
Active
Sources checked
2 October 2026
Original website title
ScopeLift/umbra-protocol · Official homepage title · retained in its source language
How we review sourcesSuggest a correction