Channel
@resolvlabs
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,505subscribers
-28 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001967922737 |
|---|---|
| Type | Channel |
| Username | @resolvlabs |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/resolvlabs |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 23:48 | 1,505 | -9 |
| 10 Aug 2026, 16:51 | 1,514 | -16 |
| 7 Aug 2026, 11:40 | 1,530 | -3 |
| 7 Aug 2026, 00:46 | 1,533 | first reading |
20 posts held, back to 26 February 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 2 pagesof 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 9 June 2026. An engagement rate over an empty window would be a number about nothing.
244 reactions across 19 posts, in 13 distinct kinds. The most used accounts for 32.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 80 | 32.8% | |
| ❤ | 79 | 32.4% | |
| 👍 | 47 | 19.3% | |
| 🤣 | 11 | 4.51% | |
| 🎉 | 8 | 3.28% | |
| 👏 | 7 | 2.87% | |
| 🤔 | 5 | 2.05% | |
| 🥴 | 2 | 0.82% | |
| 🍓 | 1 | 0.41% | |
| 🏆 | 1 | 0.41% | |
| 😁 | 1 | 0.41% | |
| 🙉 | 1 | 0.41% | |
| 🤝 | 1 | 0.41% |
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 19 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 244reactions 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 26 February 2026 to 9 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.
The recovery portal is open for Stage 2 Eligible categories: • USR / wstUSR acquired post-incident 1 USR : 0.5 USDC • LP positions (post-incident portion) 1 USR : 0.5 USDC + RESOLV allocation bringing total recovery to 95% at reference RESOLV price • RLP holders (not leveraged) 1 RLP : 0.71 USDC + 2.71 RESOLV per RLP (60%+ total recovery at reference RESOLV price) → app.resolv.xyz/recovery Recovery portal is ope…
❤5👏2🏆1
Important Snapshot Notice On June 3, 23:59 UTC, a snapshot of all post-hack USR positions and RLP will be taken to enable Stage 2 recovery through the Resolv recovery portal. This snapshot will determine compensation for affected positions, including both the cash recovery and RESOLV token allocation. Stage 2 recovery will launch separately — details to follow.
❤7🔥5
In the next 24 hours, there are expected movements of funds across wallets associated with Resolv Labs and Resolv Foundation. These operational transfers are conducted as a part of preparations for upcoming recovery processes and additional security/infrastructure measures (including planned wallet rotation).
👍5🔥5
Resolv Foundation has published an update on the path forward, covering the complete recovery framework. Inside: • Recovery terms for all affected user categories • Introduction of Vault Street — a new business line focused on tokenized RWA for institutional allocators • RESOLV staking resumption and rewards → Read the full article
🔥14👍3👏2🍓1🤝1
Over the past weeks, Resolv has been actively working with affected counterparties and ecosystem participants to move the recovery process forward across both pre-incident and post-incident user groups. As part of this process, we have reached a shared understanding with Fluid on the path forward, as one of the key counterparties impacted by the post-incident dynamics. This reflects constructive dialogue and close c…
❤15🔥4🎉3
Resolv Foundation Q1 2026 Report is out. Q1 was a challenging period for Resolv. Since late March, main focus has been on recovery and ensuring long-term sustainability. Foundation is committed to supporting the token as part of the broader system going forward: • the core functionality of RESOLV token remains unchanged post-relaunch; • we are actively working with major exchanges to support RESOLV continued availa…
👍7🔥4
Fedor, co-founder of Resolv, just shared an update reflecting ongoing work with external partners and continued progress on the investigation. 🔗Check X post
❤3👏2
Ivan, co-founder of Resolv, has shared a new video update on the current state of the recovery plan and what’s driving the timeline. 🔗Watch the full video on X
❤13👏1😁1🙉1
Resolv Postmortem — March 22, 2026 Incident The report covers the multi-stage attack originating outside Resolv’s perimeter, unauthorized access to signing infrastructure, and the resulting mint of 80M USR, along with detection, containment, and remediation actions across infrastructure and on-chain systems. The investigation is ongoing and is being conducted with support from external security firms including Hype…
👍17
Ivan, co-founder of Resolv, has shared an update on the protocol security incident and recovery process. Some of the questions covered: → Why were whitelisted USR users redeemed first? Verified wallets allowed the team to act within 24 hours manually to limit further impact on the broader market. 98% of those redemptions are complete. → What can non-whitelisted pre-exploit USR holders expect? The same 1:1 commitme…
❤2👍2
Update on illicitly minted USR supply reduction Of the total 80M USR illicitly minted during the exploit on March 22, 2026, approx. 46M (~57%) has been permanently removed from circulation through a combination of burns and blacklisting. As a result, no illicitly minted assets remain on exploiter-associated addresses that could be further transferred or converted. Multiple steps have been taken to reduce the amoun…
🔥12🥴2
Update on Redemption Process Over the past 2 days, $77M+ has been redeemed for allowlisted wallets with pre-exploit USR, representing 90%+ of this group and marking strong progress in phase one of recovery. Next: • Redemption process for this group is actively being completed • Work on subsequent phases, covering remaining user groups
❤11🤔5
Showing the 12 most recent of 20 posts we hold for @resolvlabs. 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 — 140,128 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.
Named by 5 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Resolv Labs” (@resolvlabs), 1,505 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/resolvlabs.
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.