Product navigation
This is the canonical Encrypt / Ika route: a visitor can run browser encryption, REFHE payroll proof receipts, Ika readiness reads, 2PC-MPC approval preparation, Ika custody preparation, and proof-linked confidential operation flows without a terminal.
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.
Services should show the business model, the operating lane, and the live Testnet proof in one commercial surface
This route works best when pricing, billing rehearsal, treasury routing, trust packets, and hosted-read packaging are kept together instead of being split across static documents.
REFHE, MagicBlock, and Ika are tracked as protocol-native rails
The live read-node now exposes one spine for the Frontier privacy stack: REFHE finalized Testnet receipts, MagicBlock private corridor receipts, Ika Solana final approval, Ika SDK and pre-alpha custody readiness, and the visitor-repeatable Solana Memo claim that every reviewer can create fresh from their own wallet. Building and development continue without interruption while each rail moves toward deeper native execution.
This route separates what is runnable today from the final production gates: REFHE and client encryption execute now; Ika has a real Solana pre-alpha final approval signature plus readiness, approval-preparation, and custody-preparation lanes while Ika-network dWallet DKG remains separately recorded when available.
Four concrete execution rails, one truth boundary
REFHE, browser encryption, and receipt generation are runnable from the page. Ika/2PC-MPC now includes a real Solana pre-alpha final approval signature, plus readiness, approval-preparation, and custody-preparation rails: executable program and funded operator checks are visible, while Ika-network dWallet DKG remains a separately recorded receipt class.
REFHE payroll proof
Runnable nowEncrypt a payroll payload in the browser, submit commitment-safe proof data, and receive a backend receipt hash.
Ika / 2PC-MPC custody preparation
Solana final approval signedOpen the Ika Solana final approval signature, then read the Ika SDK network route, executable pre-alpha program, funded operator boundary, and custody-preparation route.
Browser encrypted manifest
Runnable nowCreate an AES-GCM encrypted operation manifest locally before anything enters a shared review or execution lane.
One-click Testnet truth board
Runnable nowRun browser encryption, REFHE receipt, Ika Sui read, Ika Solana read, approval preparation, and custody preparation from one page.
Encrypt / Ika / 2PC-MPC / REFHE execution truth board
This route lets a visitor run the encrypted payroll proof path directly: browser encryption, REFHE receipt generation, Ika SDK network read, Solana pre-alpha program read, governed approval-route preparation, and Ika custody route preparation. The counters below are stored by the backend so attempts from different devices increase the same public totals.
Run an encrypted proof action to see live output.
How encrypted operations feed the rest of the product
Encrypt / IKA is the privacy preparation layer. It protects payroll instructions, sensitive treasury operations, and confidential governance payloads before Cloak, Umbra, or MagicBlock take over as execution rails. Intelligence still feeds this lane by narrowing what should be signed and what must remain encrypted.
Ika and encryption sit in the middle of the operating system, not at the edge
This lane turns sensitive intent into commitment-safe artifacts before final wallet execution, while preserving the reviewer path through proof and documents.
Wallet history, stablecoin movement, counterparty posture, and read-node health are checked before a signer approves risk.
QVAC and deterministic analysis compress proposal, treasury, gaming, and RPC context into a clear pre-sign decision.
Sensitive payroll, vendor, and treasury intent becomes an encrypted manifest, commitment, custody route, or proof packet.
The connected wallet remains the execution boundary for Testnet governance, settlement rehearsal, and treasury motions.
Receipts, runtime logs, documents, and Solana explorer evidence keep the result inspectable without exposing private payloads.
Encrypted computation receipt for confidential payroll
The browser encrypts the payroll packet, creates commitments for the encrypted input and computed aggregate, then sends only ciphertext and hashes to the backend proof route.
Encrypted packet and proof receipt will appear here.
Programmable custody for private payroll and treasury execution
This workbench uses @ika.xyz/sdk on the read node to initialize Ika testnet, read the live network encryption key, choose the dWallet curve, and show a live execution lane for custody routing. It also reads the Ika Solana pre-alpha program and the funded Testnet/pre-alpha operator wallet used for the approval-flow lane.
The Ika SDK route response will appear here.
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.
Plan a sponsor-grade confidential operation inside the product
{
"requestId": "ENCRYPTED:CONFIDENTIAL-PAYROLL:MANIFEST-HASH-AND-COMMIT-REVEAL:ATTESTED-EVIDENCE",
"operationProfile": "Confidential payroll",
"privacyMode": "Manifest hash + commit-reveal",
"settlementMode": "Attested evidence",
"operatorVisibility": "Hybrid",
"sponsorLift": [
"Privacy",
"Umbra",
"Encrypt"
],
"recommendedAmount": "1,000 USDC",
"recipientCountHint": "8",
"posture": "Reviewer-safe confidential operation",
"rationale": "Prepare a governed salary or grant disbursement where the manifest stays off-chain and the settlement path remains reviewable. Use the existing private governance discipline and keep recipient detail in an encrypted off-chain manifest. Use the current settlement evidence posture with explicit reviewer-safe continuity.",
"reviewerPath": "/security",
"servicePath": "/services",
"settlementPath": "/documents/settlement-receipt-closure",
"proofPath": "/documents/confidential-payout-evidence-packet",
"nextOperatorAction": "Keep the manifest boundary explicit and carry the same operation plan into treasury review and governed execution."
}- Confirm the operation profile is confidential payroll and the recipient count posture still matches the intended treasury motion.
- Confirm Manifest hash + commit-reveal is the right privacy mode for the sponsor and reviewer expectations.
- Confirm Attested evidence keeps the trust boundary readable enough for this submission and release stage.
- Confirm Hybrid keeps the operation understandable to the target reviewer without weakening the privacy story.
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.
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.