Channel
@gonka_software_updates
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
140subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003309145823 |
|---|---|
| Type | Channel |
| Username | @gonka_software_updates |
| Description | Официальные обновления Гонки. / The official source for all critical updates regarding Gonka. Контакты: @prog256 |
| Created | Between 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/gonka_software_updates |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 22:31 | 140 | no change |
| 8 Aug 2026, 04:35 | 140 | 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 1 of 8 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (26 June 2026 – 7 August 2026) |
| Views total | 412 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 22:31 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.
# Bridge update reminder A few nodes appear to be running an outdated bridge and haven't updated it yet. If your node is one of the following, please check and update your bridge: gonka1m58jds005cttwq2vt0p7yk6vy2aqg254cqqppf gonka1gyk0aahvr3qeju4zx0nplfreej6cy4jjk8svc5 gonka1w29nvdy6caqtrw30whz9h6ghl0xszwh3egndah gonka1346p2h8dn4kp98c5e93k5q64g0h7vxjxnd55fh gonka1avqx987zq7q9alr9f9grtcprescgzq0wtr7fue Please chec…
## API Binary Update: v0.2.15-post3 A new API binary is available. This release improves PoC seed reliability and includes several API and deployment fixes. What changed PoC seed stability - Missed seed submissions are recovered after epoch-boundary lag - Local seed restoration retries after transient failures such as signer unavailability, preventing validators from getting zeroed API - /v1/versions now returns …
To check the voting status: export NODE_URL=https://node3.gonka.ai/ ./inferenced query gov votes 89 -o json --node $NODE_URL/chain-rpc/ ## Required actions in preparation for the upgrade In case the proposal is approved, the following preparation is recommended. - Now / before the mainnet upgrade — update your API and bridge. To keep the Ethereum bridge stable during the mainnet upgrade, update the api binary and th…
# v0.2.14 Upgrade Proposal Enters Governance The v0.2.14 proposal is now on-chain and open for voting. The mainnet chain/API work focuses on PoC duplicate-artifact protection, early share detection, classic inference API deprecation (disabling /v1/chat/completions billing on mainnet and removing embedded /v1/devshard from the API binary), reward recipient routing, and upgrade-time safety fixes. The devshard part prep…
# The PR for the devshard-only upgrade is now open for review Devshard upgrades update the devshard runtime independently from the main blockchain. They do not require a coordinated full-node upgrade through Cosmovisor, do not affect mainnet behavior, and are not expected to cause downtime for inference serving. If approved through the governance process, the new devshard version will run in parallel with the existin…
# Proposal 88 has passed: Kimi-K2.6 re-registered, devshard v1/v2 remove The expedited proposal 88 was approved on-chain. ## Kimi-K2.6 bootstrap (epoch 331) moonshotai/Kimi-K2.6 is back in the governance model list and enters the standard bootstrap flow. * Declare intent before block 5,105,276 (July 17, ~12:05 UTC): ./inferenced tx inference declare-poc-intent moonshotai/Kimi-K2.6 * Switch your MLNode to Kimi in th…
## How to vote If you do not have direct access to the key that holds voting power, or want another key to vote on your behalf, please refer to the guide on granting governance voting permission from a cold key to a warm key. Proposal details and voting are available via inferenced. Any active node can be used. Available nodes include: - http://node1.gonka.ai:8000 - http://node2.gonka.ai:8000 - https://node3.gonka.…
# Expedited governance vote (proposal 88): re-register Kimi-K2.6 and remove devshard v1/v2 runtimes This is the second step of the Kimi recovery plan announced on July 15. Proposal 87 removed moonshotai/Kimi-K2.6 from the active set; proposal 88 re-registers it in the governance model list so it goes through the standard bootstrap starting at epoch 331. The same proposal removes approved_versions v1 and v2 from devs…
To check the voting status: export NODE_URL=https://node3.gonka.ai/ ./inferenced query gov votes 87 -o json --node $NODE_URL/chain-rpc/ ## Deadlines * Voting Time: 2026-07-15 17:01 ~ 2026-07-16 05:01 (PDT) / 2026-07-16 00:01 ~ 2026-07-16 12:01 UTC (expedited, 0.667 yes-threshold; turnout matters, vote promptly). * Bootstrap intent deadline and epoch timings follow in the bootstrap instructions.
# Expedited governance vote (proposal 87): remove Kimi-K2.6 for a fast re-bootstrap moonshotai/Kimi-K2.6 lost its PoC validation majority in epochs 328–329 (see the incident details here). Removing Kimi from the active set now and re-bootstrapping it is the fastest way to bring it back with minimal downtime — the same recovery path as proposal 78 in June. The proposal removes moonshotai/Kimi-K2.6 from PoC params bef…
## Recovery plan The safest way to restore Kimi is to re-add it through a fresh bootstrap (~1.5 epochs): 1. [Today] An expedited proposal removes Kimi before the next PoC and re-adds it immediately after. A separate announcement with the proposal ID, voting commands, and deadlines follows. 2. [Tomorrow] Kimi goes through the standard bootstrap flow again: declare intent, deploy window, PoC store commit. Instructions…
# Kimi-K2.6 incident (epochs 328–329): what happened, recovery plan, and a change in delegation guidance In epoch 328, moonshotai/Kimi-K2.6 lost its PoC validation majority. Hosts serving Kimi were knocked out of the group at the start of epoch 329. The rest of the network kept operating normally. ## What happened Two guardian-operated servers running Kimi failed at the same time: * On one server, the MLNode running …
Showing the 12 most recent of 20 posts we hold for @gonka_software_updates. 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 — 569,532 of 1,478,351entries 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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“Обновления ПО Гонка / Gonka Software Updates” (@gonka_software_updates), 140 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/gonka_software_updates.
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.