GM! Some people been DMing me lately asking if I’m gone and whether I’m coming back. I’m still here and active on twitter. Most of you probably know my handle: https://x.com/edwardmorra_btc I know twitter algorithms suck ever since they changed and there is a lot of garbage content being pushed on the timeline. A lot of big profiles (many of my colleagues) are coming back to posting on telegram because it’s cleaner…

Channel
Edward Morra
@edwardmorra_btc
On this record: Growth · Engagement · Posts · Citations · Cite this entry
6,629subscribers
-6 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001131855629 |
|---|---|
| Type | Channel |
| Username | @edwardmorra_btc |
| Created | 24 June 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/edwardmorra_btc |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 09:39 | 6,629 | -2 |
| 12 Aug 2026, 01:33 | 6,631 | +3 |
| 8 Aug 2026, 22:08 | 6,628 | -5 |
| 6 Aug 2026, 05:00 | 6,633 | -2 |
| 6 Aug 2026, 03:19 | 6,635 | no change |
| 6 Aug 2026, 02:23 | 6,635 | first reading |
Engagement
18 posts held, back to 5 January 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 9 pagesof 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 18 posts for this entry, the most recent from 7 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
$BTC Gap filled. As obvious as it might sound - CME gaps are probably the highest hit rate pattern out there. It has like 90% probability of being filled (almost always). Whenever you see one - your bias should be based around it. In this case you shouldn’t had panicked during this Monday nuke.
Been trading on Hyperliquid for the past month and honestly been amazed how smooth & efficient UI/UX is. ▪️No KYC. Quick and simple onboarding. Generate your wallet and fund it with USDC (Arbitrum). ▪️Fast listings (they listed TRUMP way ahead of any CEX). My magic link gives you fee discount + your stops become invisible to market makers: 👉https://app.hyperliquid.xyz/join/MORRA
$SUI | Update Closed most of my short here. Might wick under $3.49 to shave some liquidity but my planned trade is complete here. Hyperliquid: https://app.hyperliquid.xyz/join/MORRA
$BTC Markets are front-running yet another Saylor announcement (they have been routinely bearish usually). I think we bottom early in the week and fill the gap up ($104.7-105k) https://www.tradingview.com/x/3uhiRaQ8/
🔹Kaito - the laziest airdrop ever If you have a twitter account with followers - this is your chance to participate with no extra effort whatsoever. It costs you nothing, you literally just link your twitter account to Kaito and continue tweeting as usual. You will earn “yap points” based on engagement on your tweets. Most likely your yaps will be converted into airdrop tokens in future, so don’t skip on that - star…
$SOL Fixed some profit now on my bottom buys. Bought at $176 -> sold at $215. Captured 23% move. Thanks Trump for the pump.
Here is the seasonality I was talking about. Looks like ETH failing second January in a row but look at February to May. Historically it is the best period for ETH bulls. Data from: https://www.coinglass.com/today
$ETH Some people been asking about ETH. There is nothing really to update at this point to be honest. I’m still in my long positions (spot+perps). These 2 last buys sitting slightly in profit (average entry was $3.3k). I probably should have taken profits on my last $ETH long when I closed most of my positions in the beginning of January (for example DOGE +36% here or SOL +20% here etc) but something got in my way …
$BTC Taken some partial profit on this perp long at $99660. Nice 10% move captured. Not turning bearish, just securing some profit. Spot is untouched.
We probably won't see much action in the markets till next Monday (20th Jan). Most of us were anticipating a strong rally leading into Trump presidency. And since majority can never win we topped a month+ prior and down significantly (altcoins). Anyway, most damage is done and you just have to hope orange man pumps our bags.
$XRP With XRP almost certainly going to attempt to breakout - be wary of a potential breakout fail leading to swing failure (deviation) pattern. Notes on the chart. https://www.tradingview.com/x/45uqB3fU/
Showing the 12 most recent of 18 posts we hold for @edwardmorra_btc. 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
Citation-graph rank — 516,785 of 1,481,217entries 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.
Forward network
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.
Mentions
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.
Cite this entry
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“Edward Morra” (@edwardmorra_btc), 6,629 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/edwardmorra_btc.
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.