옆집 순이할매도 알고있던 cap상장

Channel
레오의 AI/코딩/트레이딩/아비트라지
@leo_autotrading
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,120subscribers
+22 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 | -1003144759147 |
|---|---|
| Type | Channel |
| Username | @leo_autotrading |
| Created | Between 1 September 2025 and 30 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/leo_autotrading |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 01:58 | 1,120 | +2 |
| 12 Aug 2026, 12:44 | 1,118 | +8 |
| 9 Aug 2026, 07:51 | 1,110 | +12 |
| 6 Aug 2026, 12:19 | 1,098 | no change |
| 6 Aug 2026, 03:05 | 1,098 | first reading |
Engagement
20 posts held, back to 3 August 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 27.0%
- avg views ÷ 1,120 subscribers
- Avg views / post
- 303
- 20 posts measured
- Reaction rate
- 0.277%
- reactions ÷ views · ER floor
- Posts in window
- 20
- of 20 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. It is computed over the 5 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (3 August 2026 – 6 August 2026) |
| Views total | 6,050 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 12:19 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.
Reaction mix
4 reactions across 4 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 100.0% |
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 5 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 4reactions 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 3 August 2026 to 6 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.
Recent posts
[거래] 캡(CAP) 신규 거래지원 안내 (KRW, BTC, USDT 마켓) 🔗 공지사항 확인하기
저는 전업도 아니고 고수도 아니지만 플레이할 수 있는 범위가 넓어지니 이런글도 한번씩 정독하면 좋을 것 같습니다... 점점 원상따리도 먹을게 없고 사실상 매매의 영역으로 가는듯 해서 이런거라도 파먹을 수 있으면 한입이라도 해보면 좋을 것 같습니다요...
❤1
Posted without readable text
Posted without readable text
🚨 npm 공급망 공격 발생 - 440개 이상 패키지 감염 (누적 다운로드 20억+) OX Security에 따르면 Shai-Hulud 캠페인으로 440개 이상의 npm 패키지가 악성 코드에 감염됐으며, 영향 범위는 월간 누적 다운로드 20억 건 이상으로 추정됩니다. (TechRadar) 감염된 패키지를 설치하면: GitHub 토큰, npm 토큰, AWS/GCP/Azure 등 클라우드 자격증명 탈취 CI/CD 환경의 시크릿 및 환경변수 탈취 탈취한 토큰으로 GitHub·npm 계정을 이용해 추가 확산 일부 변종은 토큰을 강제로 폐기하면 시스템 파일을 삭제하는 와이퍼 기능까지 포함 (Akamai) 특히 Keyv와 Cacheable 생태계 등 많은 프로젝트에서 사용하는 라이브러리가 포함되어 있어 직접 설치하지 않았더라도 의존성(Depende…
Posted without readable text
디파이 이거 끝낫다고 생각햇는데, 븐브체인 팬케잌에서 미주디파이 이거 의외로 괜찮은거 같음. btcfi 하는거보다 훨씬 가성비 잘나오는듯. spyb 같은건 비트보다 훨씬 우상향 성격이 강해서, 범위만 잘잡으면 기존 디파이 파머들에게 난이도는 굉장히 낮을듯.
점점 AI들이 장기실행 혹은 FDS처럼 스스로 판단해서 작업을 이어나가는 방식으로 바뀌고 있는데, 그만큼 초기에 AI들에게 전달하는 프롬프트(요구사항, 예외상황 등등)을 얼마나 꼼꼼하게 잘 작성하냐가 앞으로 점점 더 중요해질 것 같다는 생각. 이게 AI가 너무 모든것을 알고있기에 생기는 문제같기도 한것 같은데 예를 들어 "해운대"라는 단어를 봤을때 누군가는 지역, 누군가는 영화제목, 누군가는 집근처 횟집 이름이 생각날 수 있음. "해운대 보러가는 길 알려줘" 라고 하면 영화 해운대를 보러간다는건지, 진짜 부산 해운대를 놀러간다는건지 애매한 상황들이 발생함. 이것이 개인화된 Context를 사람은 당연히 가지고 있기때문에 위와 같은 상황이 생겨서 알잘딱하게 이해할 수 있지만 AI는 저중에 무엇을 말하는것인지 모르기 때문에 자기가 생각한 가장…
❤1
오픈AI, 2~3개월 내 AI 활용 방식은 또 한 번 진화 최근 내가 보고 있는 결과들을 보면, Codex는 AI를 활용하기 위한 훌륭한 실행 환경(harness)이라는 점이 꽤 분명해지고 있습니다. 하지만 2~3개월만 지나면 지금의 Codex조차 원시적으로 보일 것입니다. 우리는 최첨단 AI를 사용하는 방식이 또 한 번 크게 진화하는 변곡점을 앞두고 있습니다. 차세대 모델은 더 이상 노트북 하나만으로는 충분하지 않습니다. → 차세대 모델 Astra와 같은 장기 실행 AI를 중심으로, AI 활용 방식이 일회성 질의응답에서 자율 작업 에이전트 중심으로 진화할 것임을 시사 https://t.me/Samsung_Global_AI_SW
오랜만에 하는 TGE 상장 1. TGE 상장의 정석대로 dex 뜨자마자 120m 정도에서 긁음 2. 생각 이상으로 잘 가서 150m 정도에 다 팖 3. Legion 세일 물량 떨어져서 가격 레운 4. 다시 주워볼 만하다 생각해서 평단 125m 맞춰서 줍고 업비트 보냄 5. 135m (192원~194원)에 매도 원래 제 TGE 상장 가이드라인은 dex 뜨자마자 매수하고 대가리 깨고 업비트 보내서 파는 건데 이번에는 처음 샀을 때 꽤 잘 오르고, 장도 안 좋아서 그냥 따리 한 셈 치고 그냥 팔았네유 다시 살 기회 준 건 운이 좋았던 거긴 한데, 지금 같은 장에는 업비트 보내기 전에 파는 것도 나쁘지 않은 듯듯 맥모닝 gud
❤1
바낸 알파에서 샀으면 개인ㅇ지갑을 반드시 거쳐라 아니면 돈이 공중에서 사라진다
Showing the 12 most recent of 20 posts we hold for @leo_autotrading. 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 — 21,762 of 1,481,346entries 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.
@blockschool · 4692 posts바베레토의 코인 ALL-ROUND
@baberetoallround · 1,1601 postBMT 파라다이스
@BMTube · 13,5261 post주식과 코인 샛별이
@BtcNews_Venus · 951 post크립토다이어리
@c_ryptodiary · 7,7651 post코인맵핵 🎈
@centurywhale · 16,7721 post츄린이
@churin0329 · 9,5281 post코인왕 ( 공지방 ◇ 에어드랍 )
@Coin_Airdrop_King · 43,8921 post따라하면 돈버는 억까인생 근성코 일기장
@coinking77777 · 5,8471 post크립토 폴 유
@cryptoforu12 · 7,8501 postCrypto 팬더 공지방🦅
@cryptopandann · 16,5691 post크립토 스패니얼
@CryptoSpaniel · 10,1481 post싸이버트럭
@cybertruck666 · 10,4711 post이편한코인 채널❤️
@ebtcoin2 · 1531 post돈미새 윾수
@eksoo_announce · 1,4551 post느낌좋은금융마스터포럼
@feelgoodforum · 291 post절대 펖덱에 돈을 녹이지마
@forfreere · 5211 post꿀프티 (세상 억까..) 공지방
@friedsquid26 · 10,5891 post곰디의 알고(Gomdi's Algo)
@gomdi_insight · 981 post공남은 합니다
@gongnam12 · 5,2861 postBased로 졸업하고 싶은 Leo
@hleoann · 8531 post훈토는 소액투자자
@Hoon_Pto · 681 post쉬었음청년 집가고싶다
@Iwanttogohome09 · 5,0761 postZi존파워잼민
@jammin0720 · 3,5641 post저스트코인
@JUSTCRYT · 2,9081 post영우의 크립토로 백억벌기
@kwakCrypto · 3,7181 post리암의 코인공방
@liambitcoin · 4,6061 postобезяна на коде
@megacodder · 271 post눈나 일기장🦞
@mylilttlediary · 2581 postMYU's Research (AI & WEB3)
@myu_moonyu · 7,3621 post하늘고마의 온라인 폐지줍기
@officialskygoma · 2,3921 postPAIGU - Pagu's AI Diary
@paigudiary · 551 post판판펀치
@pannpunch · 3,2521 post픽시의 스터디카페🔮🤍
@pixpot · 4,5881 post세나 리서치
@ResearchSena · 14,2951 postSally's law
@sallyslaw79 · 1441 post약국
@sidejobvip · 2,0231 post3GUYZ
@threeguyz · 591 post알쓸신잡
@UselessKn · 1,6011 post
Republishes
Channels on the register whose posts this channel has forwarded.
@pannpunch · 3,2523 posts캘빈의 감금원
@c4lvinlocked · 2,7551 post크립토메이지
@cryptocurrencymage · 9,2631 postPache Punch
@pachepunch · 2,9821 post김피카썬더볼트
@Pika_Kim · 1,6321 post라오니()
@Raoni1 · 15,1861 post[삼성 이영진] 글로벌 AI/SW
@Samsung_Global_AI_SW · 10,7821 post업비트 Upbit 공식 텔레그램
@upbit_news · 71,4391 post부자가되고싶어요
@ZzaZzaYo · 1341 post
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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“레오의 AI/코딩/트레이딩/아비트라지” (@leo_autotrading), 1,120 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/leo_autotrading.
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.