Channel
@michael_curve
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,239subscribers
+5 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002241586181 |
|---|---|
| Type | Channel |
| Username | @michael_curve |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 28 August 2026 |
| On Telegram | t.me/michael_curve |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 06:13 | 1,239 | -1 |
| 25 Aug 2026, 03:47 | 1,240 | +5 |
| 18 Aug 2026, 20:35 | 1,235 | +2 |
| 15 Aug 2026, 19:36 | 1,233 | -1 |
| 12 Aug 2026, 19:43 | 1,234 | +1 |
| 6 Aug 2026, 22:08 | 1,233 | -1 |
| 6 Aug 2026, 08:36 | 1,234 | no change |
| 5 Aug 2026, 22:01 | 1,234 | first reading |
20 posts held, back to 31 October 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 20 July 2026. An engagement rate over an empty window would be a number about nothing.
In his recent interview, Andre Cronje weighted heavily (https://x.com/therollupco/status/2078961843008397433?s=20) in favor of smart contract upgradability, contrary to what he said before. For context: Andre was one of the people who ignited the DeFi summer in 2020, started a bunch of projects (including Yearn) and invented ve(3,3) variant of ve-tokenomics launched in Solidly, now used by Aerodrome. Is he right to …
So looks like Uniswap finds out tech which was used by Curve since its start in 2020 (using liquidity based on yield-bearing vaults), calls it FX layer (it's USD-USD swaps in reality) and tries to sell to financial institutions as something new? https://blog.uniswap.org/spark-moves-150m-of-liquidity-to-v4-with-new-hook-coming-soon 🥳 Curve's UI | ✈️ Telegram Chat | 🤟 Twitter/X 🛸 China Chat | 📱 YouTube | 📱 Discord
Seeing a lot of fears about Claude Mythos allegedly being released today or tomorrow and "everything getting hacked". I suspect that we should not directly translate its success in detecting bugs in browsers and Linux Kernel to smart contracts. The software where Mythos found something is containing tens of millions lines of code and simply cannot fit the context. Smart contracts are really different. They usually …
Here we go again. Custodial stablecoins EURR and USDR were hacked by company-s multisig wallet being compromised [https://www.coindesk.com/markets/2026/05/26/stablr-freezes-usdr-and-eurr-after-attacker-mints-usd13-5-million-in-unbacked-tokens]. It was a 1-of-3 multisig, i.e. worse than just an admin key. In response to this hack of a MiCa-compliant (!) stablecoin the team did a very EU-compliant thing: froze money o…
Seeing many people getting their telegram hacked. The malware uses telegram of someone from your contact list to join some group. The group has a “SafeGuard” mini-app to “verify” yourself. It asks your telegram credentials and starts posting as if it was you. Don’t fall for these and be safe
I've made a proposal on how to recover bad debts in lending protocols, starting with Curve's own one as an example. Better than bailouts? https://gov.curve.finance/t/crv-long-llamalend-market-recovery/11062 🥳 Curve's UI | ✈️ Telegram Chat | 🤟 Twitter/X 🛸 China Chat | 📱 YouTube | 📱 Discord
Observing the hack which happened yesterday to rsETH, which caused a serious contagion at Aave. Wow, it's a lot to unfold. First of all, looks like there is no exposure of Curve or Yield Basis to either rsETH or Aave problems. But this all of the issue started with LayerZero which is relied upon by crypto with quarter of a trillion in value. How? Let's have a look. Kelp's rsETH uses a LayerZero bridge. The bridge a…
A quick thought about Bitcoin quantum safety (even though I am somewhat doubtful about the claim that "everything will be hacked soon" but who knows). Today Bitcoin addresses are not reversible to private keys even by quantum computers. But as soon as the address transacts - it well can be since public key / signature is exposed. Bitcoin transactions do not reuse addresses by default these days, so the problem appea…
Yesterday I noticed some unusual swaps in Yield Basis related pools on Curve. At first, I was very worried (always good to check when you see something unusual), but it appeared that the reason was someone exchanging 50M USDT to 36k USD worth of AAVE (sic!) [https://x.com/StaniKulechov/status/2032193345414664659]. On Aave, you can essentially swap collateral via an external exchange platform - CowSwap in this case. …
Looks like Vitalik now came to the same vision about L2s. Very very nice! https://x.com/VitalikButerin/status/2018711006394843585
Upgradable smart contracts are a bug [https://medium.com/consensys-diligence/upgradeability-is-a-bug-dba0203152ce]. Remember this? It's mostly controversial now because very few projects do immutable smart contracts these days (but Curve and Yield Basis do). So why immutable smart contracts are good? - Humans make bugs in code. Steve McConnell in his book "Code Complete" famously wrote that average for software eng…
Wow, that's quite a volatile day, and quite a peg shaking for crvUSD. But here are good news: - crvUSD is still overcollateralized and fully backed, no surprises; - Yield Basis earned something on volatility; - More information just before releasing HybridVaults which enable unbounded scaling of Yield Basis. Wait, what's HybridVault? These are vaults where in order to go above the "normal" Yield Basis cap you need …
Showing the 12 most recent of 20 posts we hold for @michael_curve. 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 — 741,783 of 1,622,129entries 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 3 registered channels — 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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“Curious facts from Michael@Curve” (@michael_curve), 1,239 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/michael_curve.
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.