Channel
@selfchainxyz
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
99,166subscribers
-12,625 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001924858479 |
|---|---|
| Type | Channel |
| Username | @selfchainxyz |
| 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 | 12 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/selfchainxyz |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 56% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 20:39 | 99,166 | -494 |
| 10 Nov 2026, 12:49 | 99,660 | -197 |
| 8 Nov 2026, 20:40 | 99,857 | -250 |
| 7 Nov 2026, 12:15 | 100,107 | -155 |
| 6 Nov 2026, 14:00 | 100,262 | -212 |
| 5 Nov 2026, 15:06 | 100,474 | -129 |
| 4 Nov 2026, 15:44 | 100,603 | -168 |
| 3 Nov 2026, 15:00 | 100,771 | -149 |
| 2 Nov 2026, 14:46 | 100,920 | -99 |
| 1 Nov 2026, 17:34 | 101,019 | -236 |
| 31 Oct 2026, 14:17 | 101,255 | -115 |
| 30 Oct 2026, 16:35 | 101,370 | -230 |
| 29 Oct 2026, 16:06 | 101,600 | -202 |
| 28 Oct 2026, 16:30 | 101,802 | -157 |
| 27 Oct 2026, 15:06 | 101,959 | -238 |
| 26 Oct 2026, 17:10 | 102,197 | -78 |
| 25 Oct 2026, 15:09 | 102,275 | -92 |
| 24 Oct 2026, 13:15 | 102,367 | -131 |
| 23 Oct 2026, 14:31 | 102,498 | -145 |
| 22 Oct 2026, 10:56 | 102,643 | first reading |
20 posts held, back to 28 July 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 199 pages of 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 10 September 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 7 videos 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.
As promised, the code for Self Chain is now fully open-sourced! This is our statement toward a fully community-driven blockchain, built on trust, transparency, and intent-first design We’re just getting started, exciting updates, roadmap milestones, and new plans are coming soon. The future of $SLF is bright, and it’s being built together 👉 https://github.com/selfchainxyz 🔗 https://x.com/selfchainxyz/status/19657…
Keyless wallets are the future. Presently, Web3 still clings to private keys with security loopholes that limit adoption. Explore how Self Chain revolutionises wallet recovery and eliminates seed phrase vulnerabilities with keyless wallets. 📚 https://blog.selfchain.xyz/revolutionizing-web3-wallet-security-recovery/ 🔗 https://x.com/selfchainxyz/status/1963541850691629062
We’re aware of Binance’s notice regarding $SLF. Self Chain today is not the same as before. Under renewed leadership, we’ve removed misaligned actors, secured full control of tech + treasury, and begun the transition to a fully community-run DAO (with Snowball’s Parul Gujral guiding execution). The code has been audited and will be open-sourced Monday. The SLF 2.0 Governance Proposal, outlining non-inflationary t…
📢 Partnership Announcement 📢 We’re excited to welcome Vitamin Ai to the Self Chain ecosystem! Together, we’re enabling ways for users to discover, connect, and collaborate with AI Agents across Web3. 🔗 https://x.com/selfchainxyz/status/1962777525878194341
Over 400 chains exist in crypto, and navigating it can feel like a maze for the average user. From selecting the right network to ensuring dApp compatibility, the transaction-centric approach often adds complexity. Let’s dive into how AI-powered Intent solves this seamlessly. 🔗 https://x.com/selfchainxyz/status/1961094831947534811?s=46
The next era of Web3 demands a complete restructure of how users and applications interact with blockchain. Currently, crypto is still typically designed for the tech-savvy, with little user-intuitiveness in mind. We believe Web3 should feel effortless, as natural and intuitive as using any mainstream application. That is why the core of our mission is simple: remove complexity, unify access, and make Web3 accessib…
📢 Partnership Announcement 📢 We’re excited to welcome Snowball Money into the Self Chain ecosystem. Together, we’re making Web3 as simple as sending a text: one name, one intent, one global identity. 📚 Read more: https://blog.selfchain.xyz/self-chain-forms-a-strategic-partnership-with-snowball/ 🔗 https://x.com/selfchainxyz/status/1960047962765025668
📢 Partnership Announcement 📢 We’re excited to welcome Inference Labs to the Self Chain ecosystem! Together, we’re combining Self Chain’s keyless access with Inference Labs’ AI verification to make agents safer, more reliable, and easier to deploy across Web3. 📚 Read more: https://blog.selfchain.xyz/inference-joins-self-chain-ecosystem/ 🔗 https://x.com/selfchainxyz/status/1957767195041415284
🎙 AMA Announcement 🎙 Join us for an exciting AMA with our ecosystem partner, @Conflux_Network. We’ll be joined by @zoeywangNZ, ecosystem BD of Conflux, as we dive into how we are making Web3 faster, AI-powered, and ready for real-world adoption. 📅 Date: 14th August, 2025 🕒 Time: 2:00 PM UTC 🔔 Link: https://x.com/i/spaces/1zqKVdQpyqdJB Save the date. 🔗 https://x.com/selfchainxyz/status/1955653256295612846
📢 Partnership Announcement 📢 We’re excited to welcome @NebulAi to the Self Chain ecosystem! Together, we’re bringing keyless access and intent-driven execution to Nebulai’s AI agent marketplace, making it easier to connect, deploy agents and earn. 🔗 https://x.com/selfchainxyz/status/1955212774658699501
Self Chain Intents will reframe Web3 access. Soon, users won’t interact manually with web3. One expression will trigger agents, solvers, and protocols across chains, coordinated, & invisible to the user. That’s the web3 we’re building towards. 🔗 https://x.com/selfchainxyz/status/1954932929119002802
📢 Partnership Announcement 📢 We’re excited to welcome Conflux Network to the Self Chain ecosystem! Together we’re bringing keyless access and intent-driven execution to Conflux, enabling seamless onboarding, agent automation, and simpler interactions. 🔗 https://x.com/selfchainxyz/status/1953782881471369623
Showing the 12 most recent of 20 posts we hold for @selfchainxyz. 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.
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.
@selfchainxyz named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 14 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 11 seed channels' Telegram-generated recommendation lists 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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“Self Chain” (@selfchainxyz), 99,166 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/selfchainxyz.
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.