Product navigation
This route packages the full confidential payment stack as an operational product surface: encrypted planning, private payout rails, intelligence-assisted risk review, and proof-linked execution continuity.
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.
This section combines multiple rails. Some cards execute live flows, others expose health or receipt continuity. The boundaries stay explicit so visitors know what has already moved on-chain and what is still a review or readiness step.
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.
Shielded treasury and payroll settlement path for confidential value movement with review-safe proof handoff.
Recipient-private payout lane for high-sensitivity disbursements and selective disclosure boundaries.
High-frequency execution path for private payment intent, commit continuity, and low-latency operation loops.
Client-side payload encryption and confidential execution commitments before any shared route receives metadata.
Encrypted payroll packet, computation commitment, and Ika custody readiness for confidential salary operations.
UserShareEncryptionKeys activation rules
`UserShareEncryptionKeys` must be created before dWallet creation, and the selected curve must match the dWallet signature path. Any mismatch breaks authorization and decryption flows.
- 1. Generate root seed securely, then derive `UserShareEncryptionKeys` with matching curve.
- 2. Register encryption key and keep serialized key bytes in secure storage only.
- 3. For dWallet activation: sign user public output and verify state before submit.
- 4. For decrypt flow: verify active dWallet state, validate share signature, then decrypt and verify output consistency.
Private Payments API is wired with the correct auth boundary
PrivateDAO now exposes MagicBlock health and challenge initiation through the read-node while preserving the required wallet-signed login step. Private balance reads are not fetched anonymously because MagicBlock requires the challenge/login bearer token for private state.
UTXO-first devnet lane, verified without exposing secrets
This route now distinguishes the hosted PrivateDAO intent receipt from the official Cloak devnet SDK surface. Reviewers can see the exact SDK package, program, relay, and probe command used for live validation.
The live probe records only public program IDs, public relay status, and public transaction or receipt references. It does not print private keys, viewing keys, UTXO private keys, raw notes, or seed material.
Devnet relayer, SDK contract, and claim lifecycle are exposed for review
The live lane checks the Umbra devnet relayer 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.
- Relayer
- https://relayer.api-devnet.umbraprivacy.com
- Supported mints
- So11111111111111111111111111111111111111112DXQwBNGgyQ2BzGWxEriJPVmXYFQBsQbXvfvfSNTaJkL64oG4sjmopf5MzvTHLE8rpVJ2uyczxfsw2K84SUTpNDx7
- 1. Prepare confidential policy and payroll intent through local-first intelligence.
- 2. Encrypt sensitive payloads client-side with Encrypt / IKA envelope before execution lanes.
- 3. Route settlement through Cloak/Umbra/MagicBlock rails based on confidentiality and speed requirements.
- 4. Publish commitment-safe receipts to proof and judge surfaces for verifiable operational continuity.
For payment-lane planning, IKA economics matters at runtime: operation pricing, validator incentives, and governance adjustments can affect dWallet lifecycle costs (generation, presign, signing, resharing). This route keeps those economics visible to treasury operators before finalizing confidential execution policies.