> For the complete documentation index, see [llms.txt](https://scmd69.gitbook.io/scmd69-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://scmd69.gitbook.io/scmd69-docs/scmd69-ecosystem-documentation.md).

# SCMD69 — Ecosystem Documentation

**Version:** 1.0 — project-approved draft; technical verification pending\
**Updated:** 9 October 2026\
**Network:** TON (The Open Network)\
**Token name:** SCMD69\
**Token symbol:** $CMD69\
**Jetton master:** `EQAj5b62MW-WTXXa3jr02byWNUtCdWpVohFoGOo7GznlKtD9`

## 1. Overview

SCMD69 is the native utility token of Club69, an independent ecosystem being developed within Telegram and the TON blockchain.

Club69 develops interconnected infrastructure for digital services, applications, social tools, and internal economic mechanisms linked by a shared token economy. The project builds its own products and integrates selected solutions from independent developers. SCMD69 functions as a common economic instrument across participating services, applications, and community activities.

Development is incremental, with an emphasis on the stability and practical use of operating products.

## 2. Origins and Concept

Club69 began as a small Telegram community established for everyday conversation. As it developed, members introduced social tools, interactive games, internal transactions, and digital services. SCMD69 emerged from this existing community environment as a means of connecting its activities through a common economy.

The community therefore predates the token. Club69 is not limited to a single application or product category: it expands through internally developed services and approved integrations with independent developers.

## 3. Ecosystem Structure

### 3.1. Core Telegram infrastructure

**Application:** [@SCMD69\_bot](https://t.me/SCMD69_bot)

The primary Telegram bot supports internal SCMD69 balances and transfers, activity rewards, rankings and member statistics, automated community news, message translation, social tools, and interactive activities.

Transfers between users inside the bot are recorded in its internal ledger. Deposits and withdrawals connect that ledger to the TON blockchain. The community also uses topic-based spaces, including an English-language area.

### 3.2. SCMDMobile

**Status:** Club69-developed operational product\
**Application:** [@SCMDMobileBot](https://t.me/SCMDMobileBot)

SCMDMobile provides international eSIM mobile-data plans. Supported plans can be purchased using SCMD69. Availability is subject to destination, device compatibility, and the terms of the selected plan.

### 3.3. Poker69

**Status:** Operational gaming product\
**Application:** [@Poker\_69bot](https://t.me/Poker_69bot)

Poker69 is a separate Telegram poker application within Club69's interactive-products category. Gaming is only one area of the ecosystem, alongside digital services, social infrastructure, and external integrations. Participation may involve financial risks and jurisdiction-specific restrictions.

### 3.4. HateCaps

**Status:** Independent product by a developer working with the project\
**Application:** [@HateCapsBot](https://t.me/HateCapsBot)

HateCaps is an NFT product integrated into Club69. Its caps provide participation functions and mechanisms for allocating a portion of revenue from supported infrastructure activities. Staking is available within the HateCaps application. Exact rights, reward conditions, and restrictions are defined by the relevant product rules; returns are not guaranteed.

### 3.5. SwiftGifts

**Status:** Independent third-party platform\
**Application:** [@swiftgifts](https://t.me/swiftgifts)

SwiftGifts is an independently operated Telegram Gifts service that has integrated SCMD69 as a payment method. It is not owned by Club69. This integration provides a use case for the token outside Club69's own applications.

## 4. SCMD69 Economy

SCMD69 is used as a common economic instrument across participating applications. Its uses include payments for supported digital products and services, transfers between members, interactive activities, community rewards, and transactions with integrated external services.

### Internal balances and withdrawals

Club69 uses a custodial internal-balance system. According to the project administrators, SCMD69 backing user balances is held in the project's main wallet, `scmd.ton`. User liabilities, the burn fund, and project reserves are tracked separately in the internal accounting system.

Users can initiate automated withdrawals to personal TON wallets, subject to the operating rules below.

| Withdrawal parameter         | Current setting           |
| ---------------------------- | ------------------------- |
| Minimum amount               | 100,000 SCMD69            |
| Withdrawal fee               | 3%                        |
| Cooldown between withdrawals | 10 minutes                |
| Daily withdrawal limit       | 5,000,000 SCMD69 per user |
| Processing                   | Automatic                 |

The minimum amount may be revised as market conditions change. Withdrawal fees support infrastructure development, additions to liquidity, and community rewards. These uses do not have fixed allocation percentages; distribution decisions are made by Club69 administrators.

Detailed project financial records are accessible to project administrators, not published as a comprehensive public financial statement. Full backing of internal balances has been reported by the project but has not been independently reconciled in this document.

## 5. Tokenomics

### Token information

| Property                                           | Value                                              |
| -------------------------------------------------- | -------------------------------------------------- |
| Blockchain                                         | TON                                                |
| Token name                                         | SCMD69                                             |
| Symbol                                             | $CMD69                                             |
| Jetton master                                      | `EQAj5b62MW-WTXXa3jr02byWNUtCdWpVohFoGOo7GznlKtD9` |
| Reported initial supply                            | 1,000,000,000 SCMD69                               |
| Supply reported by TON API on 9 October 2026       | 975,772,902 SCMD69                                 |
| Difference from initial supply                     | 24,227,098 SCMD69                                  |
| Decimals                                           | 9                                                  |
| Mintable flag reported by TON API                  | `false`                                            |
| JVault strategic reserve balances at time of check | 250,000,000 SCMD69                                 |

**Verification note:** The supply and mintability figures above were read from TON API using the project's terminal on 9 October 2026. They are a historical snapshot, not live values. The difference from initial supply is not presented as a fully independently audited total of burns; a transaction-level reconciliation remains outstanding.

### Burn mechanism

Club69 operates a token-burn fund financed by a 0.5% allocation from internal member-to-member SCMD69 transfers and by penalties imposed for confirmed violations of community rules.

When the fund reaches 10,000,000 SCMD69, project administrators manually execute a token burn using TON Minter. Members can view the fund's internal accounting balance with the Telegram command `фонд сжигания` (“burn fund”). Fund assets are intended exclusively for burning.

Tokens recorded in the fund are not yet burned: total supply decreases only after a successful on-chain burn transaction. The fund is tracked separately but is held within the main project wallet, not in a separately locked on-chain wallet.

## 6. Strategic Reserve and Vesting

The project's strategic reserve consists of 250,000,000 SCMD69, equal to 25% of the originally reported token supply. At the time of the October 2026 check, the three addresses below collectively held that amount in JVault lock contracts.

| JVault lock                                          | Tokens held at check | Published release conditions                                                                   |
| ---------------------------------------------------- | -------------------: | ---------------------------------------------------------------------------------------------- |
| [#3486](https://jvault.xyz/locker/lock_content/3486) |    50,000,000 SCMD69 | 100% scheduled for 30 September 2027, 10:31 UTC                                                |
| [#1115](https://jvault.xyz/locker/lock_content/1115) |   100,000,000 SCMD69 | Staged releases beginning 27 April 2027, 07:00 UTC; metadata indicates vesting into April 2028 |
| [#3007](https://jvault.xyz/locker/lock_content/3007) |   100,000,000 SCMD69 | 100% scheduled for 9 May 2027, 10:30 UTC                                                       |

These dates and release descriptions are taken from the JVault NFT metadata obtained through TON API. The exact on-chain vesting mechanics of lock #1115 require further validation. The amounts above are snapshot balances and should not be assumed to remain locked indefinitely.

The stated purpose of the reserve is long-term holding, intended to reduce the ecosystem's dependence on concentrated holdings by large token holders. The project intends to continue holding these tokens beyond their lock periods. That intention is a project policy, not a contractual lock after the relevant unlock dates, and does not guarantee price stability.

## 7. Liquidity and Trading

SCMD69 trades against TON on [STON.fi](https://ston.fi/). Liquidity is supplied by both Club69 administrators and independent holders. The project does not levy an additional token-specific purchase or sale fee; normal DEX trading fees apply.

Liquidity belonging to the project is **not currently locked** and may be withdrawn by its controlling providers. Strategic reserve locking through JVault should not be confused with liquidity locking. Liquidity availability, slippage, and market prices can change substantially.

## 8. Governance and Integrations

Club69 administrators set the ecosystem's overall development direction, manage project reserves and infrastructure, and decide which external products receive official partner status.

Independent developers may add support for SCMD69 without project approval. However, integrating the token alone does not make a product an official Club69 partner. Official inclusion requires approval by Club69 administrators.

HateCaps provides separate participation and voting mechanisms under its product-specific rules. Holding SCMD69 alone does not confer shareholder rights, ownership in an entity, or control of project reserves.

## 9. Project and Legal Status

Club69 is an independent project developed by a small team. It operates in an experimental, continuously evolving development phase. SCMDMobile and Poker69 are operational products, while the broader Telegram infrastructure and integrated applications continue to receive live testing and updates.

As of 9 October 2026, Club69 has not been registered as a separate legal entity. Formal registration is intended as the project matures but has not yet taken place. SCMD69 is not equity in a registered company and does not confer shareholder rights or a guaranteed financial return.

Products may be subject to local laws, eligibility requirements, and platform restrictions.

## 10. Security and Limitations

Club69 combines TON on-chain transactions with off-chain internal accounting. Internal balances use a custodial model: users do not control the private keys to the project's main wallet. Private-key access is restricted to project creators, while users can initiate withdrawals through the bot.

Administrators maintain financial records and manually reconcile recorded obligations and reserves. The project has not represented this process as a fully automated proof-of-reserves system, and comprehensive financial statements are not public.

Risks include token-price volatility, smart-contract and software failures, security of custodial wallets, availability of withdrawals and liquidity, third-party services, and changes in applicable rules or law. Users should verify contracts and official links before transacting and should never disclose private keys or recovery phrases.

## 11. Official Resources

| Resource                 | Link                                         |
| ------------------------ | -------------------------------------------- |
| Website                  | [scmd.ton.run](https://scmd.ton.run/)        |
| Telegram announcements   | [@scmd69](https://t.me/scmd69)               |
| Telegram community       | [@scmdchat](https://t.me/scmdchat)           |
| Main Club69 bot          | [@SCMD69\_bot](https://t.me/SCMD69_bot)      |
| X                        | [@scmd69](https://x.com/scmd69)              |
| SCMDMobile               | [@SCMDMobileBot](https://t.me/SCMDMobileBot) |
| Poker69                  | [@Poker\_69bot](https://t.me/Poker_69bot)    |
| HateCaps                 | [@HateCapsBot](https://t.me/HateCapsBot)     |
| SwiftGifts (independent) | [@swiftgifts](https://t.me/swiftgifts)       |
| DEX                      | [STON.fi](https://ston.fi/)                  |

## 12. Documentation Maintenance

This document describes the ecosystem as of its revision date. Features, interfaces, operational terms, integrations, and allocations may change. Current rules in each application and official project announcements take precedence for day-to-day product operation.

Supply, reserve, and vesting figures should be rechecked against TON blockchain data when the documentation is updated. Material revisions should be reflected with a new revision date.

***

### Outstanding independent verification

Before describing the documentation as independently audited, the following require additional evidence:

1. Reconciliation of all burn transactions with the reported change in token supply.
2. Confirmation of the full on-chain vesting schedule for JVault lock #1115.
3. Independent reconciliation of user liabilities and segregated internal funds against actual on-chain reserves.
4. Current liquidity size and trading-pool contract, if quantitative liquidity claims are later added.

**This document is an informational overview, not an independent audit or a promise of future results.**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://scmd69.gitbook.io/scmd69-docs/scmd69-ecosystem-documentation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.