Channel
@covalent_news
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
7subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001588562060 |
|---|---|
| Type | Channel |
| Username | @covalent_news |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/covalent_news |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 17:01 | 7 | no change |
| 7 Aug 2026, 02:02 | 7 | first reading |
20 posts held, back to 10 August 2023 — the 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.
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 14 August 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
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.
🔁 RT @TABASCOweb3: In June, as I was building out our @ChainstackHQ x @Covalent_HQ SDK, a tweet from @thatguyintech inspired me 📊 This tweet was asking about the existence of an API to determine if an address has ever deployed a contract 📒 In 4 minutes, let's leverage the SDK to do just that 👇 https://t.co/nIz2zh8wJY https://t.co/calxUiQnmJ
🐦 @Covalent_HQ: 7/ With the testnet now concluded the CQT Network team is preparing for mainnet on August 15th. 🎉 Join us in celebrating this remarkable milestone towards the CQT Network's mainnet launch!
🐦 @Covalent_HQ: 6/ Applause for our outstanding Refiner Incentivised Testnet winners! 🏆 These adept individuals embody the resilience and excellence of the CQT Network. Their expertise and dedication set them apart as key players in our journey.
🐦 @Covalent_HQ: 5/ Participant feedback was invaluable! One praised the seamless operation; another hailed the efficiency of the installation process and data transmission. Constructive feedback provided a holistic view, reinforcing our user-friendly approach and outlining areas for growth. https://t.co/hkKVJ0wWrm
🐦 @Covalent_HQ: 4/ Our stress testing uncovered some bottlenecks: 1️⃣ Gas consumption surged with accelerated block result production rates. 2️⃣ The Filecoin network struggled to keep pace. Such findings are especially valuable as we are currently exploring settlement mechanisms.
🐦 @Covalent_HQ: 3/ 📈 We systematically pushed the network's limits, progressively upping the ante to understand its capabilities. On the final day, the network produced ~ 2/3 block results in approximately every minute, with proofs being submitted each. https://t.co/CFW7NslEMJ
🐦 @Covalent_HQ: 2/ The numbers speak volumes: - 27 participants - 274,833 proofs submitted - 98.8% average uptime Each day, all participants were effortlessly pulling Ethereum data and transforming such into enriched block results depending on their needs.
🐦 @Covalent_HQ: 1/ 🎉 Exciting news for the CQT Network! From July 12th to July 26th, our two-week Refiner Incentivised Testnet was a resounding success! The goals were to: - test network throughput, - gauge user experience - and select new operators. We achieved all this and more! 👇 https://t.co/zjjvbbfKEj
🐦 @Covalent_HQ: @leichain 3/ ✅ Make sure to sign up for an API key if you'd like to follow along with @leichain as she goes over how each endpoint works: https://t.co/zoSpx0r5nn https://t.co/l9E9AtQkRI
🐦 @Covalent_HQ: @leichain 2/ 💎What makes Covalent unique? The standardized and formatted data across the 100+ chains we've indexed and human-readable transaction fields to classify events that add liquidity or when selling an #NFT.
🐦 @Covalent_HQ: 1/ 👩💻 Join @leichain on Hidden Gems as she showcases how tax companies can use the Covalent #UnifiedAPI and the following transaction endpoints: - Wallet activity - Token balances - Transactions for an address - #ERC20 Token transfers for an address https://t.co/uNMw11aBg3
🔁 RT @impossiblefi: 1/ Axie Infinity Growth Analysis Thread 🎮 This thread explores the remarkable growth in various aspects of @AxieInfinity and @Ronin_Network From new user influx to daily active users increases, dive into the numbers that define this success via data sourced from @Covalent_HQ https://t.co/rpPYVaCw4t
Showing the 12 most recent of 20 posts we hold for @covalent_news. 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.
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.
@covalent_news named 4 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Covalent twitter news” (@covalent_news), 7 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/covalent_news.
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.