Channel
@nowarp_io
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
33subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002371546535 |
|---|---|
| Type | Channel |
| Username | @nowarp_io |
| Description | nowarp.io / github.com/nowarp / x.com/nowarp_io contact: @jubnzv |
| Created | 24 January 2025 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/nowarp_io |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 01:01 | 33 | no change |
| 7 Aug 2026, 22:40 | 33 | first reading |
18 posts held, back to 24 January 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 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 18 posts for this entry, the most recent from 13 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 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.
A miscompilation is not a vulnerability until someone deploys it Three PolkaVM recompiler bugs I recently found got announced as "critical" by someone. They are not. Here is the taxonomy: • A bug is a deviation from intent. • A vulnerability is a bug with a reachable attack path. • Risk is a vulnerability plus an asset. CVSS notes this: the Base Score is intrinsic severity, assuming a reasonable worst case across …
Signed Georgiy Komarov
Part 2 of the compiler fuzzing series is out — this time hunting miscompilations: bugs where the compiler accepts a valid program and silently emits code that behaves differently. On smart-contract platforms this is the bug class that can drain user funds, and it's invisible to auditors because the source is correct. Where Part 1 went after compiler crashes (ICE), Part 2 targets semantic drifts and miscompilations a…
Signed Georgiy Komarov
A 20-year-old JDK bug, reincarnated in Tolk I was experimenting with approaches and techniques to find miscompilation errors. Not crashes – those are the easy ones. This time — the Ethereum ecosystem. Every codebase there has been audited to death; bug-hunting is desperate, and each find I made was complicated. So I tried a similar approach on TON, with the latest Tolk compiler. Just for fun. It took about 30 minut…
Signed Georgiy Komarov
100+ compiler bugs found across 5 smart-contract compilers — Sui Move, Cairo, Solang, Solidity, and Leo — in a fresh blog post on compiler fuzzing. Only bugs in later compilation passes are reported; no malformed-input crashes. The post shares experience, heuristics, and an overview of approaches for setting up a low-effort fuzzing workflow to test compiler implementations. Part 1 focuses only on ICE. What the post…
Channel name was changed to «nowarp | Web3 Security»
Skry: Hybrid LLM Static Analysis for Sui Move contracts The tool is static analysis-first and uses LLMs only for constrained semantic classification, focused around access control, governance, and centralization risks non-detectable by pure static analysis. This is a proof-of-concept tool showing the approach is viable. Blog post: nowarp.io/blog/skry Source code: github.com/nowarp/skry
🎉Misti 0.9 has just landed on NPM! ⚡️ More Detectors: New Tact detectors: DuplicatedImport, TransitiveImport, RedundantBooleanExpression, UnusedMethodArgument and PreferGlobalFunction. 🖥 Improved Github Actions integration: Better user experience via SARIF output format support. 🛠 Custom Tools: Misti now enables users to write Custom Tools, just like Custom Detectors. 🔧Fixes & Enhancements: Check out the full cha…
🚀 Introducing Scanner: Mass Static Analysis for TON Smart Contracts We've released a demo showcasing our static analysis tooling for TON contracts. 🔍 Features: - ~20 curated contracts with zero vulnerabilities - Detailed analysis results - Great for learning Tact development best practices and exploring the tooling capabilities 🛡️ We scan everything for research but only display clean contracts without vulnerabili…
💬 Follow us: x.com/nowarp_io Check out our first thread for an overview of Misti: https://x.com/nowarp_io/status/1921501042534908240
We live on the TON Talent Directory 🚀
🔧 Announcing: OCaml library for FunC parsing: nowarp/ocaml-func For developers working with FunC, this library provides AST and parser functionality.
Misti 0.8.1 has just been released. 🔧 This patch release introduces Tact 1.6.6 support and includes minor changes and fixes. Check out the full changelog.
Showing the 12 most recent of 18 posts we hold for @nowarp_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 — 659,021 of 1,169,250entries 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.
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 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“nowarp | Web3 Security” (@nowarp_io), 33 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/nowarp_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.