Encrypted manifest
Wallet-signed Testnet
Proof-linked
Payroll
Run confidential payroll and reward rehearsals from the browser

Prepare a private payroll manifest, sign a Testnet payout rehearsal from the visitor wallet, and keep proof continuity attached. This route is built for a normal operator: recipient, amount, memo, encrypt, sign, verify.

ConnectReviewSignVerify
Wallet-orchestrated UXReview first · Sign second · Verify third
Connect
Choose wallet, confirm account, and stay on Solana Testnet.
Review
Read the action, policy, risk, privacy mode, and execution lane first.
Sign
Approve the exact wallet request only after the operation is clear.
Verify
Open the receipt, explorer hash, and proof continuity from the same flow.
Review routeVerify route
Payroll privacy starts with local encryption; payment proof lands through the wallet-signed Testnet rehearsal and settlement receipt lanes.
Visitor fast pathClick → Sign → Verify
Operator sequence

Encrypt → Sign payout rehearsal → Forward private intent → Verify

Payroll is sensitive because names, amounts, bonuses, and internal reasons should not be public by default. PrivateDAO keeps the sensitive manifest encrypted in the browser, then connects it to a wallet-signed Testnet transaction and receipt path. Stablecoin rails upgrade to SPL TransferChecked where mint configuration exists; SOL fallback remains available so every visitor can test the flow immediately.

Operating map

Payroll is one execution lane inside the PrivateDAO Stack

Governance approves the payroll policy, intelligence reviews the risk and continuity, encryption protects the sensitive manifest, the wallet signs the Testnet operation, and proof keeps the resulting receipt inspectable.

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.
End-to-end Testnet claim matrixPain → Treatment → Proof

Every integration has a job in the operating flow

Organizations need privacy because payroll, votes, vendors, treasury routes, and internal operations leak by default. Blockchains need verifiability because trust collapses when execution cannot be checked. PrivateDAO connects both: private preparation, wallet-controlled Testnet execution, and public-safe proof.

Live matrix anchor
Waiting for live matrix anchor
loading
digest: loading
slot: pending
Governance + ZK
Testnet path
Pain

Strategic votes become public before the organization is ready.

PrivateDAO treatment

Commit/reveal governance, local Groth16 proof artifacts, and standalone Testnet verifier receipts turn private voting into a verifiable workflow.

Proof action

Create DAO, create proposal, commit, reveal, finalize, execute, then open Solscan and proof.

ZK Commit/Reveal
Testnet path
Pain

Private votes lose credibility if the proof path is hidden from normal reviewers.

PrivateDAO treatment

The governance rail binds commit, reveal, Groth16 proof context, and a visitor-signed Testnet digest claim into one verifiable path.

Proof action

Open Govern, run the governance flow, anchor the ZK commit/reveal claim, then inspect readiness and Explorer links.

REFHE / Encrypt Payroll
Testnet path
Pain

Salary rows, bonus reasons, and payroll strategy leak when teams operate from public wallets and spreadsheets.

PrivateDAO treatment

Encrypted payroll manifests, REFHE envelope settlement, and wallet-signed payout rehearsal bind private payroll context to public-safe proof.

Proof action

Encrypt payroll payload, anchor a confidential-payroll claim, run payout rehearsal, export proof.

REFHE Payroll Computation
Testnet path
Pain

Payroll privacy is not enough unless encrypted computation receipts and payout evidence stay connected.

PrivateDAO treatment

REFHE payroll proof produces ciphertext-safe receipts, then the visitor anchors a digest claim on Solana Testnet.

Proof action

Open REFHE payroll proof, generate the receipt, anchor the REFHE claim, export public attestation.

Encrypt Manifest
Testnet path
Pain

Sensitive operational plans should be encrypted before they enter review, automation, or payment rails.

PrivateDAO treatment

Browser AES-GCM encryption creates a local encrypted packet, hashes ciphertext, and signs only the digest on Testnet.

Proof action

Open Services, pick Encrypt Manifest, anchor a claim, verify locally, export public attestation.

MagicBlock Private Payments
Testnet path
Pain

Reward and payout corridors expose timing, recipients, and operational intent.

PrivateDAO treatment

MagicBlock corridor receipts and visitor-signed encrypted claims make private payments testable while preserving a visible execution trail.

Proof action

Open the private payments service, anchor a claim, and inspect corridor evidence.

MagicBlock Claim
Testnet path
Pain

Private payment UX needs a single route from payment corridor to explorer-visible proof.

PrivateDAO treatment

MagicBlock corridor evidence, health checks, and visitor-signed encrypted payment claims become one Testnet-verifiable lane.

Proof action

Open MagicBlock, inspect on-chain proof, anchor the MagicBlock claim, verify the digest transaction.

Umbra / Cloak Settlement
Testnet path
Pain

Vendor and contributor payments reveal counterparties before the organization wants disclosure.

PrivateDAO treatment

Recipient-private settlement intent, rail health, and selective-disclosure receipts keep the operation private but reviewable.

Proof action

Prepare settlement intent, forward through the rail, anchor the encrypted claim, verify receipt.

Ika / 2PC-MPC Custody
Testnet path
Pain

Treasury operations need stronger signing control than a single hot-wallet action.

PrivateDAO treatment

Ika readiness, Solana pre-alpha final approval, and custody preparation expose the threshold-signing path as an execution rail.

Proof action

