Getting Started
This guide reflects the current code in apps/web, services/api, and programs/toldya. The platform core is commit-reveal notarization on Solana, with web and API layers handling auth, social data, and discovery.
Prerequisites#
- A wallet-standard Solana wallet for signing transactions.
- Some SOL for network fees and configured protocol fees.
- A running API service if you are self hosting and want feed/reveal/social endpoints.
Connecting Your Wallet#
On web, clicking Connect Wallet uses Wallet Standard discovery, then triggers SIWS via /api/auth/siws/nonce and /api/auth/siws/verify.
After verification, the app issues auth cookies. Backend API routes also support bearer JWT for non-browser clients.
Creating Your First Commitment#
- Open Create (
/create) or use the N shortcut. - Write your prediction text and select a category.
- Choose a commitment type: standard, time-capsule, or collaborative.
- If using time-capsule mode, set
scheduledRevealAt. - Sign and submit the commit transaction. The client computes
SHA256(DOMAIN || creator || salt || message)and stores only the hash on-chain. - The web client stores the generated salt in session storage under
toldya_salt_<commitPda>for later reveal usage.
Commit accounts use PDA seeds ["commit", creator, commitment]. The commit account stores the creator, commitment hash, timestamps, status, and reveal reference hash.
Revealing (Current State)#
The API service exposes POST /api/v1/reveals to publish reveal content and GET /api/v1/reveals/:commitPda to read reveal details.
In this web app branch, reveal data is consumed throughout feed/detail pages, but dedicated reveal submission UI is not yet exposed as a first-class page/action.
Commitment Slots#
The web client derives slot limits with getMaxSlotsForScore() from core tier definitions:
| Tier | Score Range | Slots |
|---|---|---|
| Newcomer | 0-19 | 5 |
| Bronze | 20-39 | 5 |
| Silver | 40-59 | 7 |
| Gold | 60-79 | 10 |
| Diamond | 80-94 | 15 |
| Legendary | 95-100 | 20 |
Fees#
The create flow shows a live fee estimate, with a fallback display value of 0.00125 SOL while RPC estimation is loading. Final cost depends on current network fees and protocol config on-chain.
Additional paid surfaces (unlocks, subscriptions, boosts) are handled by dedicated API endpoints and verified on-chain transaction signatures.
Next Steps#
- Predictions — detailed route and feature coverage for counters, threads, retractions, and advanced commit modules.
- Social & Challenges — follow graph, challenges/events, sharing surfaces, and feature-gated social modules.
- Reputation — current tier/slot mappings, streak milestones, badges, and leaderboard metrics.