A public technical record for four live Telegram-native games, $TCULT Handle Desk live on the web, $TCULT Terminal in development, $TCULT Guard in production, current Vercel and Hostinger runtime lanes, read-only evidence, and later user-signed TON actions. $GRAM remains TON's native coin.
$TCULT begins with Telegram-native plush culture, then turns that attention into a concrete portfolio: four live games, $TCULT Handle Desk live on the web, $TCULT Terminal in development, and $TCULT Guard in production behind release gates.
Plush Tap: Daily Ritual, Plush Run: Gift Chase, and Plush Hop: Gift Tower are live on Vercel and Telegram. They are the participation layer: fast, mobile-native surfaces that invite people to open, play, share, and return.
The evidence lane is next. Handle Desk checks an exact Telegram username against public channel, supergroup, and Fragment evidence on the web. Terminal turns a pasted TON jetton address or explorer link into a fast panel, bundle analysis, and optional explanation. Guard checks official routes, Telegram paths, Fragment numbers, .ton domains, Getgems collections, addresses, and DEX links. All current milestones are read-only.
The TON blockchain matters because it sits close to Telegram behavior. $TCULT already lives in the language of Telegram groups, bots, mini apps, stickers, gifts, and social sharing. That makes the TON blockchain more than a settlement layer. It is the infrastructure connecting community rituals to wallet-aware tools, official resources, assets, verified records, and future applications.
$TCULT utilities are designed to open inside Telegram, feel mobile-first, and make the first useful action clear. The project keeps games public and simple while utility surfaces mature into more serious product lanes over time.
Any later wallet feature must remain non-custodial, user-signed, and protected by a clear pre-sign review. It is separate from today's read-only evidence claims.
TON Center API v3 provides indexed blockchain access for transactions, traces, jettons, NFTs, actions, wallet states, and analytics. That makes it suitable for scan cards, evidence tabs, explorer links, and read-only user education.
The live games use Vercel. Guard remains on its Vercel release path. Terminal targets a resident Node 20 Docker service on Hostinger after production approval.
The games remain the front door. Terminal and Guard add read-only evidence without turning unreleased work into a public promise.
| Layer | Job | Representative Products |
|---|---|---|
| Community play | Bring people back through fast, shareable loops. | Plush Tap: Daily Ritual, Plush Run: Gift Chase, Plush Hop: Gift Tower. |
| Identity and collection | Make community participation visible and collectible. | Sticker packs, PFPs, gift concepts, local cosmetic gift shelves. |
| Exact-name evidence | Check an exact Telegram username against public channel, supergroup, and Fragment evidence before acting. | $TCULT Handle Desk, live on the web at handles.tcult.site; the Telegram route is held until real-device QA. |
| Terminal evidence | Turn a pasted TON jetton address or explorer link into a fast panel, bundle analysis, and optional explanation. | $TCULT Terminal, in development and verified locally with fixtures. |
| Route evidence | Compare routes and links against readable official-source context before interaction. | $TCULT Guard, in production behind redeploy, DNS, Telegram, provider, and mobile QA gates. |
| Later research | Evaluate persistence and user-signed actions without changing the current read-only boundary. | Future Supabase persistence and TON Connect flows only after separate approval and security gates. |
The M2 bot gateway and Telegram conversation preview are fixture-verified locally. Terminal reuses @TCultPlushBot and does not replace the current default Mini App menu button.
Guard V1 is implemented locally. A prior public alias exists, but the current release still requires redeploy, branded DNS, Telegram configuration, provider configuration, and mobile QA before it may be described as publicly released.
The current architecture connects Telegram, four live games, Handle Desk, Terminal, Guard, public TON evidence providers, Vercel, Hostinger, and release registries. Future persistence and user-signed actions remain outside today's release claims.
Terminal and Guard begin with user-submitted inputs and public data. Each product normalizes the input, reads available evidence, and returns a conservative result without taking custody or executing a transaction.
| Component | Public Function | Boundary |
|---|---|---|
| Handle Desk lookup | Checks an exact Telegram username against public channel or supergroup evidence and official Fragment evidence, then states the honest next step. | No claim about personal handle status; that is confirmed only in Telegram settings. |
| Terminal gateway | Receives a TON jetton address or explorer link through @TCultPlushBot and returns progressive evidence cards. | No transaction execution. |
| Terminal scan pipeline | Builds a fast panel, bundle analysis, and filtered explanation from provider evidence. | No financial recommendation language. |
| Guard evidence flow | Checks routes, handles, domains, collections, addresses, and DEX links against official-route context and public providers. | No safety guarantee or public accusation. |
| Current providers | TonAPI, TON Center, and other public evidence reads where available. | Provider failures remain visible and conservative. |
| Later persistence and actions | Future Supabase records and TON Connect flows only after separate implementation, security, and approval gates. | Non-custodial, user-signed, and not part of the current release. |
Acton, Tolk, on-chain registries, persistent accounts, wallet context, and transaction flows remain research or later milestones. None of them is the current delivery path for Terminal or Guard.
Any future record layer must remain public, minimal, verifiable, and separate from recommendation language. Unknown inputs must stay unknown rather than being labeled by assumption.
The $TCULT studio uses agents for research, code handoffs, architecture updates, media planning, QA scans, public-copy checks, and iteration across games, website, lore, and utility apps.
Human approval remains the gate for public releases, production changes, security-sensitive flows, wallet behavior, and anything involving user trust.
Later wallet and transaction milestones must remain non-custodial and user-signed. Every action requires a clear pre-sign preview, quote or request expiry where relevant, visible fees, and an explicit user decision.
Automatic trading, custody, seed phrase handling, and financial direction remain outside the product boundary. These later milestones do not change the current status of Terminal or Guard.
| Status | Product | Verified Boundary |
|---|---|---|
| Live now | Plush Tap, Plush Run, and Plush Hop. | Three Telegram routes and three Vercel web apps are public. |
| Live on the web | $TCULT Handle Desk. | The branded web route is public. The Telegram route opens after real-device QA. |
| In development | $TCULT Terminal. | M2 gateway and local fixture preview are verified. Production deployment and live Telegram QA remain open. |
| In production | $TCULT Guard. | V1 is implemented locally. Redeploy, DNS, Telegram configuration, providers, and mobile QA remain open. |
| Later research | Persistence and user-signed actions. | Separate architecture, security, testnet, and approval gates are required before public commitment. |
$TCULT builds trust through careful language. The public copy is confident about the roadmap, and the utility layer never overstates what a scan proves.
This public white paper reflects the August 16, 2026 $TCULT app registries, Handle Desk release records, Terminal execution plan, Guard release status, and public TON documentation.