Open Encrypt/Ika operations, inspect readiness, prepare custody, anchor an Ika claim.

Ika 2PC-MPC Approval
Testnet path
Pain

Treasury custody claims are weak unless the approval, readiness, and signing boundary are inspectable.

PrivateDAO treatment

Ika readiness, Solana pre-alpha final approval, custody preparation, and a visitor Testnet claim form one reviewable path.

Proof action

Open Encrypt/Ika operations, inspect final approval, prepare custody, anchor the Ika 2PC-MPC claim.

Jupiter + Torque Treasury
Testnet path
Pain

Treasury moves lose context when routing, approval, and growth/accounting events live in separate tools.

PrivateDAO treatment

Jupiter route review and Torque event delivery connect treasury execution with operational telemetry.

Proof action

Preview the route, run the claim or event lane, then inspect provider status.

Torque MCP Growth Loop
Testnet path
Pain

Growth rewards become untrustworthy when product activity, treasury policy, and event delivery are split.

PrivateDAO treatment

Torque MCP/event delivery is tied to governed treasury context and an on-chain digest claim for reviewer-visible proof.

Proof action

Open Torque, inspect provider status, trigger/prepare event delivery, anchor the Torque MCP claim.

Palm USD Utility Layer
Testnet path
Pain

Stablecoin payroll, grants, and rewards usually expose operational context or sit outside governance proof.

PrivateDAO treatment

PUSD becomes a governed settlement rail: prepare private payroll/grant/reward context, encrypt the claim, sign from wallet, and verify public-safe evidence.

Proof action

Open the PUSD route, anchor the PUSD utility claim, inspect the utility API, then verify the matrix anchor.

QVAC + GoldRush Intelligence
Testnet path
Pain

Signers approve proposals without enough risk, history, counterparty, or treasury context.

PrivateDAO treatment

QVAC local reasoning plus GoldRush/Covalent, Zerion, QuickNode, and provider status create the pre-sign intelligence gate.

Proof action

Open Intelligence, review Operational Gravity, then continue to Execute.

Private encryption workbench

Client-side encrypted payroll/vendor payload

This step runs encryption in-browser before execution. Only encrypted payload + commitment moves forward to receipts and audit flow; the payment proof is produced by the wallet-signed Testnet rehearsal below.

Prepare a payroll/vendor payload, encrypt locally, then run the wallet-signed payment rehearsal below.
On-chain claim console

Anchor any privacy rail as a visitor-signed Testnet claim

This console makes every privacy and encryption lane end-to-end testable from the browser. The visitor selects the rail, encrypts the claim locally, signs a Solana Testnet commitment transaction, then verifies the signature on-chain. Stronger rails still keep their native REFHE, MagicBlock, Ika, Umbra, Jupiter, and Torque proof paths beside this universal claim layer.

Repeatable means every visitor can run a fresh live attempt. Each click creates a new AES-GCM encrypted claim packet and a new wallet-signed Testnet commitment from that visitor wallet, not a replay of an old project signature.

Step 1
Encrypt locally
Step 2
Anchor digest
Step 3
Verify receipt
Private governance

Commit/reveal governance with ZK companion proof path.

claim: visitor-wallet-memo-attestation
native: wallet-signed-onchain
Open service
Connect a Testnet wallet, pick a privacy rail, and anchor the claim on-chain.
Selective disclosure receipt
After anchoring, verify the encrypted packet locally, export a public attestation without the AES key, or export a private disclosure receipt for an allowed reviewer.
Testnet billing rehearsal

Charge a small Testnet fee from the same wallet-first product, then inspect the proof on-chain

This is the current truthful commercial lane. Every visitor can run the flow immediately with a wallet-signed transaction on Testnet. When official stablecoin mint rails are configured, the lane executes as SPL TransferChecked; otherwise the same lane executes as a memo-coded SOL rehearsal so the service stays testable end-to-end.

Current boundary
The live rehearsal always stays executable for visitors: SOL fallback is active by default and stablecoin rails upgrade in-place to SPL TransferChecked as soon as official mint configuration is set.
Execution panel
Run the charge and inspect the result
Wallet: Not connected
Visitor address: Connect a Testnet wallet to continue.
Treasury receive address: AZUroiNeGAjNdD84eEHnAKHHFwqAFmkjr2g1eoF7Ek5c
Current SKU: Wallet-first onboarding lane · 0.003 SOL
Asset rail: SOL
Execution mode: SOL transfer fallback
Network: Solana Testnet
Choose a billing lane, connect a Testnet wallet, then send the rehearsal charge.
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
Cloak private treasury lane
Use Cloak posture when payroll, vendor settlement, or treasury motion needs selective disclosure and a tighter private execution story.
Open proof routeOpen packet
Delivery state
Prepare a private settlement intent, forward it through the read-node rail endpoint, and store the receipt.
Prepared intent
{
  "rail": "cloak",
  "operationType": "private-payroll",
  "asset": "USDC",
  "amount": "250",
  "recipient": "B3STL1akxLGLvPpKd6Grz19jjVySkWrGgHFwGNK8yEZ",
  "memo": "Payroll tranche / reviewer-safe memo",
  "auditMode": "selective-disclosure",
  "recipientVisibility": "private-by-default",
  "createdAt": "2026-05-30T16:58:49.203Z"
}
Latest response preview
The rail receipt will appear here after the operator forwards the prepared intent.