Channel
@oraichain_official
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,898subscribers
-50 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001493377288 |
|---|---|
| Type | Channel |
| Username | @oraichain_official |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/oraichain_official |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 16 September 2026 and assigned it the closest of 31 fixed categories, at 72% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 11:38 | 1,898 | -8 |
| 11 Sept 2026, 15:00 | 1,906 | -1 |
| 7 Sept 2026, 03:22 | 1,907 | -6 |
| 2 Sept 2026, 20:16 | 1,913 | -5 |
| 30 Aug 2026, 20:07 | 1,918 | -9 |
| 27 Aug 2026, 15:27 | 1,927 | -5 |
| 24 Aug 2026, 06:04 | 1,932 | -1 |
| 20 Aug 2026, 08:33 | 1,933 | -6 |
| 17 Aug 2026, 10:53 | 1,939 | -5 |
| 14 Aug 2026, 03:38 | 1,944 | -1 |
| 10 Aug 2026, 11:48 | 1,945 | -4 |
| 7 Aug 2026, 16:34 | 1,949 | +1 |
| 6 Aug 2026, 20:45 | 1,948 | no change |
| 6 Aug 2026, 20:38 | 1,948 | first reading |
21 posts held, back to 20 April 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of 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 21 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
135 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 51.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 69 | 51.1% | |
| ❤ | 34 | 25.2% | |
| 😁 | 16 | 11.9% | |
| 👏 | 9 | 6.67% | |
| 😢 | 5 | 3.70% | |
| 👍 | 2 | 1.48% |
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 21 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 135 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 20 April 2026 to 7 August 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.
🚀 The H2 Roadmap is live. One of the biggest lessons from H1? Execution alone isn't enough. Live evidence, strong risk controls, trustworthy strategy records, and one connected Quant experience matter just as much. Those lessons helped shape our H2 priorities—from deeper market intelligence and richer strategy research to expanding $ORAI's role across the Quant ecosystem. 📖 Read the full roadmap: https://x.com/ora…
🔥4
No more teasers after this. H2 Roadmap. This week. ⏰😈
🔥11
🧑💻 One less thing to handle manually. You can now close open MT5 positions based on Buy, Sell, Profit or Loss—directly from Quant Terminal. Less manual work. More control. Try it now ➡️ https://quant.orai.io/dashboard?network=mt5
🔥3
📢 We've moved to a new customer support system! Need help or have a question? Submit a support ticket here: t.me/OraichainCS_bot Or simply type !support in the community chat, and the ticket link will appear automatically.
🆕 A quick update on the Polymarket Vault At the end of July, we'll be pausing active trading. Since launching in May, the Vault has grown from 1.00 to 1.92, reaching a high of 1.94. Over the past few months, it has: * Closed 452 positions * Recorded an approximately 75% win rate * Generated $17.6K in net PnL As prediction-market opportunities have become more limited, we're choosing not to force trades that don'…
😢1
Quant Terminal today is a very different product than it was at the start of H1. ✈️ 🟢 Over the past six months, 10+ proprietary quant models have been backed by 130+ days of operating history, while execution expanded across crypto and TradFi through Binance, Hyperliquid , Lighter, and MT5-connected brokers. 🟢 Along the way, Quant Cowork made strategy backtesting more accessible. GRV and XAU Alpha grew to nearly $1…
🔥13❤2
5 Quant Strategy Groups. 56 Green Days. Live on Our MT5 Headless Infra. 📈 We are not just building execution infra. Our proprietary strategies are already trading live—some fully automated, others with a human co-pilot. Our stack also includes our own exclusive XAU Index and ATP Macro Engine. Disclaimer: June + July snapshot. Account sizes and denominations vary, so results are compared by percentage—not nominal P…
👏9❤1
🚀 RUNNING QUANT TRADING STRATEGIES JUST GOT MUCH EASIER Quant Terminal now supports MT5 accounts. No more managing VPSs, MT5 installs, or trading infra. Just focus on building and running better strategies. What you can do ✅ Connect your MT5 account ✅ Backtest Oraichain strategies ✅ Deploy to demo or live ✅ Configure strategy params ✅ Monitor positions & performance Why it matters Quant Terminal is no longer l…
🔥12
🛠 Oraichain <> Solana Bridge Retirement Notice After careful review, we’ve decided to retire the Oraichain <> Solana Bridge soon due to low real retail activity and limited ongoing demand, so we can focus resources where users are most active. Users who still need to bridge assets are recommended to complete your bridge requests within July. To ensure smoother processing, all remaining bridge requests will be hand…
❤7😢2
☀️ Summer deal for Polymarket Vault users 🎫 Polymarket Vault is back, and summer access is now open 🔥 This June, the ORAI staking requirement is removed. That means you can deposit directly into the Polymarket Vault without staking ORAI first, saving one extra step and keeping your capital setup lighter. Available until June 30, limited slots ✨: https://quant.orai.io/vault-v2/0xf90e1b849bfb17d57abdb07438d68ac787b…
❤6🔥1
Before you click around blindly, read this: ✨ quant.orai.io/docs The official documentation for Quant Terminal is now live. Everything you need to understand the product better, explore features, and move with more conviction.
🔥13
XAU Agent Update We’re temporarily maintaining the XAU Agent to improve trading consistency and overall execution quality. The goal is simple: make the agent more stable before scaling further activity. Thanks for your patience. More updates soon.
👍1😁1
Showing the 12 most recent of 21 posts we hold for @oraichain_official. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Oraichain Official Announcement” (@oraichain_official), 1,898 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/oraichain_official.
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.