Telegram RegisterThe public register of Telegram

Channel

Ꭱꮻꮶꮻ Ꮯꮖꭲꭺꭰꭼꮮ

@RokoCitadel

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

175subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001896146779
TypeChannel
Username@RokoCitadel
CreatedBetween 1 October 2022 and 9 August 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/RokoCitadel

Growth

1758 Aug 2026, 00:02 — 175 subscribers8 Aug 2026, 14:02 — 175 subscribers8 Aug 2026, 00:028 Aug 2026, 14:02
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 174–176 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 14:02175no change
8 Aug 2026, 00:02175first reading

Engagement

20 posts held, back to 9 August 2023the 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 26 November 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
88
Videos
15
Links
100

Lifetime counters from Telegram’s own channel header, read 8 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.

Video runtime
6s
Average length
6s

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.

Reaction mix

76 reactions across 14 posts, in 6 distinct kinds. The most used accounts for 35.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2735.5%
2330.3%
👍1925.0%
🤝33.95%
🤯33.95%
👀11.32%

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 15 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 76reactions 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 9 August 2023 to 26 November 2023, 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

26 Nov 2023, 00:10 UTC≈1,070 views4 reactionsread 8 August 2026
Photo

Photo, posted without a caption

🔥31

3 Nov 2023, 17:58 UTC973 views4 reactionsread 8 August 2026

Roko Github is in the works, repos may be private initially until mvp launch as far as I know. A few of the devs are settling back into routine after travels to Lisbon for Urbit conference. Next week things will pick up speed. @LordRoko has been holding down the fort slaying autogen and staying on top of all the new open-source releases and synergies with autogen. Will get caught up to speed pretty quickly there 🫡

👍3👀1

22 Oct 2023, 21:30 UTC942 views5 reactionsread 8 August 2026
Voice message

Voice message, posted without a caption

🔥5

19 Sept 2023, 15:11 UTC813 views5 reactionsread 8 August 2026

We just added a 3rd core member to the Roko Multi-sig safe. We've had the pleasure of working with individual for a number of years now, they are playing a key role in development of Roko and hold the interest of tech and community at heart. New Safe Signer Address: 0x560F45677c2Ddd24108BF23B950f1651E437194A Existing Safe Addresses: 0x6cdDA44E3B32bf1F2Ef0dbA7AF81A49a5558184f (rokoguardian.eth) 0x71c5957B5998d9ff8E

🤝31👍1

18 Aug 2023, 18:30 UTC702 views14 reactionsread 8 August 2026

Users who want to run their own nodes will be using PKI using hardware wallets. Right now the hardware we are putting together will have Zymbit hsms which we just recently acquired via proposal funding for testing. We are working on a way to distribute cloud access to nodes, and also designing a consumer ready box that you can run locally at home. The hardware boxes should be starting to get assembled starting some

👍13🔥1

18 Aug 2023, 15:18 UTC590 views8 reactionsread 8 August 2026

Hey heads up, we clawed back 3 billion tokens from one of our core contributors as an internal consensus that the contributor received a disproportionate amount of tokens for their current role. Due the crazy amount of growth we've received since payment back in May, we are to making sure were always holding our team to a standard and putting the growth of our network first. On that note we also are looking to bring

7🔥1

17 Aug 2023, 18:15 UTC495 views6 reactionsread 8 August 2026

First payment to fund Logris the Bard for R&D tokenomics proposal complete. https://snapshot.org/#/rokonetwork.eth/proposal/0x0c18254c6b35d8b7e24f2c0e74ac0b6130c44c046825ad3a08218d671e8fe8cb Treasury $ROKO swap for $USDC https://etherscan.io/tx/0x77a87052ae720978210319d1792d3b29c8ff9eaf2842ac6f4fd66656f74e0fda Treasury Transfer of 10,000 $USDC to LogrisTheBard.eth https://etherscan.io/tx/0x6ad0b68e0310a578a9aea141

🔥6

Showing the 12 most recent of 20 posts we hold for @RokoCitadel. 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 — 616,982 of 1,189,255entries 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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“Ꭱꮻꮶꮻ Ꮯꮖꭲꭺꭰꭼꮮ” (@RokoCitadel), 175 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/RokoCitadel.

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.