Umbra Confidential Payout

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

Open govern Open execute Open curated docs Founder Whiteprint

Phase 2 after judging

Encrypted customer delivery

Auditor-gated source

Mainnet review path

Post-judging roadmap

Phase 2 turns every service request into an encrypted delivery lane

After the active judging window, PrivateDAO will move the commercial service flow into a fully encrypted client lane: intake, package selection, provider routing, on-chain payment reference, time-limited access, delivery, renewal, and upgrade decisions will be bound to the customer's selected privacy and intelligence requirements.

The defensive license layer is designed to revoke access, erase locally sealed service material, and stop execution when tampering is detected. It is not designed to damage user devices or third-party systems.

After Phase 2, the roadmap moves into Mainnet deployment preparation and external security review. Phase 3 opens the same protected infrastructure cross-chain so sensitive institutions can use broader blockchain rails while Solana remains the guardian chain, first proof home, and decision layer that anchors the system.

Encrypted intake from the first form field through service delivery.

Time-bound license keys issued from on-chain payment and service terms.

Client-selected intelligence rails across QVAC local models, GoldRush, Dune SIM, Zerion, SNS, and Covalent-style recovery prompts.

Auditor-visible security review before sensitive source, policy matrices, and partner-only integration bundles are closed.

Mainnet deployment begins after the current judging phase and the required external security reviews.

Phase 3 expands the infrastructure cross-chain while Solana remains the guardian chain and first governance home.

Payment-bound access

The payment transaction hash can become the customer's activation reference after settlement confirmation.

Intelligence routing

QVAC handles local emergency and private briefs; external rails add wallet, market, identity, and simulation context.

Security review boundary

Sensitive source, policy matrices, and anti-tamper logic move behind auditor and partner review after the public judging phase.

Start encrypted intake Review QVAC lane Open proof

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 model

Prepare claim link, execute private payout, verify receipt

The payout lane is structured for recipient privacy and operator clarity. The same route exposes settlement preparation, claim-oriented flow, and direct reviewer paths into judge and proof.

Open execute lane Open judge lane Open proof lane

Umbra claim-link lane

Create a private claim link and execute the payout intent

This lane models Umbra-style claim payouts for recipients who should not expose destination details publicly. It prepares a claim link, forwards a claim settlement intent, and records proof continuity.

Asset

Amount

Recipient hint

Recipient wallet

Memo

Open proof

Delivery state

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

Claim link

No link generated yet.

Claim intent payload

{
  "rail": "umbra",
  "operationType": "payment-link-claim",
  "asset": "USDC",
  "amount": "25",
  "recipient": "RecipientWalletxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "memo": "Umbra claim payout rehearsal",
  "recipientHint": "contractor-01",
  "auditMode": "confidential-payout",
  "recipientVisibility": "recipient-private",
  "createdAt": "2026-05-13T18:38:11.505Z"
}

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

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": "RecipientWalletxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "memo": "Payroll tranche / reviewer-safe memo",
  "auditMode": "confidential-payout",
  "recipientVisibility": "recipient-private",
  "createdAt": "2026-05-13T18:38:11.506Z"
}

Latest response preview

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