Explore
Product navigation
Eitherway
Wallet-first
Testnet flow
Live dApp
Deliver a wallet-first product flow that normal users can run without terminal complexity
This route implements the Eitherway requirement as a real product lane: wallet connect, profile signing, partner selection, action continuation, and proof-linked continuity.
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.
Services route brief
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.
Lead with the product lane a buyer can try immediately from a Testnet wallet.
Keep pricing and billing language tied to the current public-good Testnet boundary, not to unshipped mainnet claims.
Use the commercial surface to show that PrivateDAO can evolve into a sustainable infrastructure company.
PrivateDAO uses this lane to bridge partner tracks into one clear user experience. The same connect/sign flow can feed private payroll, treasury rebalance, or governed market execution.
Eitherway live dApp lane
Wallet-first flow with real signature and real proof continuity
This lane closes the Eitherway requirement operationally: users connect a wallet, sign a profile challenge, and move into governed execution from the same interface.
Live configuration
Wallet: Not connected
Network: Testnet
Status: Connect a wallet and sign a profile challenge to start the live dApp flow.
Wallet UX checklist
Wallet picker with logos, installed auto-detect, and fallback install/open links.
Deep links for Phantom/Solflare and browser-return flow.
QR session handoff so users can continue in mobile wallet browser.
Review-first, sign-second, verify-third flow with proof route continuity.
Profile challenge signature is persisted as an operation receipt for reviewer traceability.