#вакансия #blockchain #crypto #web3 #blockchainanalytics #KYT #SQL #lead #fulltime #remote #удаленно 🔎 Ведущий специалист по разметке блокчейн-адресов (удалённо) 📌 О компании Продуктовая компания в области блокчейн-аналитики и KYT ищет специалиста, который возьмёт на себя направление разметки адресов: биржи, санкции, взломы, мошенничество, мосты и другие сущности. 🎯 Задачи — Поставить цели и метрики разметки (по…

Channel
КРИПТО - ВАКАНСИИ | Работа в Web3
@crypto_vacancy_web3
On this record: Topic · Growth · Engagement · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
21,427subscribers
-5,246 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001581175740 |
|---|---|
| Type | Channel |
| Username | @crypto_vacancy_web3 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/crypto_vacancy_web3 |
Topic
Job listings — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 20:58 | 21,427 | -162 |
| 13 Nov 2026, 09:17 | 21,589 | -35 |
| 10 Nov 2026, 23:39 | 21,624 | -87 |
| 9 Nov 2026, 09:17 | 21,711 | -100 |
| 8 Nov 2026, 00:15 | 21,811 | -104 |
| 6 Nov 2026, 20:07 | 21,915 | +777 |
| 5 Nov 2026, 17:10 | 21,138 | -84 |
| 4 Nov 2026, 18:09 | 21,222 | -32 |
| 3 Nov 2026, 21:26 | 21,254 | -20 |
| 2 Nov 2026, 20:38 | 21,274 | -7 |
| 1 Nov 2026, 22:06 | 21,281 | -6 |
| 1 Nov 2026, 01:36 | 21,287 | -4 |
| 30 Oct 2026, 23:49 | 21,291 | -11 |
| 30 Oct 2026, 03:09 | 21,302 | -3 |
| 28 Oct 2026, 01:20 | 21,305 | -4 |
| 27 Oct 2026, 04:36 | 21,309 | -10 |
| 26 Oct 2026, 03:17 | 21,319 | -2 |
| 25 Oct 2026, 04:08 | 21,321 | -194 |
| 24 Oct 2026, 02:37 | 21,515 | +167 |
| 23 Oct 2026, 01:51 | 21,348 | first reading |
Engagement
39 posts held, back to 2 July 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 100 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 15.6%
- avg views ÷ 21,427 subscribers
- Avg views / post
- 3,340
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 39 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.
| Window | Rolling 30 days · latest post in window 9 November 2026 |
|---|---|
| Posts held | 39 (2 July 2026 – 9 November 2026) |
| Views total | 6,680 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 16:37 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
Telegram’s own ‘edited’ marker: 2 of 2 posts held from the last 30 days (100.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
#вакансия #контекстолог #marketing #yandexdirect #googleads #gaming #igaming #fulltime #remote #удаленно 🎯 Требуется Контекстолог (Яндекс Директ / Google Ads) 📌 О компании Развиваем собственный Gaming / iGaming-проект в индустрии CS2. Платформа находится на финальной стадии разработки. Ищем опытного специалиста по контекстной рекламе для запуска, продвижения и масштабирования проекта. 💼 Что нужно делать — Настра…
#вакансия #bizdev #bdm #businessdevelopment #crypto #fulltime #remote #удаленно #affiliate #sales 💼 Требуется BizDev Manager У нас есть трафик и объёмы. От тебя - прямые рекламодатели, выгодные условия и новые сделки. 🎯 Твои задачи: — Поиск прямых Crypto-рекламодателей — Продажа и масштабирование объёмов — Переговоры по ставкам, GEO и лимитам — Тестирование и развитие партнёрств 🧠 Кого ищем: — Опыт BizDev / Aff…
#вакансия #bizdev #businessdevelopment #bdm #headofpartnerships #fintech #sales #partnerships #fulltime #remote 🤝 Требуется BizDev / Head of Partnerships 📌 О нас Swapster — быстрорастущий финтех-стартап, объединяющий традиционный банкинг, криптовалюту и инвестиционные инструменты. И мы ищем БД, который не ждет лидов, а сам ищет их и закрывает сделки. Нужен сильный кандидат из финтеха — тот, кто понимает индустрию,…
#резюме #projectmanager #fintech #crypto #cryptopayments #web3 #b2b #remote #удаленно| 👤 Ищу работу на позиции Project Manager в крипто или финтех-проекте Меня зовут Дина Касимова. У меня 2 года опыта работы Project Manager. Работаю на стыке бизнеса, разработки и операционной команды: собираю требования, превращаю их в задачи, координирую выполнение и участвую в проверке результата. 💼 Мой опыт: — Вела проектные з…
#вакансия #aml #kyt #compliance #crypto #blockchain #аналитик #fintech #investigations #remote #web3 🔎 AML-аналитик Криптовалюты / KYT 📌 О компании Мы - компания, разрабатывающая платформу блокчейн-аналитики и KYT для комплаенс-команд и специалистов по расследованиям. Ищем AML-аналитика, который знает эти инструменты из ежедневной практики и поможет сделать продукт удобнее и надёжнее. 💼 О роли Ваш опыт работы с…
#вакансия #арбитраж #crypto #trading #fintech #трейдинг #криптовалюта #аналитика #remote #удаленно 📊 СПЕЦИАЛИСТ ПО АРБИТРАЖНЫМ ОПЕРАЦИЯМ 📌 О направлении Fintech-проект развивает направление межбиржевой торговли и анализа цифровых активов. Специалист работает с котировками на централизованных торговых площадках, отслеживает ценовые расхождения между ними и оценивает возможность проведения арбитражных операций. Раб…
#вакансия #сценарист #screenwriter #video #youtube #crypto #trading #parttime #remote #удаленно 🎬 Сценарист на лонг ролики YouTube — Crypto / Trading Качаем YouTube в нише трейдинга и Forex. Ищем супер заинтересованного человека в теме трейдинга и разбирающегося в ютубе, опыта в создании 5-10 роликов за последние 3-6 месяцев будет достаточно 🎯 Что нужно будет делать: — Делать ролики под поисковые запросы, тоесть …
#вакансия #director #executivedirector #manager #coo #crypto #fulltime #remote #удаленно 💼 Менеджер / Исполнительный директор 🎯 Обязанности: — Управление операционной деятельностью обменного бизнеса, включая соблюдение стандартов и правил международной работы — Разработка и внедрение стратегий масштабирования бизнеса — Ведение переговоров с партнерами и клиентами для расширения бизнеса — Управление командой, включ…
#вакансия #криптоарбитраж #арбитраж #трейдинг #crypto #trading #junior #аналитика #remote #удаленно 💸 Ищем работников в команду крипто-арбитража 📌 О компании: AUREX — инвестиционная компания, специализирующаяся на крипто-арбитраже и торговых стратегиях. Ищем начинающих специалистов, которые хотят с нуля разобраться в криптовалютном рынке, арбитраже и трейдинге и развиваться вместе с командой. 🎯 Что предстоит дел…
#вакансия #архитектор #crypto #web3 #blockchain #wallet #dotnet #ethereum #bitcoin #сербия 🚀 Архитектор некастодиального криптокошелька Мы строим финансовую платформу, объединяющую фиат и крипту. В центре экосистемы — некастодиальный кошелёк, где ключи хранятся у пользователя. Ищем архитектора, который возглавит техническое направление и поможет масштабировать продукт до миллионов пользователей 🎯 Задачи: — Проект…
#вакансия #marketingmanager #smmmanager #smm #crypto #fulltime #remote #удаленно #outreach #web3 📣 Crypto Marketing Manager / SMM & Outreach Specialist Мы - fintech-проект в сфере crypto payments. Развиваем платежную инфраструктуру для бизнеса и ищем маркетолога в команду на долгосрочное сотрудничество. 🎯 Что нужно делать: — вести LinkedIn, X, Telegram и другие каналы; — готовить контент на английском; — искать к…
Showing the 12 most recent of 39 posts we hold for @crypto_vacancy_web3. 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.
Posts recorded as deleted after publishing
We recorded 1 post on @crypto_vacancy_web3 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 9 November 2026
- Most recent seen missing
- 9 November 2026
- Median time before seen missing
- 44 days
- Seen missing in the last 30 days
- 1
Mentions
Named by 3 registered channels — 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@crypto_vacancy_web3 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 8 posts, 8 August 2026 – 20 August 2026
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 November 2026 — this entry's latest reading, not the date you are reading this.
“КРИПТО - ВАКАНСИИ | Работа в Web3” (@crypto_vacancy_web3), 21,427 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/crypto_vacancy_web3.
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.