Lots of thing cooking : Announcements soon https://x.com/pumatheuma/status/1966243602054713583?s=46&t=EzJ4hw_04t0kzdna-LuyUQ

Channel
Succinct Korea 공지
@Succinct_Korea_Announcement
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
281subscribers
-6 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 | -1002357277236 |
|---|---|
| Type | Channel |
| Username | @Succinct_Korea_Announcement |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/Succinct_Korea_Announcement |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 23 September 2026 and assigned it the closest of 31 fixed categories, at 45% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 22:18 | 281 | -2 |
| 6 Sept 2026, 08:15 | 283 | -3 |
| 8 Aug 2026, 08:20 | 286 | no change |
| 8 Aug 2026, 00:47 | 286 | -1 |
| 7 Aug 2026, 14:59 | 287 | first reading |
Engagement
20 posts held, back to 1 July 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 page of 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 12 September 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 5s
- Average length
- 5s
Measured directly from 1 video 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.
Reaction mix
21 reactions across 9 posts, in 4 distinct kinds. The most used accounts for 76.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 16 | 76.2% | |
| 🔥 | 3 | 14.3% | |
| 👎 | 1 | 4.76% | |
| 🥰 | 1 | 4.76% |
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 9 of the 20 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 21 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 1 July 2025 to 12 September 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
Galxe가 Succinct Prover Network로 마이그레이션했습니다. Galxe의 래플은 이제 최고 수준의 성능과 비용 효율성을 제공하는 세계적 수준의 프로버들이 처리하게 됩니다. https://x.com/SuccinctLabs/status/1963663970612760858
👎1
Succinct Proofspace guild 오픈 Succinct가 $PROVE 스테이커들을 위한 프라이빗 길드를 만들었습니다. $PROVE 장기 보유자, 빌더, 그리고 Succinct의 미래를 함께 만들어가는 작가들을 위한 공간이라고 하며 현재 참여기준은 5000 $PROVE 이상을 스테이킹 해야 참여가 가능합니다! 해당되시는 분께서는 https://guild.xyz/proofspace 에서 참여하시면 됩니다.
Succinct, Arbitrum의 zk도입을 위해 1년간독점 파트너십 Succinct co-founder Uma roy는 Succinct Labs와 Offchain Labs이 1년간 독점 파트너십을 체결하여 Arbitrum 롤업 스택에 ZK 기술을 도입한다고 발표했습니다. 해당 트윗은 이더리움 파운더 비탈릭도 리트윗 할만큼 Succinct의 영향력이 점점 더 커지는 것 같아 앞으로의 행보가 너무 기대가 되네요. Uma roy 공지 트윗
Hibachi, $PROVE 스테이커들에게 추가보상 지급 Succinct와 파트너 관계인 Perp DEX Hibachi가 $PROVE 스테이커들에게 더 많은 거래보상을 지급한다고 하니 스테이킹 하신분들중 Hibachi를 이용해보실분은 참고하시면 좋겠습니다 https://x.com/succinctfnd/status/1954998296541532192?s=46&t=EzJ4hw_04t0kzdna-LuyUQ
$PROVE가 코인원에도 상장합니다! 입출금 예정 일정: - 입금 오픈: 2025년 8월 6일(수) 17:00 (KST) - 출금 오픈: 2025년 8월 7일(목) 12:05 (KST) 거래 예정 일정: - 매도 오픈: 2025년 8월 7일(목) 12:00 (KST) - 매수 오픈: 2025년 8월 7일(목) 12:05 (KST) - 시장가 예약가 오픈: 2025년 8월 7일(목) 14:05 (KST) 이로써 한국 코인거래소에는 다 상장했네요. (고팍스는요? 라고 질문X)
❤3
😀Succinct, 빗썸 상장
😀 Succinct, $PROVE LIVE https://claim.succinct.foundation/
Succinct $PROVE 클레임기간이 마감됐습니다! 클레임되지 않은 물량은 향후 스테이킹 하신분들께 인센티브로 사용됩니다. https://x.com/succinctfnd/status/1952082038170763435?s=46&t=EzJ4hw_04t0kzdna-LuyUQ
😀 블록미디어에서 Succinct co-founder Uma roy와 단독 AMA를 진행하였습니다. TGE를 앞둔 지금 Succinct가 어떤 프로젝트인지 다시 한번 알아가는 중요한 내용들이 많으니 모두들 한번씩 읽어보시는 걸 추천 드립니다. https://www.blockmedia.co.kr/archives/952835
😀 Succinct 에어드랍 등록 오픈 https://register.succinct.foundation/
The Succinct Proveys 놀라운 Succinct 커뮤니티의 6개월간의 성과를 기념하는 한정 이벤트를 진행합니다. 그동안 커뮤니티 활성화를 위해 노력해주셨던 분들중 가장 눈에 띄게 활동해주신 기여자를 뽑습니다! 아래링크에서 투표를 진행해주시면 됩니다. (투표는 24시간후 부터 진행됩니다.) https://vote.prove.rs/vote
❤1
Showing the 12 most recent of 20 posts we hold for @Succinct_Korea_Announcement. 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.
Forward network
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.
Mentions
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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Succinct Korea 공지” (@Succinct_Korea_Announcement), 281 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/Succinct_Korea_Announcement.
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.