Telegram RegisterThe public register of Telegram

Channel

SoSo 정보 공지

@sosoinfo

On this record: Growth · Engagement · Posts · Citations · Cite this entry

1,815subscribers

-6 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001123615736
TypeChannel
Username@sosoinfo
Created25 September 2017measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/sosoinfo

Growth

1,8151,8211,8186 August 2026 — 1,821 subscribers6 August 2026 — 1,821 subscribers9 August 2026 — 1,816 subscribers12 August 2026 — 1,815 subscribers6 August 202612 August 2026
4 measurements spanning 6 days, net -6. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,814–1,822 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 09:071,815-1
9 Aug 2026, 09:511,816-5
6 Aug 2026, 12:331,821no change
6 Aug 2026, 12:271,821first reading

Engagement

34 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
5.73%
avg views ÷ 1,815 subscribers
Avg views / post
104
34 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
34
of 34 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held34 (4 August 20267 August 2026)
Views total3,538
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:28 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.

Recent posts

7 Aug 2026, 16:28 UTC13 viewsread 7 August 2026

⚠️ BTC 페이 서버, "취약점 해킹 진행 중... 자금 손실 가능성" 오픈소스 암호화폐 결제 프로세서 BTC 페이 서버가 취약점 발견으로 해킹 공격이 진행 중이라고 경고했다. BTC 페이 서버는 공식 X를 통해 자금 손실이 발생할 수 있다며, 즉시 서버 v2.4.2로 업데이트하거나 서버를 종료해 해킹을 방지하라고 권고했다. ✍️ 원문 한 번 보길. 출금 잠시 미루는 거 권장. https://coinness.com/news/1165031

7 Aug 2026, 14:06 UTC44 viewsread 7 August 2026

₿ 마라 홀딩스, 726 BTC 매도…총 35,577 BTC 보유 중 상장 비트코인 채굴 기업 마라 홀딩스($MARA)가 726 BTC를 매도했다. 현재 마라 홀딩스의 총 비트코인 보유량은 35,577 BTC다. ✍️ 채굴 기업 매도, 단기 시장에 소폭 매도 압력으로 작용할 수 있음. @bitcoin

7 Aug 2026, 12:31 UTC61 viewsread 7 August 2026

🌐 미국 7월 비농업 부문 고용이 전월 대비 2만 3천 명 감소했다. 이는 시장 예상치인 8만 명 증가를 크게 밑도는 수치다. ✍️ 고용 지표 둔화, Fed 금리 인하 기대감 높일 수 있다. @WalterBloomberg

7 Aug 2026, 11:53 UTC56 viewsread 7 August 2026

₿ 암호화폐 / BTC 콜드카드 공동 창업자가 1.3억 달러 해킹 피해 발생 후 X 게시물을 삭제하고 있습니다. 콜드카드 제조사 코인카이트의 공동 창업자 로돌포 노박(NVK)이 자신의 소셜 미디어 게시물을 삭제하고 있습니다. 해커들이 지난주 콜드카드 하드웨어 지갑의 취약점을 악용하기 시작한 이후 1.3억 달러(2,055 BTC) 이상이 탈취되었으며, 피해는 계속되고 있습니다. 노박은 지난 5년간 작성했던 일부 게시물을 삭제했으며, 여기에는 2024년 11월 블록클록 모조품이 "사람들의 홈 네트워크에 백도어가 될 수 있다"고 경고한 내용도 포함됩니다. 비트코인 개발자 피터 토드는 이 삭제를 포착했습니다. 코인카이트가 웹사이트에서 콘텐츠를 삭제했다는 의혹도 제기되었으나, 회사 측은 이에 대해 반박했습니다. 노박은 콜드카드 실패에 대한 사과문

7 Aug 2026, 09:51 UTC72 viewsread 7 August 2026

₿ 암호화폐 / BTC 콜드카드 해킹 사태 이후 지난 일주일간 장기 보유자(LTH) 주소에서 약 21만 BTC가 이동했다고 코인데스크가 보도했다. 이는 글래스노드 데이터 기준 지난해 12월 이후 최대치다. LTH 보유량은 사건 전 약 1,500만 BTC에서 현재 1,470만 BTC로 감소했다. 코인데스크는 이를 해킹 위험이 있는 기존 지갑에서 새 지갑으로 BTC가 이동하는 양상으로 분석했다. 대규모 매도보다는 규제 수탁기관이나 현물 비트코인 ETF로 보관처를 바꾼 것으로 보인다고 덧붙였다. 같은 기간 미국 현물 BTC ETF에는 약 7억 5,400만 달러가 순유입됐으며, 대부분 블랙록 IBIT로 유입됐다. ✍️ 해킹 리스크에 따른 지갑 교체. 매도 압력보다는 장기 보유자들의 포트폴리오 재정비로 해석. https://coinness.c

