20 Apr 2026, 08:26 UTC33 viewsread 12 August 2026
https://t.me/+xZClj1qv73swODZk
Channel
MarketMaker Notes
@market_maker_notes
On this record: Growth · Engagement · Posts · Cite this entry
5subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003234126050 |
|---|---|
| Type | Channel |
| Username | @market_maker_notes |
| Created | Between 1 October 2025 and 30 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 29 August 2026 |
| On Telegram | t.me/market_maker_notes |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 10:13 | 5 | -1 |
| 12 Aug 2026, 22:46 | 6 | no change |
| 7 Aug 2026, 17:44 | 6 | first reading |
Engagement
20 posts held, back to 30 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 April 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
19 Nov 2025, 00:12 UTC13 viewsread 12 August 2026
Security assumptions reduced to hash functions XMSS requires only that the underlying hash function be secure (pre-image and second-preimage resistance). It does not rely on factoring or discrete log problems. Forward security and one-time signatures By design, XMSS uses a finite set of one-time keys; compromise of one key does not allow forging signatures for other indices. This property limits damage from local key…
19 Nov 2025, 00:12 UTC12 viewsread 12 August 2026
Stateful: there is a finite number of signatures per keypair, each index must be used only once. This complicates implementation but greatly simplifies the security analysis. XMSS and its multi-tree variant XMSS-MT have been standardized specifically to provide post-quantum digital signatures that can be deployed today, at the cost of larger signatures and more complex key management. 7. Quantum-resistant cryptocurre…
19 Nov 2025, 00:12 UTC12 viewsread 12 August 2026
1. Introduction: why quantum computing is a real threat to cryptocurrencies Modern cryptocurrencies – Bitcoin, Ethereum and most altcoins – rely on public-key cryptography based on problems like integer factorization (RSA) and discrete logarithms over elliptic curves (ECDSA / EdDSA). These problems are believed to be hard for classical computers, but they are not hard for a sufficiently powerful quantum computer. Sho…
19 Nov 2025, 00:12 UTC10 viewsread 12 August 2026
At present (late 2025), no such machine exists, and even the most ambitious roadmaps (IBM, Google, others) are talking about hundreds of logical qubits around the late 2020s, not thousands. 4. Time horizon and “harvest now, decrypt later” (HNDL) Even if we assume that a crypto-breaking quantum computer will not exist until the 2030s or 2040s, this does not eliminate the risk. There is a well-recognized threat model: …
19 Nov 2025, 00:12 UTC41 viewsread 12 August 2026
Quantum Resistant Ledger (QRL) is one of the few live blockchains that use XMSS at the core consensus layer from genesis, avoiding legacy ECDSA keys and providing a ledger whose entire history is structured to be post-quantum-secure under standard assumptions. For a general audience, the key message is: Quantum computing does not destroy cryptocurrencies today, but it forces a long-term transition to post-quantum cr…
19 Nov 2025, 00:12 UTC97 viewsread 12 August 2026
High-quality technical overview: https://medium.com/@adnanmasood/quantum-sundays-9-q-day-countdown-quantum-threats-to-blockchain-cryptography-and-the-strategic-cb3a137ee1bd Critical Review of Quantum Marketing Claims “Bitcoin will be hacked in 2 years” — debunking analysis: https://coinmarketcal.com/pt/news/bitcoin-will-be-hacked-in-2-years-and-other-quantum-resistant-marketing-lies --- 5. Current State of Qua…
13 Nov 2025, 06:30 UTC13 viewsread 12 August 2026
Photo
where the first line of my bot 😃
13 Nov 2025, 06:26 UTC23 viewsread 12 August 2026
Photo
Photo, posted without a caption
7 Nov 2025, 00:46 UTC27 viewsread 12 August 2026
Photo
Today’s session ended with a “near breakout”… but not quite 😏 They still haven’t realized — it’s not about the volume. 7.11.2025 2:15 la capitulation
5 Nov 2025, 15:16 UTC21 viewsread 12 August 2026
Referal link https://www.pionex.com/en/signUp?r=0v1AhDwjUtw
5 Nov 2025, 14:15 UTC18 viewsread 12 August 2026
05.11.2025 3:17 посмотрите график BTC. This is the Start
Showing the 12 most recent of 20 posts we hold for @market_maker_notes. 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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“MarketMaker Notes” (@market_maker_notes), 5 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/market_maker_notes.
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.