Channel
@theopencoin_community
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
21,377subscribers
-136 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002490763225 |
|---|---|
| Type | Channel |
| Username | @theopencoin_community |
| Description | App: @TheOpenCoin_bot Chat: @theopencoin_chat |
| Created | Between 1 September 2024 and 22 January 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/theopencoin_community |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 01:03 | 21,377 | -26 |
| 13 Aug 2026, 15:26 | 21,403 | -12 |
| 12 Aug 2026, 18:08 | 21,415 | -20 |
| 11 Aug 2026, 19:32 | 21,435 | -16 |
| 10 Aug 2026, 20:04 | 21,451 | -22 |
| 9 Aug 2026, 20:32 | 21,473 | -15 |
| 8 Aug 2026, 23:51 | 21,488 | -17 |
| 8 Aug 2026, 00:44 | 21,505 | -8 |
| 7 Aug 2026, 14:31 | 21,513 | no change |
| 7 Aug 2026, 14:28 | 21,513 | first reading |
20 posts held, back to 22 January 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 21 pagesof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 22 February 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
3,355 reactions across 20 posts, in 45 distinct kinds. The most used accounts for 37.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,271 | 37.9% | |
| ❤ | 567 | 16.9% | |
| 🔥 | 507 | 15.1% | |
| 💩 | 180 | 5.37% | |
| 🤡 | 153 | 4.56% | |
| 👎 | 110 | 3.28% | |
| 🤣 | 97 | 2.89% | |
| 😭 | 73 | 2.18% | |
| 👀 | 31 | 0.924% | |
| 😁 | 29 | 0.864% | |
| 🐳 | 26 | 0.775% | |
| 🤮 | 26 | 0.775% | |
| 🖕 | 22 | 0.656% | |
| 🥰 | 21 | 0.626% | |
| 🏆 | 20 | 0.596% | |
| 👏 | 20 | 0.596% | |
| 💔 | 19 | 0.566% | |
| 🍌 | 16 | 0.477% | |
| 🕊 | 16 | 0.477% | |
| 🤝 | 15 | 0.447% | |
| 25 further kinds | 136 | 4.05% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 3,355reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 22 January 2025 to 22 February 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
AgentsCloud will soon integrate Telegram’s Cocoon network for private inference — and we’ll subsidize credits for the first 100 agents. To make this possible, we first built a proper SDK — since the current entry barrier to Cocoon is quite high. The SDK is now open-source, so anyone can start using Cocoon in under five minutes https://x.com/indie_cto/status/2025674810739835222
❤7👍4🤣4🔥2
⚫️ Completely new chapter. TOC users have always been some of the most proactive, builder-mindset people in the Telegram ecosystem. That was the original vision — gathering people who want to shape the future of apps through governance directly inside Telegram. After TOC was closed, part of our team started working on something new — building an AI-agents platform for Telegram. You’ve probably seen many ambitious …
🤣16❤8👍7💩6🔥4🤡2
⚫️ Hey TOC community, Our journey has come to an end All refund requests — both through the app and the Google form — have been completed The last ones were processed today. Thank you for being with us. Stay tuned and keep following the team’s progress: @noscamcryptobuilder
👍32🥰20❤15👎11💩4😭4🦄2🫡2
🚨 Last Call 🚨 As previously announced, we’re shutting down the app tonight. For those who missed the refund claim, a Google Form will remain open for one more month. After that, any unclaimed funds will be considered a donation to the team. If you have any issues with refunds, reach out in the chat ASAP!
😭35👍30❤🔥14🖕12🔥7🗿2🫡2👾1
More than half of the users have already claimed their refunds. We truly appreciate those who chose to support the team by donating instead of claiming. Thank you! We hope to find a way to reward such generosity in the future. Regarding the two previously discussed issues: TON Refund Issue: If you claimed a TON refund but didn’t receive it, you have the opportunity to reclaim it now. We apologize for the inconveni…
👍43🤡26❤24👏9🕊5🔥3👀1👎1
From now on, users can claim their refunds - or choose to donate them to the team and climb the leaderboard. Please note that we’re facing some technical issues: Stars: In rare cases, we’re encountering undocumented Telegram API errors. We’re actively working on a solution. TON: Due to occasional node errors, some transactions may get stuck but will be processed later. Rest assured, we have all the necessary data…
👍62💩30❤23🤡19🕊8🔥7🖕4😁4
⚫️ Is This the End of TOC...? The community has spoken. The voting results are in, and the majority has chosen partial refunds and shutdown. Many are struggling due to the current market conditions, and as a community-owned project from day one, we must respect and implement the decision made by our members Within the next 24 hours, we will enable the refund claim functionality, allowing everyone to claim their ref…
❤69👍48😭34🤝15🤡13🙏6😱5🖕4
⚫️ Hello TOC Community, We’d like to provide you with an update on our progress and outline the next steps. ⚫️ Our Progress So Far We've put in significant effort to make our ecosystem more decentralized and resilient. Here’s a summary of what we’ve accomplished: - Bot-Farm Prevention: We introduced a logarithmic referral system to ensure only activated referrals are counted. - Enhanced Security: We implemented fo…
👍89❤39👀30💩28👎20💔19🍌8🤡8
⚫️ The third halving is behind us, and block rewards are now 125 TOC Approximately 7.2% of the blocks have been mined so far. You're still early
👍82🤣45❤26🔥21🤡10👻5💊5🍌4
GOVERNANCE PROPOSAL #14 EXECUTED ⚫️ Pool owners can now promote users to admin roles Next step: implementing "admin salaries" — a portion of the pool's mining fees allocated to admins
💩64👍63❤31🔥18😐7👨💻5😁4
We’re launching a partner program for new OTC market listings! As a community-owned ecosystem, we want our community to help us grow and benefit from the success! ⚫️ OTC has proven its functionality and stability—many issues and security vulnerabilities have been resolved, and the platform is now much more mature! From now on, anyone who brings us a new partner to list on OTC will receive a share of all commission…
🔥44👍36🤣15💩11❤9😁5👎4🆒4
⚫️ The OTC is growing and proving it works, even though it's still in beta Anyone can now buy $TOC from it and transfer it to the app t.me/OTCbyTOC_bot/app
👍68❤25🔥21👎12👏6🤣6🎉5🤡5
Showing the 12 most recent of 20 posts we hold for @theopencoin_community. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 15 August 2026 — this entry's latest reading, not the date you are reading this.
“TOC - community” (@theopencoin_community), 21,377 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/theopencoin_community.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.