Umbra Confidential Payout

This route packages Umbra-style recipient privacy flow as Testnet product behavior: claim-link preparation, private settlement intents, private recipient boundaries, and proof continuity for operators, treasury teams, and judges.

Open govern Open execute Open curated docs

Route summary

Use PrivateDAO like infrastructure, not like a static brochure

This services route explains hosted reads, privacy policies, payout corridors, and the integration starter needed to plug the product into real organizations.

Use PrivateDAO like infrastructure, not like a static brochure

Execution boundaries

On this Umbra Testnet lane, relayer health and intent receipts are visible before any claim is treated as a completed private payout. The page keeps that boundary explicit for visitors and reviewers.

Live execution

A route actually prepares or submits a real runtime action on its current rail.

Health / status

A route checks vendor availability, relayer readiness, or runtime state without moving funds.

Intent receipt

A route records a review-safe intent or receipt so operators and judges can inspect continuity.

Full private settlement

A route reaches the actual payout rail and finishes the confidential transfer lifecycle.

Execution model

Prepare claim link, execute Testnet payout intent, verify receipt

The payout lane is structured for recipient privacy and operator clarity. Umbra is not isolated here; it serves the larger PrivateDAO system by handling the recipient-private disbursement edge inside confidential payroll, treasury payouts, grants, and controlled organizational distributions.

Build note: PrivateDAO development and hardening continue without interruption. This public route stays live while each integration is promoted from preparation, to Testnet receipt, to stronger on-chain execution proof.

Open execute lane Open MagicBlock lane Open judge lane Open proof lane

Umbra claim-link lane

Create a private claim link and execute the Testnet payout intent

This lane lets the visitor run the Umbra-style flow directly from the browser on the PrivateDAO Testnet operating surface. It prepares a claim link, forwards a recipient-private settlement intent to the read-node, records proof continuity, and leaves a live relayer health endpoint that the user can open immediately.

Network

Solana Testnet

User action

Build -> execute -> verify

Proof path

Read-node receipt + live relayer health

Asset

Amount

Recipient hint

Recipient wallet

Raw Solana address or .sol SNS name accepted.

Memo

Open proof Verify Testnet rail Open Testnet explorer

Delivery state

Build a claim link, then execute the claim settlement intent.

User-verifiable Testnet receipt

After execution, the receipt reports network: testnet, the settlement rail, execution reference, and relayer boundary. The project keeps building and hardening this rail continuously without interrupting the public Testnet route.

Boundary: this browser action proves the Umbra Testnet intent route and relayer readiness. Full Umbra claim settlement becomes explorer-linked only when the wallet supplies SDK proof account data, UTXO slot data, and a submitted claim transaction.

Execute the claim intent to display the latest Testnet receipt.

Claim link

No link generated yet.

Claim intent payload

{
  "rail": "umbra",
  "operationType": "payment-link-claim",
  "asset": "USDC",
  "amount": "25",
  "recipient": "B3STL1akxLGLvPpKd6Grz19jjVySkWrGgHFwGNK8yEZ",
  "memo": "Umbra claim payout rehearsal",
  "recipientHint": "contractor-01",
  "auditMode": "confidential-payout",
  "recipientVisibility": "recipient-private",
  "createdAt": "2026-06-11T02:23:24.642Z"
}

Umbra SDK runtime

Umbra relayer boundary, SDK contract, and claim lifecycle are exposed for review

The live lane reaches Umbra's public relayer endpoint through the PrivateDAO read-node and keeps the exact claim boundary visible: browser clients still need wallet signing, SDK-generated proof account data, UTXO slot data, and relayer polling before a real claim is submitted. The upstream hostname is preserved as evidence; the PrivateDAO operating surface remains routed through the Testnet read-node.

Open Umbra boundary probe Read relayer info Check relayer health

Verified public fields

Relayer: https://relayer.api-devnet.umbraprivacy.com
Supported mints: So11111111111111111111111111111111111111112
DXQwBNGgyQ2BzGWxEriJPVmXYFQBsQbXvfvfSNTaJkL6
4oG4sjmopf5MzvTHLE8rpVJ2uyczxfsw2K84SUTpNDx7

Claim lifecycle

