Product navigation
This route exposes MagicBlock as an execution lane: live Solana RPC proof for the corridor, finalized private payment receipts, challenge initiation, bearer-token private reads, and wallet-signed continuation in one place.
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.
MagicBlock is bound to the same visitor-repeatable on-chain claim layer
The corridor keeps its native MagicBlock proof endpoint and finalized Solana Testnet receipts, while every visitor can create a fresh PDAO_ENCRYPTED_CLAIM_V1 Memo claim from the browser and verify the signature on Explorer. Building and development continue without interruption as PER delegation evidence is deepened.
MagicBlock proof starts on-chain, then protects private reads
The public proof endpoint checks the corridor PDA and finalized Testnet receipts live through Solana RPC. Private balances remain behind MagicBlock challenge/login, then the user wallet signs and submits any payment transaction to the connection returned by the payments API.
Private payments are tied to explorer-visible Testnet receipts
PrivateDAO exposes the MagicBlock corridor as a live proof lane: the read-node verifies the corridor PDA and the deposit, private transfer, withdraw, settle, and execute signatures directly against Solana RPC. Private balance reads still require MagicBlock challenge/login, so sensitive state remains wallet-authorized.