Giveaways & airdrops — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 83% 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 the other topics.
Growth
66 measurements spanning 102 days, net -97,286. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 528,671–655,143 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)
Subscribers
Change
16 Nov 2026, 01:36
543,264
-2,119
12 Nov 2026, 16:46
545,383
-1,251
10 Nov 2026, 15:46
546,634
-898
8 Nov 2026, 23:40
547,532
-912
7 Nov 2026, 15:55
548,444
-432
6 Nov 2026, 14:19
548,876
-4,589
5 Nov 2026, 11:31
553,465
-3,821
4 Nov 2026, 10:26
557,286
-16,964
3 Nov 2026, 11:39
574,250
-558
2 Nov 2026, 14:00
574,808
-638
1 Nov 2026, 10:58
575,446
-499
31 Oct 2026, 13:08
575,945
-495
30 Oct 2026, 15:55
576,440
-750
29 Oct 2026, 17:16
577,190
-682
28 Oct 2026, 16:39
577,872
-576
27 Oct 2026, 15:56
578,448
-748
26 Oct 2026, 16:56
579,196
-668
25 Oct 2026, 13:59
579,864
-915
24 Oct 2026, 15:58
580,779
-933
23 Oct 2026, 17:50
581,712
first reading
Engagement
20 posts held, back to 12 January 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 210 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 20 posts for this entry, the most recent from 10 February 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
303
Videos
2
Links
504
Lifetime counters from Telegram’s own channel header, read 18 November 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.
Reaction mix
11,656 reactions across 20 posts, in 31 distinct kinds. The most used accounts for 19.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
2,269
19.5%
🔥
2,200
18.9%
👍
2,168
18.6%
🎉
2,122
18.2%
😁
1,900
16.3%
👏
342
2.93%
🥰
313
2.69%
🤩
300
2.57%
🤔
5
0.043%
💯
4
0.034%
🤝
4
0.034%
⚡
3
0.026%
💅
3
0.026%
🤡
3
0.026%
👌
2
0.017%
😱
2
0.017%
🤯
2
0.017%
🆒
1
0.009%
🌭
1
0.009%
🍾
1
0.009%
11 further kinds
11
0.094%
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 11,656 reactions 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 12 January 2026 to 10 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.
Telegram Stars
Stars received
1
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @tongiftsnews. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 12 January 2026 to 10 February 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
💬 Do you trust campaigns more when rewards are auditable and real?
Let’s be honest — trust decides whether users participate or walk away.
🔍 Would you join more Web3 campaigns if rewards were:
✔️ On-chain
✔️ Fully transparent
✔️ Provably verifiable
Yes or No — tell us why in the comments 👇
🧠 In Web3, trust isn’t optional — it’s infrastructure.
📈 Transparent rewards don’t just build confidence — they scale communi…
🏛 Project Review | DAO Participation
Low voter turnout is a common DAO problem — governance exists, but users don’t engage.
OpenGifts transformed passive governance into a progressive reward journey:
📖 Read proposals → 🗳 Vote → 🤝 Delegate → 🎁 Earn rewards
📊 Impact delivered:
• Voter participation increased by 180%
• Proposal discussions became deeper and more meaningful
• Delegation activity and long-term involveme…
Why Users Feel OpenGifts Is Different
✨ Users can feel good design.
One thing stands out in OpenGifts campaigns:
Users say they feel comfortable.
Why?
Because we remove:
❌ Cognitive overload
❌ Trust anxiety
No complex wallets upfront.
No chain-switch confusion.
No unclear transactions.
Instead:
📲 Social actions first
🎁 Rewards second
🔗 On-chain later
By the time users touch Web3,
they already trust the flow.
Th…
🔥 Web3 Reality Check — Be Honest
😤 Which type of Web3 campaign do you hate the most?
Let’s call out the bad UX that kills growth 👇
A) Too many complicated steps 🧩
B) Hidden rules and unclear conditions 🕵️
C) Rewards that take forever to arrive ⏳
D) No real value or utility at all 🚫
💬 Vote and share your thoughts
📉 Bad experience = lost users
📈 Better UX = real growth
Your feedback helps shape smarter, fairer Web3…
⚙️ Project Review | L2 Ecosystem Growth
An L2 network rolled out major upgrades — but most users barely noticed.
So OpenGifts turned boring release notes into an interactive journey:
Learn → Test → Claim → Share 🚀
📊 Impact Results
🔥 22,000+ test transactions
👛 9,500+ new wallets created
💬 Developer community engagement surged
🎯 Instead of passive reading, users learned by doing
🎁 Education became rewarding
🔁 Part…
💡 Growth without revenue is just vanity.
Partners often ask:
“Can OpenGifts bring value beyond user numbers?”
The answer is yes — because our tasks reflect real intent.
Instead of empty actions:
❌ Like & leave
❌ Join & disappear
Partners design tasks around real usage:
🎮 Try a feature
🧪 Test a product
🗳 Participate or vote
🎁 Rewards are small but meaningful
⚡️ Friction stays low
🔁 Behavior becomes repeatable
Ove…
🧠 Memory Test — What makes a project unforgettable?
Not all rewards create memories.
Some just disappear.
Others stick emotionally — and keep users coming back 💭💖
Which reward makes a project truly memorable for you?
A) Your first on-chain asset ⛓️
B) An exclusive badge 🏅
C) A small but instant reward ⚡️
D) Community-only perks 👥
Vote + tell us why 👇
Because emotion drives retention — not just incentives 🚀
🧧Join…
Project Review | SocialFi Engagement
A SocialFi app struggled with inflated metrics caused by task farming and low-quality interactions. Clicks were high, but trust was missing.
🎁 OpenGifts redesigned the reward logic around real social proof:
Post → Reply → Get Verified → Unlock
📊 Results:
🤖 Bot activity ↓ 41%
💬 Genuine conversations ↑ 3×
🌱 Creator retention improved
💡 Key insight:
SocialFi grows through trust, …
📲✨ Where Should Web3 Rewards Live? ✨📲
Rewards shouldn’t feel forced.
They should feel natural — right where users already are 👀💡
So we’re curious 👇
Where do you prefer to claim Web3 rewards most naturally?
🐦 X
💬 Telegram
🎮 In-game
🧩 Web mini-app
The best rewards don’t interrupt the experience.
They blend into it 🎁✨
Reply with your choice below 👇
Because rewards should feel native, not bolted on 🚀
🧧Join us to le…
🚀 Let’s be honest.
Web3 isn’t short on tech or ideas —
it struggles with sustainable user growth.
Most projects still depend on:
🪂 Short-term airdrops
📉 One-off campaigns
🗯 Noise without retention
OpenGifts was built to break this cycle.
We don’t chase clicks. We build distribution:
🎁 Task-based social gifting
🎯 Rewards for real behavior
🔗 Turning Web2 actions into Web3 ownership
User journey:
Follow → Join → Int…
🌐🚀 Growth Doesn’t Live on Just One Platform 🚀🌐
Growth isn’t about choosing a single channel —
it’s about meeting users wherever they are 👥✨
What if engagement could flow freely across platforms? 🤔
Across Telegram, X, Discord — and beyond 🔗
At OpenGifts, we break down platform walls 🧱❌
By unifying
🎁 gifting
🎉 rewards
🔍 verification
into one seamless experience ⚙️✨
Because real growth doesn’t happen in isolation.
I…
🎮📚 GameFi | Turning Trial Users into On-Chain Players
🎯 Project Review: GameFi Onboarding
A GameFi studio faced a common problem:
Web2 gamers loved the gameplay —
but dropped off before wallet setup 😵💨
To fix this, OpenGifts redesigned onboarding around incentives 🎁
Instead of forcing wallets first, we flipped the flow:
▶️ Play → Win → Claim → Bind Wallet
📊 The impact:
👥 11,600 players successfully completed wa…
🔥140❤135😁132🎉117👍113🥰4🏆1🤔1
Showing the 12 most recent of 20 posts we hold for @tongiftsnews. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Forward network
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.
Mentions
Named by 10 registered channels — 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.
Domains linked from posts
2 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 16 November 2026 — this
entry's latest reading, not the date you are reading this.
“OpenGifts News” (@tongiftsnews), 543,264 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/tongiftsnews.
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.