One directory.
Each thread has its own state.
Choose /general/, /tari/ or /pol/. Every category is public and reads conversations from the same deployed Tari board. Your browser filters threads using the category recorded in each opening post.
Built on
Choose a forum
General opens by default. You can read without a wallet. Choose Start a thread in your selected forum to begin a conversation, or open a thread and use Leave a reply. Review post and Review reply let you check the text and network fee before publishing. Categories and thread titles are public. Choose a public body or a sealed body encrypted in your browser. Accepted messages cannot be edited or deleted.
For wallet setup, funding, forgotten PINs and pending submissions, follow the getting-started guide. Hide thread affects only your browser's view; Show hidden threads lets you find it again.
How a conversation is stored
Published Tari template · shared contract code
A template is the reusable contract code. A component is an individual instance with its own state and address. Each thread already has a separate component; creating a thread does not publish another copy of the template.
Where the data lives
| Data | Location |
|---|---|
| Category, opening text and replies | On-chain post-page state: public category and title, with readable public bodies or encrypted sealed bodies. Invitation keys are required to decrypt sealed bodies. |
| Thread directory and page references | On-chain board and thread components. |
| Wallet words and private keys | Password-encrypted storage in your browser. |
| Reads and submitted transactions | Forwarded through the app and Tari's public testnet indexer. The app has no separate forum-content database. |
Older threads without a category, or with the retired category, appear in General. Categories organize the feed; the current template does not enforce a category registry or separate moderation rules. Other clients can interpret the same stored category data.
Capacity and growth
- 128 threads per board, shared by all three categories. Splitting threads into separate components does not remove this directory limit.
- 2,048 posts per thread, including the opening post. That is at most 128 pages of 16 posts.
- 4,096 bytes per stored post payload. JSON metadata, including the category, uses part of that allowance.
Post pages keep each write bounded, but stored history and indexer work still grow. Reading the feed currently loads thread metadata and opening posts to identify their categories. Storage and execution also affect Tari transaction fees.
When a thread fills, start a continuation. When the board fills, another board component is needed. Automatic directory rollover and independent board components for each forum are future work; this version does not silently create either. Existing accepted posts have no edit or delete method, and a testnet reset can remove history.
Public metadata, optional sealed bodies
Every forum has public titles and categories. Public bodies are readable by anyone; sealed bodies need an invitation key shared through a trusted private channel. Anyone with that key can read and share the full history and future messages. There is no key revocation or author authentication. The contract stores no author field. Wallet keys stay in your browser, but transaction timing, fees and the transaction graph remain observable. A separate thread component does not by itself make its poster anonymous.