Channel
@CrossCurveMetaLayer
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
71,157subscribers
-732 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001527072198 |
|---|---|
| Type | Channel |
| Username | @CrossCurveMetaLayer |
| Description | Ready-to-integrate infrastructure providing access to deep DeFi liquidity and leading interoperability protocols — enabling automated on-chain operations beyond EVM with gasless execution and advanced cross-chain routing. |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/CrossCurveMetaLayer |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 19:44 | 71,157 | -108 |
| 13 Aug 2026, 08:36 | 71,265 | -73 |
| 12 Aug 2026, 05:13 | 71,338 | -113 |
| 11 Aug 2026, 08:18 | 71,451 | -107 |
| 10 Aug 2026, 08:33 | 71,558 | -84 |
| 9 Aug 2026, 08:51 | 71,642 | -50 |
| 8 Aug 2026, 11:42 | 71,692 | -63 |
| 7 Aug 2026, 14:35 | 71,755 | -97 |
| 6 Aug 2026, 11:02 | 71,852 | -37 |
| 6 Aug 2026, 01:35 | 71,889 | no change |
| 6 Aug 2026, 00:48 | 71,889 | first reading |
14 posts held, back to 15 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 21 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 14 (15 April 2026 – 11 August 2026) |
| Views total | 2,262 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Aug 2026, 21:23 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.
Lifetime counters from Telegram’s own channel header, read 14 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.
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.
✨ After six incredible years, CrossCurve is coming to an end. What started in 2020 as an idea around cross-chain infrastructure became a journey shared with hundreds of thousands of people. We built, learned, failed, won, and pushed the boundaries of what was possible. Today, we are closing this chapter. Thank you to our users, investors, partners, developers, liquidity providers, DAO participants, and community f…
⚠️ Reminder: Withdraw Your Funds from the Old CrossCurve Token Bridge Dear users, As part of the CrossCurve bridge recovery process, withdrawal functionality has been restored for several additional networks. Funds still remain in the old bridge contracts across multiple networks, including Blast, Taiko, Arbitrum, Ethereum, Optimism, Avalanche, BNB Chain, Polygon, Base, Gnosis, Linea, Fraxtal, Celo, and Sonic. If…
✨ CrossCurve MetaLayer is scaling beyond EVM Solana is now integrated into CrossCurve as part of its cross-chain routing layer enabling seamless swaps across one of the most active non-EVM ecosystems in Web3. This is a structural evolution: from EVM-only routing to a truly multi-ecosystem infrastructure built for scale, liquidity access, and execution efficiency. What’s now available: 🔘 Cross-chain swaps across E…
https://x.com/i/status/2066551305628197060
🇬🇧 CrossCurve News pinned a photo
⚠️ CrossCurve Token Bridge Recovery - Withdrawal Mode Activated Dear users, As part of the recovery process for the CrossCurve bridge infrastructure affected by the exploit, we have temporarily re-enabled withdrawals from the old bridge. If you still have funds remaining in the bridge, they must be withdrawn within one week from the date of this announcement. At the moment, more than $200,000 in user funds still …
🟢 CrossCurve MetaLayer Aggregator Restored Following a series of technical works and infrastructure upgrades carried out in preparation for upcoming releases, we’re pleased to announce that the CrossCurve MetaLayer aggregator is now fully available to users again. This is only the beginning of the next major phase of the CrossCurve ecosystem. Ahead are the release of the upgraded Token Bridge with OFT support, the …
🇹🇷 CrossCurve at BlockchainX Istanbul! On May 16, our CEO Boris Povar will speak at BlockchainX Istanbul — one of the крупнейших Web3 events in the region, bringing together leading blockchain projects, infrastructure teams, investors, and builders from around the world. Boris will share his expert perspective on the market — from the current state of cross-chain DeFi to the key infrastructure challenges shaping th…
🛡 CrossCurve Successfully Completes Consensus Bridge Re-Audit by MixBytes As part of strengthening CrossCurve’s security, the Consensus Bridge has successfully undergone a re-audit following the previous attack. The review focused on validating the implemented fixes and further enhancing the system’s resilience and reliability. This audit completes our planned audit cycle and sets the stage for the upcoming release…
📝 April 2026: CrossCurve Recap April was a month of focused groundwork for CrossCurve — combining strong presence at key industry events with deep work on infrastructure reliability. ✔️ Conferences Our CEO, Boris Povar, attended Paris Blockchain Week — a week filled with high-density meetings with leading players across the ecosystem, including Bitstamp, Robinhood, Liquity, Enigma, FrankenCoin, Webacy, Chainlabs, …
🚧 Scheduled Maintenance As part of the upcoming release and deployment of the upgraded infrastructure — including the Token Bridge with OFT support and the Consensus Bridge — the CrossCurve MetaLayer aggregator will be temporarily paused in the near term. During this period, swaps will be unavailable. We will notify you as soon as the system is restored. Thank you for your understanding — stay tuned for updates.
🔍 Recent CrossCurve Updates You Might Have Missed As we approach the final stage of auditing and the upcoming release of the upgraded Consensus Bridge and Token Bridge with LayerZero OFT support, here’s where things stand Recently, we completed a series of independent audits of key system components conducted by Hashlock, SmartState, and Hexens. Each audit included an in-depth review of the architecture, smart cont…
Showing the 12 most recent of 14 posts we hold for @CrossCurveMetaLayer. 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.
Citation-graph rank — 72,121 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 3 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.
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 1 seed channel's Telegram-generated recommendation list 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“🇬🇧 CrossCurve News” (@CrossCurveMetaLayer), 71,157 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/CrossCurveMetaLayer.
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.