7 Aug 2026, 08:15 UTC79 viewsread 7 August 2026

₿ 암호화폐 지난 7월 암호화폐 도난 피해액이 2억 4,740만 달러(약 3,400억 원)를 기록하며 올해 두 번째로 피해가 컸던 달로 나타났다. 특히 콜드카드 익스플로잇으로 최소 1억 달러 상당의 비트코인이 탈취된 것이 가장 큰 사건이었다. 이 외에도 본조 렌드, 세컨드파이, AFX, 베루스 이더리움 브릿지 등 여러 플랫폼에서 해킹이 발생했다. ✍️ 또 폰지 의혹. 지갑 단속 시간. https://whale-alert.io/stories/84d801fc206cfc/July-crypto-thefts-hit-2474-million-led-by-a-Coldcard-exploit-that-stole-at-least-100-million-in-Bitcoin

7 Aug 2026, 07:50 UTC84 viewsread 7 August 2026

₿ 암호화폐 트래블룰 금액 기준을 폐지하는 특정금융정보법 개정안이 11일 국무회의에 상정된다. 국무회의 의결을 거치면 오는 20일부터 시행될 예정이다. 개정안은 가상자산사업자가 100만원 이상 디지털자산을 이전할 때만 정보를 제공하던 기존 규정을 바꿔, 금액과 관계없이 모든 이전 시 정보를 제공하도록 의무화했다. ✍️ 트래블룰 금액 기준 폐지, 국내 가상자산 시장 투명성 강화될 듯. https://coinness.com/news/1164985

7 Aug 2026, 02:55 UTC68 viewsread 7 August 2026
Forwarded from @upbit_news

[거래] 블록스트리트(BSB) 신규 거래지원 안내 (KRW, BTC, USDT 마켓) 🔗 공지사항 확인하기

7 Aug 2026, 02:39 UTC83 viewsread 7 August 2026
Forwarded from @BithumbExchange

[마켓 추가] 블록스트리트(BSB) 원화 마켓 추가 https://feed.bithumb.com/notice/1654365

7 Aug 2026, 02:30 UTC106 viewsread 7 August 2026

🇹🇭 태국, 2029년까지 암호화폐 양도소득세 면제 태국 재무부가 2029년 12월 31일까지 암호화폐 양도소득세를 면제한다. 이는 투자 유치와 디지털 통화 생태계 강화를 위한 조치다. 줄라푼 아몬비왓 태국 재무부 차관은 이번 면세가 태국의 경제 잠재력을 높이고 태국 기업가들이 글로벌 무대에서 성장할 기회가 될 것이라고 밝혔다. 다만, 면세 혜택은 태국 증권거래위원회(SEC)가 규제하는 현지 라이선스 거래소, 브로커, 딜러를 통한 거래에만 적용된다. ✍️ 태국, 자국 거래소 유도하며 암호화폐 시장 활성화 노림. https://washingtondc.thaiembassy.org/en/content/thailand-waives-capital-gains-tax-on-crypto-for-fi?cate=64c93aa8fd9aa7078962929

7 Aug 2026, 02:09 UTC61 viewsread 7 August 2026
Forwarded from @upbit_news

[거래] 카미노파이낸스(KMNO) KRW 마켓 디지털 자산 추가 🔗 공지사항 확인하기

7 Aug 2026, 00:45 UTC97 viewsread 7 August 2026

₿ 비트코인 채굴 기업, BTC 매도 지속 비트코인 채굴 기업들이 BTC를 매도하고 있다. 마라(MARA)는 36,303 BTC(약 23억 4천만 달러)를 보유 중이며, 10시간 전 NYDIG에 200 BTC(약 1,286만 달러)를 입금했다. 라이엇 플랫폼즈(Riot Platforms) 역시 10시간 전 NYDIG에 381 BTC(약 2,451만 달러)를 추가 입금하며 BTC 매도를 이어갔다. ✍️ 채굴 기업 매도 압력, 단기 BTC 변동성 확대 가능성. https://arkm.com/explorer/entity/mara-pool

Showing the 12 most recent of 34 posts we hold for @sosoinfo. 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 — 1,056,440 of 1,345,403entries 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“SoSo 정보 공지” (@sosoinfo), 1,815 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/sosoinfo.

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.