receivedvalidatingoffsets_reservedbuilding_txtx_builtsubmittingsubmittedawaiting_callbackcallback_receivedfinalizingcompleted

Operating map

Where Umbra fits inside the full product

Umbra covers the recipient-private payout edge. Governance and intelligence decide when a payout should happen, treasury selects the funding route, Encrypt / IKA protects sensitive payroll preparation, MagicBlock can handle fast private execution loops, and Umbra preserves recipient privacy at the disbursement step.

Coordination core

DAO creation, proposal preparation, commit/reveal voting, wallet authorization, PDAO governance-token context, and immediate Testnet proof.

Encryption payment lane

Cloak, Umbra, MagicBlock, and stablecoin billing stay grouped as one private money-movement corridor instead of scattered payment pages.

Confidential operations

Encrypt, Ika, REFHE, and 2PC-MPC preparation keep payroll instructions private while preserving receipt and proof continuity.

Treasury rails

Jupiter route preview, PUSD/AUDD activation paths, policy checks, and wallet signatures connect treasury planning to Testnet execution.

GamingDAO and community rewards

Tournament, community, and competition reward operations use the same governance, private payout, and proof rails.

Intelligence before authorization

QVAC, GoldRush/Covalent, SNS, Zerion, QuickNode, and policy context explain risk before a normal user or agent approves.

How intelligence feeds every lane

Governance receives proposal review, risk framing, and policy context before a signer approves.

Payments receive counterparty review, settlement lane selection, and private rail clarity before funds move.

Payroll receives encrypted operational preparation so payout metadata stays out of shared review surfaces.

Treasury receives wallet history, stablecoin visibility, and route comparison before rebalance or disbursement.

Wallet-first flows receive simpler user context so normal operators can act safely without losing technical truth.

Open intelligence core Start governance Open proof continuity

Confidential payments system

Encrypted payment coordination built as product infrastructure

This lane is not a trading flow. It is operational infrastructure for confidential payroll, encrypted treasury coordination, secure payout routing, and AI-assisted pre-sign controls, with each rail connected to review and proof surfaces on Solana Testnet.

Cloak private settlement rail

Shielded treasury and payroll settlement path for confidential value movement with review-safe proof handoff.

Umbra confidential payout rail

Recipient-private payout lane for high-sensitivity disbursements and selective disclosure boundaries.

MagicBlock private payments rail

High-frequency execution path for private payment intent, commit continuity, and low-latency operation loops.

Encrypt / IKA + REFHE envelope

Client-side payload encryption and confidential execution commitments before any shared route receives metadata.

REFHE payroll proof

Encrypted payroll packet, computation commitment, and Ika custody readiness for confidential salary operations.

Intelligence layer

QVAC sovereign decision layer

Local-first AI review for sensitive payroll and treasury flows before a signer approves execution.

SolRouter encrypted analysis

Encrypted operational reasoning for non-sensitive policy summaries and route pre-checks.

Covalent GoldRush intelligence

Counterparty, treasury, and wallet context to reduce operational blind spots before confidential settlement.

Open full encrypted payments section Open proof continuity Open judge verification path

Private settlement rail workbench

Prepare and forward rail-specific private settlement intents

This workbench turns private settlement into a real operator action surface. It prepares a Cloak or Umbra execution intent, forwards it through a rail-specific proxy when available, and records the resulting receipt path.

Settlement rail

Umbra confidential payout lane

Use Umbra posture when recipient privacy, claim-style flows, and public-facing confidential payout UX are the main product requirement.

Operation type

Asset

Amount

Recipient

Raw Solana address or .sol SNS name accepted.

Operator memo

Open proof route Open packet

Delivery state

Prepare a private settlement intent, forward it through the read-node rail endpoint, and store the receipt.

Prepared intent

{
  "rail": "umbra",
  "operationType": "private-payroll",
  "asset": "USDC",
  "amount": "250",
  "recipient": "B3STL1akxLGLvPpKd6Grz19jjVySkWrGgHFwGNK8yEZ",
  "memo": "Payroll tranche / reviewer-safe memo",
  "auditMode": "confidential-payout",
  "recipientVisibility": "recipient-private",
  "createdAt": "2026-06-11T02:23:24.665Z"
}

Latest response preview

The rail receipt will appear here after the operator forwards the prepared intent.