بات @lnp2pbot طبق اعلامیهای که چندی پیش منتشر کردند فعالیتش تا اطلاع ثانوی متوقف شد.
💔9👍3⚡2
Signed Mo Tahmasbi

Channel
@SatoshiSchool
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
6,075subscribers
-16 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001372274367 |
|---|---|
| Type | Channel |
| Username | @SatoshiSchool |
| Description | آموزش بیتکوین و بازتاب تحولات مهم جامعهی بیتکوین فارسی و انگلیسی. گلچینی از محتواهایی که بهش برمیخوریم یا تولید میکنیم. رزرو یک جلسهی دمو (نمایش خدمات) با لینک زیر: https://21stcapital.com/bitguide |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/SatoshiSchool |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @SatoshiSchool/3730 · this entry22 Jun 2026, 20:01 UTC | @irancoin/13611 Jul 2026, 07:20 UTC | 1.00 | 8 days |
| @irancoin/13725 Aug 2026, 13:38 UTC | @SatoshiSchool/3750 · this entry6 Aug 2026, 17:00 UTC | 1.00 | 27 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @irancoin | 6 (6/6 hand-verifiable sample passed) | 1.00 | 18 hours | even |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 18 comparable posts for this entry, running 22 June 2026 to 7 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @SatoshiSchool — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 02:13 | 6,075 | -8 |
| 9 Aug 2026, 05:02 | 6,083 | -7 |
| 6 Aug 2026, 04:50 | 6,090 | -1 |
| 6 Aug 2026, 03:22 | 6,091 | no change |
| 6 Aug 2026, 02:50 | 6,091 | first reading |
25 posts held, back to 22 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 9 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.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 25 (22 June 2026 – 10 August 2026) |
| Views total | 49,159 |
| Reactions total | 512 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 03:33 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.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
655 reactions across 24 posts, in 24 distinct kinds. The most used accounts for 45.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 299 | 45.6% | |
| ❤ | 160 | 24.4% | |
| 💔 | 26 | 3.97% | |
| 👎 | 22 | 3.36% | |
| 😭 | 22 | 3.36% | |
| 😱 | 16 | 2.44% | |
| 🤣 | 16 | 2.44% | |
| 🥱 | 15 | 2.29% | |
| 😎 | 13 | 1.98% | |
| 🤨 | 13 | 1.98% | |
| 👌 | 12 | 1.83% | |
| 🍌 | 7 | 1.07% | |
| 💩 | 5 | 0.763% | |
| ⚡ | 4 | 0.611% | |
| 🌚 | 4 | 0.611% | |
| 🙏 | 4 | 0.611% | |
| 🔥 | 3 | 0.458% | |
| 😁 | 3 | 0.458% | |
| 🤡 | 3 | 0.458% | |
| 🤪 | 3 | 0.458% | |
| 4 further kinds | 5 | 0.763% |
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 25 of the 25 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 693reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 25 most recent posts we hold, published 22 June 2026 to 10 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.
بات @lnp2pbot طبق اعلامیهای که چندی پیش منتشر کردند فعالیتش تا اطلاع ثانوی متوقف شد.
💔9👍3⚡2
Signed Mo Tahmasbi
چقدر شوکه کننده و غیر قابل انتظار. حدود ۹۹.۸۵٪ از هشپاور بیتکوین با بیتکوین موند. شاخه BIP-110 فقط دو بلاک استخراج کرده و الان بیش از ۸۰ بلاک عقبه. و پروندهش عملا بسته شده.
❤17😱4🔥3👌2
Signed Snz
دوستان من اشتباه میکردم. اگر چین اسپلیت شد و سکهی لوک-کوین واستون ایردراپ شد به هیچ عنوان به کسی نفروشیدش چون همون تراکنش رو شبکه اصلی هم معتبره و میتونه روی شبکه اصلی منتشر کنه و بیتکوین شما رو بگیره. در مورد replay attack تحقیق کنید. متاسفانه ازین BIP-110 آبی واسمون گرم نمیشه.
👍15❤9
Signed Snz
بیپ-١١٠ موجب اسپلیت چین شد. بیپ-١١٠ بیپ پیشنهادی لوک برای سافتفورک و اعمال محدودیت روی قابلیتهای کنونی گنجاندن داده در زنجیرهی بیتکوین بود. این ویدئو لحظهایه که بیتکوین مکانیک و چند تا از افراد سرشناس حامی بیت-١١٠ فورک شدن دو زنجیره رو به صورت زنده میبینن. نکتهی اخلاقی: این که تصور کنیم سافتفورک خوبه و هارد فورک بد تصور اشتباهیه. یه سافتفورک هم در صورت نداشتن پشتیبانی موجب چین اسپلیت (دو شاخه شدن زنجیره…
❤8👌1
Signed Mo Tahmasbi
یکی از باگ های مهمی که تو این کمپین پیدا شده مربوط به BTC Pay Server هستش که خود پروژه هم تاییدش کرده و میگه که همین الان داره ازین آسیب پذیری امنیتی سو استفاده میشه. اگه از این سرویس استفاده میکنین توصیه شده همین الان یا آپدیت کنید یا سرور رو خاموش کنید.
❤13👍1
Signed Snz
ویدیوی توضیحی از موسسه Bitcoin Policy که به زبان ساده توضیح میده چرا کلمات ریکاوری ساخته شده با کیف پولهای سخت افزاری Coldcard اینقدر ضعیف بودن که منجر به دزدیده شدن بیت کوینهای داخل اونها شدن و چرا امکان تولید اعداد تصادفی واقعی اینقدر برای امنیت مهم و حیاتی هست. 🔎 bitcoinpolicy 📍 @TechTube
❤14
Signed Mo Tahmasbi
این سید ساینر ساده که روی یه کامپیوتر چندمنظوره (رزبریپای) ساخته شده، طی همهی این سالهایی که nvk مشغول خریدن دامنه برای مسخره کردنش بوده، صد هیچ از کلد کارد جلو بوده! زمانی کلاً دیگه تحمل شنیدن صدای nvk رو از دست دادم که فهمیدم یه مشت دامنهی seedsigner خریده بود و وقتی کاربر بازش میکرد، به یه صفحهای هدایت میشد که سیدساینر رو مسخره کرده بود و به مردم نسبت به ساختن کامپیوتر air-gapped برای نگهداری بیتکوین هشدا…
❤17⚡2
Signed Mo Tahmasbi
از زیباییهای این فضا:حالا که هوش مصنوعی داره باگهای خطرناکی پیدا میکنه چندین دولوپر با تجربه جمع شدن و با کمک مالی موسسات مختلف دارن هر پروژه اپن سورس بیتکوینی که میتونن رو بررسی امنیتی میکنن. فعلا که میگن کلی باگ پیدا شده تا اینجا. https://x.com/callebtc/status/2084561246305542617?s=20
❤12😭4👍1
Signed Snz
رودلفو (NVK) کلدکارد رو از روی کدِ متنباز Trezor ساخته بود. شرکت Foundation کد کلدکارد رو برای ساخت کیف پول سختافزاری Passport فورک کرد. (این کار توی فضای متنباز کاملاً قانونی و عادیه.) رودلفو زورش گرفت و پروانهی کلدکارد رو طوری عوض کرد که رقبا دیگه نتونن از کدش استفاده کنن. اما چون نمیتونست پروانهی کد GPLی رو که از ترزور گرفته بود عوض کنه، مجبور بود اون کد رو حذف کنه و به جاش کد جدید بنویسه. توی همین فرآی…
❤15👍5🙏3
Signed Mo Tahmasbi
جمعا برآوردها نشون میده ۱۰۰ میلیون دلار سرقت شد و دیگه سرقتها خیلی کم تعداد شدن.
💔17❤5😭1
Signed Snz
شانس آوردید کلد کارد گرونفروش بود و کریپتوهای دیگه رو ساپورت نمیکرد واسه همین ایران زیاد وارد نمیشد.
👍18🤣16🤪3😁2
Signed Snz
اینکه چند وقته غر میزنم کارای مهمتری داریم که ول کردیم و چسبیدیم به اسپم یکیش همین موضوع ساده کردن و امن کردن حضانت بیتکوین بود. ایدهای که میگه بیتکوین رو دیگه نباید آپگرید کرد بر این اساس استواره که همه چیز الان درست کار میکنه و اشخاص عادی میان سه تا والت سخت افزاری میخرند و بعد با تاس سید فریز درست میکنن و در سه جای مختلف ذخیره اش میکنن. اگه یکم با ادمای عادی صحبت کنن متوجه میشن که در توهم هستند و هرگز با این حجم…
👍31❤6👌2🥱1
Signed Snz
Showing the 12 most recent of 25 posts we hold for @SatoshiSchool. 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 — 110,904 of 1,151,006entries 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.
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.
@SatoshiSchool named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 3 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“بیتگاید” (@SatoshiSchool), 6,075 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/SatoshiSchool.
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.