Channel
@soliditypedia
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
4,338subscribers
-38 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001180526959 |
|---|---|
| Type | Channel |
| Username | @soliditypedia |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 25 August 2026 |
| On Telegram | t.me/soliditypedia |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 14:45 | 4,338 | -8 |
| 22 Aug 2026, 15:57 | 4,346 | -6 |
| 19 Aug 2026, 07:53 | 4,352 | -7 |
| 16 Aug 2026, 05:19 | 4,359 | -7 |
| 12 Aug 2026, 23:54 | 4,366 | -6 |
| 10 Aug 2026, 10:03 | 4,372 | -3 |
| 7 Aug 2026, 15:15 | 4,375 | -1 |
| 7 Aug 2026, 02:00 | 4,376 | no change |
| 7 Aug 2026, 01:56 | 4,376 | 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 6 pagesof 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 4 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 20 (26 June 2026 – 5 August 2026) |
| Views total | 1,042 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 18:18 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.
15 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 73.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 11 | 73.3% | |
| 🔥 | 3 | 20.0% | |
| 🤔 | 1 | 6.67% |
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 6 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 15reactions 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 5 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.
Spending policies enforced by a ZK proof, not a trusted signer Most wallet spending limits leak intent: the contract sees the amount, the recipient, the rule. ERC-8366 proposes a composable interface where any fund-holding contract — an escrow, ERC-4337 account, or EIP-7702-delegated EOA — releases funds only against a zero-knowledge proof that a policy was satisfied, without revealing the policy inputs on-chain. T…
ERC-4337 paymasters that accept ERC-20s, signatures, or NFTs OpenZeppelin Contracts v5.7 ships composable paymaster primitives, so sponsoring gas becomes a policy you write, not a bespoke contract. The hard part in a paymaster is validatePaymasterUserOp: you must decide who to sponsor and how to charge, then reconcile in postOp after the real gas cost is known. The new base contracts split this into pluggable check…
👍2🔥1
Uniswap v4 hooks move security into your code — and the defaults bite Hooks let pools run custom logic on swaps and liquidity changes: dynamic fees, custom accounting, external calls. That flexibility relocates trust boundaries into hook code, and two real incidents (Cork, Bunni) show where it breaks. The recurring failures Trail of Bits flags: Access control: hook callbacks must reject any caller that isn't the P…
OpenZeppelin 5.7.0 breaks EIP-712 domains that relied on long name/version If your contract passes a name or version longer than 31 bytes to EIP712, upgrading to 5.7.0 will now revert in the constructor with ShortStrings.StringTooLong. Earlier versions kept a storage fallback for values that didn't fit a ShortString. That fallback is gone: the domain is stored exclusively in immutables. Cheaper reads and a simpler …
Instant redemption is the wrong default for illiquid RWAs Tokenize an asset that settles T+2 off-chain, then let it redeem instantly on-chain, and you have created a liquidity mismatch: the vault promises what the underlying can't deliver on demand. Two design responses are converging. Async settlement: ERC-7540 splits redemption into request then claim, so the vault can honor real settlement windows instead of pre…
Pricing a prediction market on-chain with LMSR, no order book A new ERC draft binds each binary (YES/NO) market one-to-one to an ERC-721: question, odds, pool, and resolution all live on-chain and render into the tokenURI. The interesting part is the pricing. Instead of matching buyers and sellers, it uses Hanson's Logarithmic Market Scoring Rule. A single liquidity parameter b sets depth; the cost to move the mark…
Study real exploits by running them, not reading about them Most exploit write-ups leave you guessing about the exact state and call sequence. The evm-hack-registry is a self-contained, offline-runnable archive of DeFi exploit proof-of-concepts spanning the full history of EVM hacks (2017 to 2026). Each entry forks the pre-exploit state and reproduces the drain in a test, so you can step through the actual call tra…
Upgrading an EOA to a smart wallet without losing its address EIP-7702 lets an EOA set code via a signed authorization, but you still need a storage layout that survives implementation swaps. Base's eip-7702-proxy is a minimal ERC-1967 proxy that delegates a plain EOA to CoinbaseSmartWallet, keeping the account's address and history intact. Why it matters: the naive approach points the EOA directly at wallet logic,…
An O(1) fully on-chain limit order book, without per-order storage Classic on-chain CLOBs die on gas: matching walks a linked list, so fills and cancels scale with book depth. The Cohort Order Book proposal sidesteps this by making liquidity at each price level fungible. The mental model: instead of tracking individual orders, each price level holds pooled liquidity split into generations (cohorts). A trader's clai…
Ostium drained ~$18M via a registered oracle forwarder and future-dated reports Per Blockaid, the attacker didn't break the price feed — they abused a trusted path into it. A registered forwarder submitted oracle reports timestamped in the future, letting the attacker book fake trading profits against the vault before honest prices caught up. Root cause is a recurring pattern: perps and margin systems trust any rep…
This week in Solidity Security and correctness: Yul optimizer miscompile: the optimizer's call-graph analysis sometimes tagged mutually recursive functions as non-recursive, excluding them from memory spilling and risking silent corruption. Recheck builds that lean on the optimizer. details OpenZeppelin's contributor rules: a solid checklist for anyone shipping libraries — API design for safe inheritance, errors/e…
An AI agent that can wipe prod with one command isn't hypothetical — it's Tuesday 😅 A shell alias blocks one command on one machine. HELM is a fail-closed firewall for the whole agent boundary. Every action hits it before it runs: safe goes through, destructive gets blocked, unknown MCP tools get quarantined, anything borderline escalates to you. Every decision comes signed with a receipt you can verify offline. Lo…
👍3
Showing the 12 most recent of 20 posts we hold for @soliditypedia. 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 — 289,601 of 1,604,598entries 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 25 August 2026 — this entry's latest reading, not the date you are reading this.
“Solidity Treasures” (@soliditypedia), 4,338 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/soliditypedia.
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.