Channel
@namada_gov_monitor
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
29subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002316313115 |
|---|---|
| Type | Channel |
| Username | @namada_gov_monitor |
| Description | Namada governance monitor powered by 0Y validator. 0y.io — social-graph collective focused on validating, defi, infrastructure, LP, investment, and content creation. managed by @cyberomanov. |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/namada_gov_monitor |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 04:46 | 29 | no change |
| 6 Aug 2026, 17:18 | 29 | first reading |
20 posts held, back to 6 June 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 20 posts for this entry, the most recent from 5 March 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.
2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1 | 50.0% | |
| 😁 | 1 | 50.0% |
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 7 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 2reactions 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 6 June 2025 to 5 March 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @namada_gov_monitor. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 6 June 2025 to 5 March 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
#42 | Signalling - Knowable is leaving Namada https://forum.namada.net/t/knowable-is-leaving-our-namada-role/1930 Knowable joined Namada to help launch and grow, but faced challenges with ecosystem isolation. Despite efforts, the team is leaving due to insurmountable obstacles. Commitments and contributions will end, with assets and responsibilities transferred. PGF initiatives will be wound down, with plans to dis…
#41 | Whitelist Osmosis and Cosmos Hub channels permissionlessly https://forum.namada.net/t/permissionless-whitelisting-of-osmosis-and-cosmos-hub-channels/1912 This proposal aims to allow unlimited permissionless transfers between Namada, Osmosis, and Cosmos Hub blockchains. It supports Polaris and enables IBC Eureka by facilitating transfers with Osmosis and Cosmos Hub for ERC20 assets into Namada. The code for th…
#40 | Turn off PGF treasury inflation https://forum.namada.net/t/proposal-to-turn-off-pgf-treasury-inflation/1908 Proposal to change pgf_inflation_rate parameter from 0.05 to 0.00. The PGF treasury has sufficient funds for sustainability, reducing total network inflation from 8.64% to 3.64%. Inflation is seen as a cost and should only be used when it adds value. The future fees from shielded pool usage will fund th…
#39 | Update tx_ibc.wasm for mainnet v201.0.7 https://forum.namada.net/t/mainnet-update-tx-ibc-wasm-for-v201-0-7/1910 This proposal aims to update the on-chain wasm tx for IBC transfers to facilitate Namada's integration with Polaris and allow IBC Eureka assets to flow into Namada. The attached wasm file was generated using code from a specific GitHub repository. More details can be found in the forum discussion. …
#38 | Update two protocol parameters needed for IBC Eureka activation https://forum.namada.net/t/mainnet-update-two-protocol-parameters-for-ibc-eureka-activation/1906 Proposal to increase `max_tx_bytes` and `max_proposal_bytes` parameters for IBC Eureka activation. Refer to Namada forum for details. Proposal code available on GitHub. 01 Dec, 20:43 UTC - 04 Dec, 20:47 UTC https://namada.valopers.com/proposals/38
#37 | Signalling - Upgrade to v201.0.7 at Block 4514500 https://forum.namada.net/t/signalling-upgrade-to-v201-0-7-at-block-4514500/1899/1 Knowable proposes upgrading Namada mainnet to v201.0.7 at Block 4514500, bringing permissionless IBC assets, transaction-level fee capture, support for Ethereum assets, shielded sync optimizations, bug fixes, and more. This upgrade sets the stage for future developments and align…
#36 | Adjust Shielded Set Rewards to Align with PMF Experiments. https://forum.namada.net/t/adjusting-shielded-set-rewards-to-align-with-pmf-experiments/1889 Veil proposes to reduce Shielded Set Reward (SSR) incentives for six tokens to 0, focusing Namada's resources on product-market fit initiatives. USDC incentives will be maintained for stability, allowing for new asset introduction and experimentation. The prop…
#35 | Whitelist tokens over the Osmosis IBC channel for Polaris integration. https://forum.namada.net/t/proposal-whitelist-tokens-manually-for-polaris-integration/1883 This proposal aims to unblock Polaris integration by manually whitelisting tokens over the Osmosis IBC channel. Whitelisted assets can be viewed in the Rust code. After an upgrade, a governance proposal can whitelist a whole channel permissionlessly.…
#34 | Update two gas parameter values https://forum.namada.net/t/proposal-increase-two-gas-related-protocol-parameters/1880 This proposal aims to increase two gas parameters in the protocol: Max block gas from 5M to 10M and Masp fee payment gas limit from 100k to 300k. The changes will support IBC Eureka and address unshielding difficulties for users. Check the forum for more details. 22 Oct, 03:16 UTC - 27 Oct, 0…
#33 | Add USDN support to the MASP, whitelist USDN as a gas token, and establish initial rate-limit parameters. https://forum.namada.net/t/proposal-to-add-usdn-support-to-the-masp/1871 Veil proposes adding USDN to Namada's Multi-Asset Shielded Pool (MASP), whitelisting USDN as a gas token, and setting initial rate-limit parameters. This would make USDN the first yield-bearing stable asset in the MASP, allowing shie…
#32 | Update Shielded Inflation: MASP Gain Calibration & SSR Target Adjustments https://forum.namada.net/t/adjust-the-masp-gain-and-ssr-target-values/1847 This proposal aims to update the Multi-Asset Shielded Pool incentive mechanism by adjusting Proportional Gain and Derivative Gain values for incentivized assets. It also suggests reducing Shielded Set Reward targets to align with usage and privacy needs, focusing…
#31 | Reduce staking inflation from 5% to 2.75% https://github.com/namada-net/namada-governance-upgrades/blob/9ea5c5a6d8d29a2866e83f73ece069d4658cd822/increase_target_staked_ratio/src/lib.rs This proposal aims to decrease staking inflation from 5% to 2.75% and lower the target staking ratio from 55% to 45%. The goal is to reduce unnecessary dilution, incentivize privacy usage through Shielded Rewards, and strengthe…
Showing the 12 most recent of 20 posts we hold for @namada_gov_monitor. 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 — 881,197 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.
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.
“namada governance | 0Y” (@namada_gov_monitor), 29 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/namada_gov_monitor.
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.