PrivateDAO turns governance, treasury, billing, and learning actions into Torque custom_events through a protected read-node relay. The growth loop stays attached to verifiable product behavior instead of vanity traffic.
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.
PrivateDAO now sends real product actions into Torque from the protected read-node
The browser never receives the Torque key. It prepares the action payload, the read-node signs the delivery boundary with server-only credentials, and Torque returns an accepted ingestion receipt.
Torque becomes the measurable retention layer for real PrivateDAO operations
The loop is intentionally strict: PrivateDAO does not reward passive page views. It converts wallet-first actions into custom_events, forwards them through the protected read-node relay with verified credentials, then sends the user back to a proof route where the action can be inspected.
A user creates a DAO, creates a proposal, signs a billing route, finishes learning, or executes a private treasury event.
The browser builds a Torque-style custom_event payload with wallet, route, network, reward intent, and proof routes.
The read-node endpoint /api/v1/torque/custom-event forwards the event with a verified server-side Torque ingestion key.
The user lands back in Judge, Proof, or Learn so the incentive loop points to a real product action, not a vanity visit.
The page builds events and the read-node forwards them to Torque
The visible workbench builds inspectable event payloads, records local delivery state, and posts to /api/v1/torque/custom-event. The API route exists in the read-node and forwards to Torque with a scoped server credential. This keeps private keys out of the browser while preserving a testable growth UX for judges.
Torque is wired as an operator-controlled growth engine, not a blind reward faucet
The page exposes the public product loop while the MCP workflow remains an operator action: authenticate, choose project context, preview the query, confirm reward economics, and publish evidence. This prevents the common leaderboard mistake where raw activity values become uncapped token payouts.
Rank operators by verified private treasury actions or governance activation.
Return a small percentage after a signed billing SKU, proposal execution, or treasury route preview.
Reward learning completion, first wallet execution, or weekly verified participation.
Distribute partner, contributor, or judge-demo rewards to a fixed wallet list.
Torque MCP token stays local/operator-side; ingestion keys stay server-side in the read-node.
PrivateDAO project cmpm5lnzt00hujq1jd9imtp2o is the active growth workspace.
The assistant should load project context before choosing formula, source, schedule, or reward type.
Every query must be previewed before an incentive is created; no blind leaderboard formulas.
Each incentive should link back to /judge, provider status, event ID, and accepted ingestion proof.
Convert real product actions into retention events and incentive loops
Torque fits PrivateDAO as a measurable growth layer: users do not earn rewards for visiting a page; they earn from wallet-first actions such as creating a DAO, creating a proposal, signing a billing SKU, or finishing the Solana frontend learning path.
The event workbench records local activity immediately and forwards the same payload to Torque through the verified read-node relay. This keeps the growth loop tied to product behavior rather than detached campaign copy.
{
"userPubkey": "4Mm5YTRbJuyA8NcWM85wTnx6ZQMXNph2DSnzCCKLhsMD",
"timestamp": "client-generated-on-record",
"eventName": "dao_created",
"data": {
"reward_intent": "onboarding rebate",
"route": "https://privatedao.org/govern/",
"network": "solana-testnet",
"product": "private-governance-and-stablecoin-treasury",
"proofRoutes": [
"https://privatedao.org/judge/",
"https://privatedao.org/proof/?judge=1"
]
}
}