Place each submission in live, Toccata, based-app, or research lane.
Kaspa builder funnel
Kaspa builder review queue.
This is the review model for emailed builder and supporter submissions. It is not a live public marketplace: submissions are reviewed privately first, then published or routed only as opt-in cards.
Timing note: payments are live today. New app-layer rules need Toccata activation and supporting wallets or tools.
Board rules.
- Private first. Raw submissions stay private until the founder opts into a public card.
- Public card. Cards show idea, user, Kaspa fit, stage, evidence, help needed, and contact rule.
- Score meaning. The score measures review readiness, not financial quality.
- Intro consent. Introductions happen only when both sides opt in.
- Status labels. Live, testnet, targeted, roadmap, and research labels stay visible.
Possible public card lanes.
| Lane | Public card shows | Examples |
|---|---|---|
| Live network | Payment, receipt, API, wallet, node, or accepted-transaction proof. | Receipt wallet, explorer support flow, API monitor |
| Toccata shaped | Vault, escrow, asset, assurance, or proof-check rule with pending mainnet label. | Team vault, grant assurance, event pass |
| Based-app prototype | Shared state, replay, proof plan, and app-specific settlement path. | Auction state, task board, liquidity records |
| Research heavy | Oracle, privacy, MEV, external fact, or full app-composition dependency. | Event market, private commitments, cross-app actions |
Review loop.
Remove private names, email, city, and company data unless public sharing is approved.
Rate user, Kaspa fit, evidence, risk, distribution, and next action.
Create a short public card and a private intro note.
A human checks claims and consent before publishing or sending intros.
Share approved cards or intros only where the submitter agreed.