Channel
@cryptospac3
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
4subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001148323692 |
|---|---|
| Type | Channel |
| Username | @cryptospac3 |
| Description | Hand-picked news from the CRYPTOSpace, that are worth spreading! |
| Created | Between 1 May 2017 and 31 July 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/cryptospac3 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 05:32 | 4 | no change |
| 7 Aug 2026, 09:43 | 4 | first reading |
20 posts held, back to 17 June 2021 — 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 27 October 2022. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 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.
As promised, we've launched the ability to buy Telegram usernames on a dedicated platform – Fragment. Auctions for the most valuable usernames are already live, so make sure to check it out. In a few days, we will also introduce the ability for users to sell their existing usernames on Fragment. For the first time in the history of social media, a fair, transparent market for usernames is established. Finally people…
Bitcoin exchange balances trend back to historic lows as BTC withdrawals resume in January BTC is coming off trading platforms again as prices dip into Q1 2022. https://ct.com/a7yj
https://hackernoon.com/how-to-transfer-tokens-between-the-worlds-leading-blockchains-r32237x8
Top 10 Decentralized Exchanges (DEX) in 2021 https://cryptonews.com/guides/top-10-decentralized-exchanges-dex-in-2021.htm
$69k Bitcoin is NOT the top. ALL bull markets have ended AFTER crossing the 2yr moving average x5. Still early
https://cointelegraph.com/news/bitcoin-on-chain-metric-suggests-2017-style-bull-run-will-continue?utm_source=Telegram&utm_medium=social
Huge 19,000 BTC outflow from Coinbase yesterday. Institutions are here and they're buying your bitcoin. Don't sell your Bitcoin to institutions. You’re gonna regret this decision and buy back higher.
VanEck has also been approved to launch Bitcoin futures ETF to trade next week. VanEck의 비트코인 선물 ETF도 승인을 받았으며 다음주에 거래가 될 것입니다. https://www.coindesk.com/business/2021/10/20/vaneck-to-join-proshares-in-launching-a-bitcoin-futures-etf/
SEC documents state that the ProShares Bitcoin Futures ETF has been approved. SEC 문서에 ProShares Bitcoin Futures ETF가 승인되었다고 명시되었습니다. https://www.sec.gov/Archives/edgar/data/0001174610/000168386321006057/f10048d1.htm https://www.nytimes.com/2021/10/18/business/dealbook/bitcoin-etf-proshares.html
Nasdaq has approved Valkyrie's Bitcoin futures ETF for trading but is currently waiting for SEC's final decision. 나스닥이 Valkyrie's Bitcoin futures ETF를 승인하였습니다. 그러나 SEC의 최종결정을 기다리고 있는 중입니다. https://www.sec.gov/Archives/edgar/data/1877493/000135445721001164/8A_Cert_BTF.pdf
There is a rumor the SEC is poised to allow the first U.S. Bitcoin futures ETF to begin trading next week according to people familiar with the matter. 루머에 따르면 관계자들이 SEC가 다음주에 비트코인 선물 ETF를 승인할 것으로 밝혔다고 알려졌습니다. https://www.bloomberg.com/news/articles/2021-10-15/bitcoin-futures-etf-said-not-to-face-sec-opposition-at-deadline?sref=PFCuwcPr
Bloomberg predicts Bitcoin Futures ETF has a 75% chance of approval in October 2021. 블룸버그는 선물기반 비트코인 ETF가 10월에 승인될 가능성을 75%로 예측하고 있습니다.
Showing the 12 most recent of 20 posts we hold for @cryptospac3. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“CRYPTOSpace” (@cryptospac3), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/cryptospac3.
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.