Telegram RegisterThe public register of Telegram
Telegram profile photo for LI.FI Newsfeed

Channel

LI.FI Newsfeed

@lifinews

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

1,754subscribers

-13 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001621605912
TypeChannel
Username@lifinews
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live29 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/lifinews

Growth

1,7541,7671,760.57 August 2026 — 1,767 subscribers7 August 2026 — 1,767 subscribers10 August 2026 — 1,764 subscribers13 August 2026 — 1,758 subscribers16 August 2026 — 1,759 subscribers19 August 2026 — 1,760 subscribers23 August 2026 — 1,754 subscribers26 August 2026 — 1,756 subscribers29 August 2026 — 1,754 subscribers7 August 202629 August 2026
9 measurements spanning 22 days, net -13. 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 1,752–1,769 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 17:361,754-2
26 Aug 2026, 12:041,756+2
23 Aug 2026, 15:571,754-6
19 Aug 2026, 19:481,760+1
16 Aug 2026, 15:441,759+1
13 Aug 2026, 04:361,758-6
10 Aug 2026, 09:301,764-3
7 Aug 2026, 15:201,767no change
7 Aug 2026, 06:161,767first reading

Engagement

20 posts held, back to 13 January 2026the 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 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

102 reactions across 20 posts, in 4 distinct kinds. The most used accounts for 63.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6563.7%
🔥3029.4%
👎43.92%
👍32.94%

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 20 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 102reactions 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 13 January 2026 to 9 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

9 Jul 2026, 14:41 UTC297 views5 reactionsread 7 August 2026

We just shipped the new Partner Portal! It's the one place where you can find all the details releated to your LI.FI integration. On X: https://x.com/lifiprotocol/status/2075227320429003231?s=20 On Linkedin: https://www.linkedin.com/feed/update/urn:li:activity:7480992874134892544

4👍1

Signed Arjun | LI.FI

25 Jun 2026, 12:38 UTC477 views6 reactionsread 7 August 2026

LI.FI’s Token Service just got a major upgrade! Bringing accurate price streams for 2M+ tokens across 40+ chains. Now live for all integration partners, out of the box. On X: https://x.com/lifiprotocol/status/2070122519278018767?s=20 On Linkedin: https://www.linkedin.com/feed/update/urn:li:activity:7475887932671893504

5👍1

Signed Arjun | LI.FI

26 May 2026, 13:24 UTC738 views9 reactionsread 7 August 2026

LI.FI Intents is now live! Enterprise grade infrastructure for onchain finance, enabling: > stablecoin payments > access to real world assets > access to compliant onchain liquidity On X: https://x.com/lifiprotocol/status/2059258196200726687?s=20 On Linkedin: https://www.linkedin.com/feed/update/urn:li:activity:7465023821918613504

🔥62👎1

Signed Arjun | LI.FI

14 Apr 2026, 13:09 UTC970 views5 reactionsread 7 August 2026

LI.FI Earn is now live! on X: https://x.com/lifiprotocol/status/2044037985767960710?s=20 also linkedin: https://www.linkedin.com/feed/update/urn:li:activity:7449803769942347776

🔥3👍1👎1

Signed Arjun | LI.FI

9 Apr 2026, 03:01 UTC909 views4 reactionsread 7 August 2026

We’re organising the DeFi mullet hackathon One week building on everything DeFi and yield - powered by LI.FI If you’re vibe coding, sign up 👇 https://x.com/kenny_io/status/2041875759665406224?s=46

🔥4

Signed Arjun | LI.FI

18 Mar 2026, 15:48 UTC≈1,010 views2 reactionsread 7 August 2026

Why LI.FI Composer? https://x.com/lifiprotocol/status/2034277775860023550?s=46

2

Signed Arjun | LI.FI

10 Mar 2026, 17:41 UTC≈1,020 views12 reactionsread 7 August 2026

Rahul, our new Head of AI, just released a guide on how to vibe-code AI agents that trade crypto 24/7. It walks through how agents can execute swaps and cross-chain trades using the LI.FI MCP. Bookmark this one: https://x.com/RHLSTHRM/status/2031383989488070972?s=20

10👎2

Signed Arjun | LI.FI

9 Mar 2026, 15:15 UTC797 views6 reactionsread 7 August 2026

Introducing LI.​FI’s API for Agentic Commerce, a one-shot integration for building agentic workflows onchain. https://x.com/lifiprotocol/status/2031007975775817890?s=20

6

Signed Arjun | LI.FI

25 Feb 2026, 14:44 UTC844 views6 reactionsread 7 August 2026

Where Will Solver Orderflow Come From in 2026? 3 trends reshaping the solver landscape and how solvers can position to benefit from it. Read more 👇 https://x.com/julimorla/status/2026667514319532141?s=20

6

Signed Arjun | LI.FI

20 Feb 2026, 15:02 UTC818 views4 reactionsread 7 August 2026

Stop Writing Routers 🎙️ How do we make one-click transactions everywhere a reality? Watch our Head of Research and Development, Leo, break down exactly how LI.FI Composer works under the hood. Watch the full workshop 👇 https://youtu.be/qopjLwJXeb0

4

Signed Damian

19 Feb 2026, 15:34 UTC662 views4 reactionsread 7 August 2026

Orchestrating Flow How LI.FI powers multiple crypto apps and reduces friction in transaction flows with orchestration layers. ✍️ Read more: https://x.com/Decentralisedco/status/2024504186751369461?s=20

4

Signed Damian

18 Feb 2026, 13:58 UTC607 views3 reactionsread 7 August 2026

Unbundling finance was DeFi’s innovation. Now it's holding us back. The case for bundling money legos ✍️ Read more: https://x.com/arjunnchand/status/2024110052886630864?s=46

3

Signed Arjun | LI.FI

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

Citation-graph rank — 994,019 of 1,626,935entries 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.

Mentions

Named by 1 registered channel — 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.

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

“LI.FI Newsfeed” (@lifinews), 1,754 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/lifinews.

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.