Channel
@multimesh
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
96subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002473278475 |
|---|---|
| Type | Channel |
| Username | @multimesh |
| Created | Between 1 September 2024 and 16 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/multimesh |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 12:02 | 96 | no change |
| 7 Aug 2026, 04:03 | 96 | first reading |
20 posts held, back to 16 March 2025 — 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 29 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 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.
25 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 80.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 20 | 80.0% | |
| 👍 | 4 | 16.0% | |
| 🔥 | 1 | 4.00% |
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 9 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 25reactions 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 16 March 2025 to 29 June 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.
Partnership announcement 🚀 MultiMesh is partnering with @KiraPayOfficial to explore smoother cross-chain asset movement, payments, and settlement workflows. MultiMesh helps users find efficient cross-chain swap routes across bridges and DEXs. KIRAPAY brings strong payment infrastructure for wallets, tokens, and multi-chain settlement. This is another step toward making cross-chain transactions simpler, faster, an…
❤1
MultiMesh beta now has Telegram alerts. Users can link their wallet once and get notified when: - a limit order fills - a DCA buy is due - it’s time to return for a recurring trading action This is a big step for our retention layer. Most wallet-only DeFi apps have no simple way to bring users back after they leave. MultiMesh is not just building one-off cross-chain swaps. We’re building a cross-chain trading w…
MultiMesh beta just got a major trust upgrade. Before signing a swap, users now see a clean pre-sign review showing: * what they pay * what they receive * source + destination chain * estimated fees * slippage * estimated time * recipient address * explorer link after transaction Cross-chain trading should feel clear before users commit. Looking for active DeFi users to test one small swap and give honest feedbac…
👍1
Welcome to MultiMesh Beta. MultiMesh helps active DeFi users swap, refuel, DCA, set limit orders, and consolidate assets across chains from one interface. We’re looking for early beta testers. Your mission: test one swap, report your experience, and suggest one improvement. Early testers get Beta Mesher recognition and will help shape the product. Just early builder energy.
👍1
Cross-chain swaps shouldn’t feel painful. https://x.com/i/status/2057795345661264113
🚀Cross-chain traders, this one’s for you. We’re opening MultiMesh beta to early pioneers. Early users get: 🏆 Early Contributor role 🎟 Priority access to future partner whitelists & ecosystem campaigns 📈 Live leaderboard recognition 🛠 Direct feedback access to founders How to join: Complete your first swap on MultiMesh Climb the leaderboard Share feedback Start here: themultimesh.com https://x.com/i/status/205772120…
Introducing Meshpoints our early user rewards system. Every swap earns you XP. Cross-chain swaps earn bonus XP. Your streak multiplies everything. The earlier you start, the more your history matters https://x.com/i/status/2054193266162090491
On a $5,000 cross-chain swap: 0.1% Slippage= $5 lost 0.5% Slippage= $25 lost 1.5% Slippage= $75 lost MultiMesh shows you the exact Slippage before you confirm. No surprises. No hidden costs. This is what "best route" actually means. https://x.com/i/status/2052811687590309980
❤1
We compared 5 cross-chain routes for ETH -> USDC across chains. Most people overpay by 15-30% because they pick the first bridge they find. Here's what the data actually shows🧵 https://x.com/i/status/2052315378215223561
Cross-chain swapping is still broken in 2026. You want to move ETH on Arbitrum → USDC on Base? That's 3 tabs. 4 steps. 10 minutes. And you still get wrecked on slippage. We built MultiMesh to fix this. Here's what it does 🧵 https://x.com/i/status/2051261895944876435
Cross-chain Swapping is still broken in 2026, you want to move ETH on Arbitrum->USDC on Base? That's 3 tabs. 4 steps. 10 mins. And you still might get wrecked on slippage. We built Multimesh to fix that. Here's what it does. A Thread🧵 https://x.com/i/status/2046565222819795247
🚀 New Partner on DAOaaS: MultiMesh is Live! We’re excited to welcome MultiMesh — the “Deploy Anywhere” protocol backed by TorusChain and supporting Arbitrum, Aptos, and more. 🔑 One key, every chain. 🚀 Deploy once, launch everywhere. 🌐 Interoperability meets execution — powered by DAOaaS. 👉 Join the MultiMesh DAO community: https://daoaas.io/communityDetail?communityId=57
Showing the 12 most recent of 20 posts we hold for @multimesh. 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 — 282,435 of 1,350,102entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Multi-Mesh Official” (@multimesh), 96 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/multimesh.
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.