Telegram RegisterThe public register of Telegram

Channel

Bitcoin.ℏ (BTC.ℏ)

@BitcoinHT

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

161subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002343652654
TypeChannel
Username@BitcoinHT
DescriptionBitcoin.ℏ (BTC.ℏ) is a cryptocurrency designed to solve one of the crypto industry's biggest issues: the excessive energy consumption of traditional Bitcoin. Bitcoin.ℏ retains the advantages of Bitcoin's original framework while eliminating the downsides,
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/BitcoinHT

Growth

1617 Aug 2026, 14:26 — 161 subscribers8 Aug 2026, 17:01 — 161 subscribers7 Aug 2026, 14:268 Aug 2026, 17:01
2 measurements spanning 1 day. 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 160–162 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 17:01161no change
7 Aug 2026, 14:26161first reading

Engagement

20 posts held, back to 2 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
45.3%
avg views ÷ 161 subscribers
Avg views / post
73.0
1 post measured
Reaction rate
1.37%
reactions ÷ views · ER floor
Posts in window
1
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 July 2026
Posts held20 (2 March 202615 July 2026)
Views total73
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 17:01 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
178
Videos
14
Links
319

Lifetime counters from Telegram’s own channel header, read 8 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.

Video runtime
46s
Average length
46s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

11 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 36.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍436.4%
327.3%
👏327.3%
🔥19.09%

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 8 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 11reactions 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 2 March 2026 to 15 July 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.

Recent posts

15 Jul 2026, 14:45 UTC73 views1 reactionsread 8 August 2026
Photo

We're proud to announce that Bitcoin HT, LLC is now a member of the MiCA Crypto Alliance. This marks another step in our commitment to transparency, responsible innovation, and regulatory engagement as the BTC.ℏ ecosystem continues to grow. Read our announcement: https://bitcoin.org.ht/news/Bitcoin.h-Joins-the-MiCA-Crypto-Alliance.htm Read the MiCA Crypto Alliance announcement: https://www.micacryptoalliance.com/n

👏1

7 Jul 2026, 13:30 UTC57 views2 reactionsread 8 August 2026
Photo

Big milestone for BTC.ℏ. Our MiCA-compliant white paper is now published, providing a detailed look at the project, token design, governance, sustainability, and risk disclosures. Built for fast settlement, low costs, and real-world utility, BTC.ℏ continues moving toward broader global adoption. Read the MICA white paper: https://bitcoin.org.ht/mica-white-paper/

👏2

12 Jun 2026, 19:01 UTC97 views2 reactionsread 8 August 2026
Video

Disclosure Notice The alpha version of the inkjug is officially complete and now in the hands of our private alpha testers. The focus of the alpha build is simple: prove the BTC.ℏ wallet works, remove friction, and make BTC.ℏ payments easy enough for grandma to use. Beta is next and work has already started. We are excited to start building tools for the planned Inkjug "Tool Store". The sneak peak video shows two

👍2

19 May 2026, 14:24 UTC115 views2 reactionsread 8 August 2026
Photo

🚨 URGENT REMINDER 🚨 All BTC.ℏ[base], BTC.ℏ[bsc], BTC.ℏ[avax], BTC.ℏ[arb], BTC.ℏ[eth] and BTC.ℏ[0x] must be un-bridged (un-ported) back to BTC.ℏ[hts] by May 31st at 12:00 UTC $BTC.ℏ [hts] on the @hedera network is unaffected. The token issuer ( Bitcoin HT, LLC ) is NOT responsible for the redemption of wrapped Hashport assets. Redemption is handled exclusively by @HashportNetwork, and the deadline to act is May 31

👍2

15 May 2026, 15:23 UTC100 views2 reactionsread 8 August 2026
Photo

Just a quick update on the progress of InkJug. We’ve made strong progress on the InkJug wallet and have successfully tested wallet creation, sending, and receiving. We are now focused on implementing and refining the best verification methods for account sign-up. Also, the new inkjug logo has officially been finalized and will be the logo we take to market. 🚀

2

7 Apr 2026, 13:07 UTC147 viewsread 8 August 2026
Photo

💡Bonzo - Hedera Ecosystem Spotlight #527 Bonzo Finance is an open source, non-custodial lending & borrowing protocol built on the public Hedera network. 📖 Learn more: https://bonzo.finance 🌟Explore $HBAR ecosystem: https://hashledger.net Sponsored by Bitcoin.ℏ: https://bitcoin.org.ht

3 Apr 2026, 06:33 UTC124 viewsread 8 August 2026
Photo

💡AgentBrewHouse - Hedera Ecosystem Spotlight #526 AgentBrewHouse is a decentralized marketplace built on the Hedera network that enables autonomous AI agents to discover, collaborate, and transact directly using HBAR or USDC. 📖 Learn more: https://agentbrewhouse.io 🌟Explore $HBAR ecosystem: https://hashledger.net Sponsored by Bitcoin.ℏ: https://bitcoin.org.ht

2 Apr 2026, 18:55 UTC82 viewsread 8 August 2026

IMPORTANT 🚨 ACTION REQUIRED Hashport is shutting down. All BTC.ℏ[base], BTC.ℏ[bsc], BTC.ℏ[avax], BTC.ℏ[arb], BTC.ℏ[eth] and BTC.ℏ[0x] must be un-bridged (un-ported) back to BTC.ℏ[hts] by May 31st at 12:00 UTC. BTC.ℏ assets not bridged back to the hedera network by May 31st will be unrecoverable. Convert to BTC.ℏ[hts] here: https://app.hashport.network You can read more about Hashport wind down here: https://hash

31 Mar 2026, 07:31 UTC69 viewsread 8 August 2026
Photo

💡Honeytrail - Hedera Ecosystem Spotlight #525 Honeytrail empowers beekeepers and industry professionals worldwide with a low-cost, low-barrier, immutable and transparent traceability system and is built on @Hedera . 📖 Learn more: https://honeytrail.io 🌟Explore $HBAR ecosystem: https://hashledger.net Sponsored by Bitcoin.ℏ: https://bitcoin.org.ht

27 Mar 2026, 22:48 UTC61 viewsread 8 August 2026
Photo

💡Hashly - Hedera Ecosystem Spotlight #524 Hashly aims to be a community-oriented discovery and event platform for the Hedera ecosystem. 📖 Learn more: https://hash-ly.com 🌟Explore $HBAR ecosystem: https://hashledger.net Sponsored by Bitcoin.ℏ: https://bitcoin.org.ht

24 Mar 2026, 13:47 UTC62 viewsread 8 August 2026
Photo

💡Candy Machine - Hedera Ecosystem Spotlight #523 The Candy Machine DApp is a meme token with NFT's and is built on Hedera. 📖 Learn more: https://candyhbar.com 🌟Explore $HBAR ecosystem: https://hashledger.net Sponsored by Bitcoin.ℏ: https://bitcoin.org.ht

19 Mar 2026, 14:20 UTC67 viewsread 8 August 2026
Photo

💡ClimateGPT - Hedera Ecosystem Spotlight #522 ClimateGPT - an ensemble of task-specific AI models bringing trust to climate data with native Hedera integration to ensure the highest standards of data integrity and sustainability by providing an immutable and distributed record of the workflows for ClimateGPT. 📖 Learn more: https://eci.io/climategpt 🌟Explore $HBAR ecosystem: https://hashledger.net Sponsored by Bitc

Showing the 12 most recent of 20 posts we hold for @BitcoinHT. 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.

Mentions

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.

Cite this entry

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“Bitcoin.ℏ (BTC.ℏ)” (@BitcoinHT), 161 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/BitcoinHT.

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.