Channel
@railoxide
On this record: Growth · Engagement · Posts · Citations · Cite this entry
9subscribers
+3 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004245190127 |
|---|---|
| Type | Channel |
| Username | @railoxide |
| Created | 4 June 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 4 September 2026 |
| On Telegram | t.me/railoxide |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 17:34 | 9 | +2 |
| 15 Aug 2026, 16:26 | 7 | +1 |
| 12 Aug 2026, 22:32 | 6 | no change |
| 8 Aug 2026, 00:06 | 6 | first reading |
14 posts held, back to 4 June 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 1 page 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 14 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
New release: v0.2.0-beta.1 Tag: v0.2.0-beta.1 - Added Tor session statistics UI and automatic detection of degraded state - Added outgoing PPOI recovery - Added "Mimic Railway" mode to Shield. This reduces on-chain type-of-wallet identification risk as long as Railway stays popular, at the expense of slightly higher gas cost and submitting an infinite ERC20 approval. - Fixed a rare race condition on network mode swit…
New release: v0.1.0-alpha.12 Tag: v0.1.0-alpha.12 Added sandboxed Flatpak distribution, see https://github.com/triamazikamno/railoxide/pull/3 for details Release page: https://github.com/triamazikamno/railoxide/releases/tag/v0.1.0-alpha.12
New release: v0.1.0-alpha.11 Tag: v0.1.0-alpha.11 - Added block-builder sponsored self-broadcasting mode (currently Mainnet only). This is a reliable and permissionless way to send private transactions using an empty/underfunded EOA without public broadcasters - Added advanced public send actions (arbitrary contract calls, contract deployments) - Hardened rpc client against very slow rpc endpoints - Various UI improv…
New release: v0.1.0-alpha.10 Tag: v0.1.0-alpha.10 - De-cluttered hardware wallet unlock dialog - Added passphrase mode cycling on Tab key press on Trezor unlock - Added 1h cooldown timer for PPOI on shielding, added safe block confirmation counter for pending transactions - Added tx fee estimation to public Send and Shield views - Added gas top-up feature for arbitrary destination accounts - Refactored native token S…
New release: v0.1.0-alpha.9 Tag: v0.1.0-alpha.9 - Redesigned public broadcaster picker - Dramatically reduced idle cpu usage - Added auto-lock on inactivity. Default is 15m, configurable in Settings -> Privacy - Limited waku communication to unlocked state. When wallet locks, all connections to waku network are dropped to prevent wasteful bandwidth consumption Release page: https://github.com/triamazikamno/railoxide…
New release: v0.1.0-alpha.8 Tag: v0.1.0-alpha.8 Fixed windows build by downgrading Arti(Tor client library) Release page: https://github.com/triamazikamno/railoxide/releases/tag/v0.1.0-alpha.8
New release: v0.1.0-alpha.7 Tag: v0.1.0-alpha.7 - Did a massive refactor to the artifact-based sync logic, now it's much more reliable, faster and prevents a whole class of possible race conditions - Improved status bar indicators for better visibility on sync progress - Added more ways to reset various state caches in Settings -> Maintenance Release page: https://github.com/triamazikamno/railoxide/releases/tag/v0.1…
New release: v0.1.0-alpha.6 Tag: v0.1.0-alpha.6 - Added vault password change - You can now reset local POI cache. Located in Settings -> Privacy -> POI - Improved UX around pending/recoverable POI proofs - Added sync status indicators to the status bar Release page: https://github.com/triamazikamno/railoxide/releases/tag/v0.1.0-alpha.6
New release: v0.1.0-alpha.5 Tag: v0.1.0-alpha.5 - Open last used wallet and chain on app start - Show estimated tx fee in broadcaster picker - Fix build on linux and windows - Remove dependency on protoc binary Release page: https://github.com/triamazikamno/railoxide/releases/tag/v0.1.0-alpha.5
New release: v0.1.0-alpha.4 Tag: v0.1.0-alpha.4 - Added `Export keys` where you can retrieve seed phrase and view-only key - Randomized equal-fee broadcaster picker ordering to disincentivize smaller 0zk address farming - Improved wallet readiness transitions and added more detailed sync status - Added indexed artifact sync option with prefilled publisher key and IPNS name of the railgun-indexer instance. See [railgu…
New release: v0.1.0-alpha.3 Tag: v0.1.0-alpha.3 - Added gas top-up option during unshielding - Improved recipient picker, it shouldn't clip on smaller screens anymore - Added attention attraction and badge counter for incoming walletconnect requests - Added version info and social buttons to the header Release page: https://github.com/triamazikamno/railoxide/releases/tag/v0.1.0-alpha.3
RailOxide pinned «Group for discussion/feedback: @railoxide_discussion»
Showing the 12 most recent of 14 posts we hold for @railoxide. 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.
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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“RailOxide” (@railoxide), 9 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/railoxide.
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.