Channel
@TensorCash_org
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
162subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004312792965 |
|---|---|
| Type | Channel |
| Username | @TensorCash_org |
| Created | 26 June 2026 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/TensorCash_org |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 16:47 | 162 | no change |
| 7 Aug 2026, 14:16 | 162 | first reading |
20 posts held, back to 26 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 7 of 15 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 20 (26 June 2026 – 8 August 2026) |
| Views total | 3,103 |
| Reactions total | 21 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 16:47 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
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.
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.
23 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 52.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 12 | 52.2% | |
| 🔥 | 6 | 26.1% | |
| 👍 | 5 | 21.7% |
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 8 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 23reactions 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 26 June 2026 to 8 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
It is the weekend—a good time to take a step back and look at what we have accomplished. Pick a prompt. Any prompt you want. A real model responds. The response is perfectly natural and no different from a normal model response. There is no separate mining workload, but that inference can mine a block. It is easy to take this for granted because it looks so simple and has run so smoothly. But no one had done it bef…
❤4🔥1
📜 New blog: Real-World Assets on TensorCash — the ticker is the easy part. A blockchain moves a unit pseudonymously, efficiently, across borders. What it cannot do by itself is say what the unit MEANS. If a token represents cash, reserves, a fund or a share, someone must define the claim and sign the terms — and the asset keeps living after issuance: distributions, votes, amendments. How TensorCash joins the two ha…
📢 TensorCash v1.1.0 — coordinated network upgrade at block 20,440, expected today. v1.1.0 moves the difficulty algorithm from the 2,016-block retarget to ASERT: difficulty adjusts every block based on how far the chain is ahead of or behind its 600-second schedule. The old rule needed weeks to respond when mining throughput changed abruptly — the cause of the recent slow blocks. ⚠️ UPGRADE BEFORE BLOCK 20,440 — nod…
👍2
🔐 Post-quantum spending is live on TensorCash — since block zero, not a someday migration. You opt in by funding a new address type: tc1z… • Taproot v2, key path disabled by consensus. A tc1z is an ordinary 32-byte Taproot output, but consensus permits only script-path spends — so there is no secp256k1 key-path signature to attack. What the leaf requires is up to the script; the standard wallet template makes it a …
🔥3
⛏️ TensorCash is at 600-second blocks. Difficulty retargeted at block 20,160 (+3.72×) and blocks have averaged 605.7s since — right on target. Early miners rode blocks arriving 4–6× faster than target, and those rewards went to the people who showed up first. Thank you. The network is doing ~7.7M tokens/sec of real model inference — 4.6 billion tokens every block. More powerful commercial models are on the way, and…
👍1
On 28 July, in mainnet block 19,978, a tokenised difficulty option changed owner and native TSC moved the other way — both legs inside the *same* transaction. There was no exchange account, no deposit or withdrawal, no escrow agent and no custodian. Two people running the TensorCash desktop wallet found each other over a bulletin board, negotiated directly, and settled on chain. The interesting part is the guarante…
❤5🔥2
A miner ran the committed model at fp8 on a smaller GPU and submitted the proof as bf16. Full verification reran the model at bf16: the p-values collapsed, both blocks were assigned zero work, and the chain never extended them. Trust in action. 👇 https://tensorcash.org/blog/catching-a-quantized-miner/
❤2
Meet COMPUTE — the first asset issued on TensorCash. Real AI inference is the work that secures the chain, so as compute grows, difficulty becomes a live on-chain tracker of AI-inference activity. COMPUTE is the clearest way to see the asset-issuance platform in action. 👇 https://tensorcash.org/blog/tokenised-difficulty-options/
⚠️ Wallet setup note: the AI-proof check needs a verifier, and the wallet doesn't come pointed at one — you set it yourself. Run the open-source verifier on your own GPU, or point your node at a verification service you trust: VALIDATOR_HTTP_URL=https://your-verifier 👇't ask someone's server what you own. The TensorCash wallet is a full node with a GUI — balances and assets verified locally, not fetched from a backen…
Your wallet shouldn't ask someone's server what you own. The TensorCash wallet is a full node with a GUI — balances and assets verified locally, not fetched from a backend. Prebuilt for Linux; runs anywhere with Docker (VNC console: off by default, password-gated). 👇 https://tensorcash.org/blog/how-to-run-the-wallet/
TensorCash mainnet, six weeks in: implied throughput has climbed from ~27 to 100,900 tok/s, and difficulty has retargeted up step by step to keep pace. Our version of hashrate is measured in tokens per second of real inference, not wasted hashes. 👇 https://tensorcash.org/explorer
TensorCash v1.0.5 is out — setting up has never been easier. Prebuilt, public Docker images for GPU mining workers (Hopper + Blackwell) and the full node, plus Linux node builds and macOS (Apple Silicon) miner binaries. No more building from source. 👇 https://github.com/tensorcash/tensorcash/releases/tag/v1.0.5
Showing the 12 most recent of 20 posts we hold for @TensorCash_org. 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 — 749,875 of 1,345,403entries 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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“TensorCash” (@TensorCash_org), 162 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/TensorCash_org.
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.