Telegram RegisterThe public register of Telegram

Channel

@Figment_io

@Figment_io

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

8subscribers

+0 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001597090674
TypeChannel
Username@Figment_io
Descriptionnfrastructure / Research / Application layer solutions for Web 3. Institutional Staking on 50+ PoS networks. 🚀🌎
Created18 February 2022measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/Figment_io

Growth

812 Aug 2026, 04:01 — 8 subscribers12 Aug 2026, 15:47 — 8 subscribers12 Aug 2026, 04:0112 Aug 2026, 15:47
2 measurements taken within a single day. 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 7–9 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 15:478no change
12 Aug 2026, 04:018first reading

Engagement

12 posts held, back to 18 February 2022the 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 12 posts for this entry, the most recent from 4 May 2022. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
11

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. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

4 May 2022, 21:51 UTC182 viewsread 12 August 2026

📺 We're live! Tune in here 👉 https://t.co/C4yiAQyWiP

4 May 2022, 21:51 UTC182 viewsread 12 August 2026

The evolution of @avalancheavax🔺 continues with an expected mass migration to the Avalanche mainnet 🌐 ⛓️ Read our take on the interoperability of @avalancheavax 🔺👇 https://t.co/rY2DcJyAkI https://t.co/tlzR4UWfs9

27 Apr 2022, 16:52 UTC157 viewsread 12 August 2026

👀 @flow_blockchain governance tool is called CAST This governance tool is currently being used to vote on the first proposal on the network, which marks the initial step from a centralized off-chain governance model into a more decentralized system 🤝 https://t.co/F30WiaY7pF https://t.co/rNpBcNwMrr

25 Apr 2022, 17:32 UTC75 viewsread 12 August 2026

⏰ Tune in to our upcoming AMA with @archwayHQ this Friday at 12:30pm EST🎙️ Set your reminder and reply with your questions below👇🔔 https://t.co/oVLydhNIUN

25 Apr 2022, 16:46 UTC66 viewsread 12 August 2026

The future is NEAR 🙌 🎙️ We'll be chatting with experts from @Finoa_Banking & @NEARProtocol to discuss opportunities in the NEAR ecosystem and how institutional investors can safely generate yield staking 📆 RSVP now 👉 https://t.co/Mbhwe0Q08M https://t.co/xPCoLDuH5n

15 Apr 2022, 07:57 UTC50 viewsread 12 August 2026

Ready to superfluid stake $OSMO and earn rewards? 🧪 Follow along our step-by-step video guide from @CalicoKittencat 🔮👇 https://t.co/83hKW1jnDT

14 Apr 2022, 07:18 UTC40 viewsread 12 August 2026

🌐 Building universal connectivity for Web 3 - @axelarcore is connecting multiple blockchains through wrapped assets 🔗 💻 Follow our guide, Stake your $AXL tokens now 👇 https://t.co/DaN6gqPCWr https://t.co/2sRYC0AGiC

14 Apr 2022, 07:15 UTC32 viewsread 12 August 2026

✈️ 🇫🇷 Bonjour, we're in Paris for #PBWS2022! Join @menzel_clayton and others, as they discuss blockchain technology and its usage in maintaining privacy in Web3 🔒 📆 04/13/22 @ 2:40PM CEST 👉 https://t.co/klADb1fmNO https://t.co/vwbrV7SBXu

14 Apr 2022, 07:14 UTC24 viewsread 12 August 2026

Ready to stake your $MATIC? 📈 Token holders can now stake their $MATIC on @ethereum with @MetaMask 🦊 Follow along our video guide below from @CalicoKittencat 👇 https://t.co/hvCTCnF1LA

18 Feb 2022, 15:08 UTC49 viewsread 12 August 2026

Privacy issues are an ever growing concern in tech, and @nymproject is at the forefront of the fight 💻 @nymproject provides developers and users full-stack privacy 🔐 Learn more about @nymproject below 👇 https://t.co/nYlfBEEpuu

18 Feb 2022, 15:06 UTC39 viewsread 12 August 2026

Taxation of PoS networks raises a lot of questions 🙋 This article from @VelvetMilkman provides a general overview on PoS networks, as well as outlining the various challenges taxpayers face 👇 https://t.co/UGiUsiM5Z7

Showing the 12 most recent of 12 posts we hold for @Figment_io. 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 — 1,140,053 of 1,176,251entries 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.

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.

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

“@Figment_io” (@Figment_io), 8 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Figment_io.

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.