this month Jaya Talent celebrates 3 years 🎉💜 we offered 20 career consultation chats for the anniversary - and completed them all ✨ for those who are planning to change career in the next few months, not getting interviews or visibility, and need help with warm intros 🎁6 days left in October - so we are opening 6 more additional slots at the same celebration price: $75 instead of $500 🎁to lock your slot, dm Anna …

Channel
Engineering · Rust / Solidity / Smart Contracts | Job Aggregator by Jaya Talent
@web3devs3
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
304subscribers
-5 since we began measuring on 26 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002705695744 |
|---|---|
| Type | Channel |
| Username | @web3devs3 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 October 2026 |
| Last confirmed live | 18 November 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 18 November 2026 |
| On Telegram | t.me/web3devs3 |
Topic
Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 18 November 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 |
|---|---|---|
| 18 Nov 2026, 11:16 | 304 | -4 |
| 9 Nov 2026, 01:07 | 308 | -1 |
| 26 Oct 2026, 05:22 | 309 | no change |
| 26 Oct 2026, 04:39 | 309 | first reading |
Engagement
11 posts held, back to 21 October 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 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 5.59%
- avg views ÷ 304 subscribers
- Avg views / post
- 17.0
- 6 posts measured
- Reaction rate
- 4.00%
- reactions ÷ views · ER floor
- Posts in window
- 6
- of 11 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 1 of 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 24 October 2026 |
|---|---|
| Posts held | 11 (21 October 2026 – 24 October 2026) |
| Views total | 102 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 26 Oct 2026, 05:22 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.
What this channel posts
- Video runtime
- 26s
- Average length
- 26s
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
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 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 1 of the 11 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 21 October 2026 to 24 October 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
Telegram’s own ‘edited’ marker: 0 of 6 posts held from the last 30 days (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).
Senior Inference Engineer Remote - Dubai - Abu Dhabi A unified platform for high-performance AI inference - one API to deploy and run AI models at scale, across cloud, dedicated capacity and clients' own hardware. This is the senior technical seat for AI serving. You will own the inference serving stack: prefill/decode disaggregation, continuous batching, KV-cache management, speculative decoding, MoE serving, quan…
we updated it 💜 our top headhunters in the crypto space list - 2026 edition is live want access to the full guide? dm Anna @jayatalentoffice - just write "Recruiter" inside: 🔹 Dubai headhunters in crypto 🔹 global crypto headhunters 🔹 recruitment agencies in crypto - global 🔹 recruitment agencies in crypto - Dubai based build your network in advance. not when you lose your job. now, while you still have one. hav…
Open Roles 1. Design Engineer at Trust-wallet Location: Remote - Global Apply: Apply Now 2. HPC Systems Engineer at Jump trading Location: Sydney Apply: Apply Now 3. Senior Software Engineer, Developer Platform at Moonpay Location: United States - Hybrid Apply: Apply Now 4. Mandarin - Engineer Project Manager at Bydfi Location: Cupertino, California, United States Apply: Apply Now 5. Onchain Analytics Engineer a…
Open Roles 1. Software Engineering Intern, iOS at Ramp network Location: New York, NY (HQ) Apply: Apply Now 2. Senior Mobile Engineer (React Native) at Trust-wallet Location: Remote - Global Apply: Apply Now 3. Senior Software Engineer, Data Services at Alchemy Location: San Francisco Apply: Apply Now 4. Principal Software Engineer, Trading Systems at Ninjatrader Location: Chicago Apply: Apply Now 5. Senior Soft…
❤1
4 of our people just landed jobs. Tether. KAST. Coinbase. OKX. All 4 came to a career consultation with the same problems: • weak positioning - nobody understood what they actually do • salary negotiation - they kept losing money at the offer stage • zero LinkedIn visibility - invisible to every recruiter • cold applying for months - and hearing nothing back Not a skills problem. Never was. We fixed the positioni…
Open Roles 1. DevSecOps Engineer at Casa Location: Remote Apply: Apply Now 2. Fullstack Engineer / AI Engineer for BRAIINS MANAGER at Braiins Location: Braiins Apply: Apply Now 3. Software Engineer - Front End - Studio (Core) at Clearstreet Location: London, UK Apply: Apply Now 4. Web: Full Stack Tech Lead at Clarity Location: Ideally London-based (Hybrid) Apply: Apply Now 5. GTM Engineer, Advisor Recruiting at …
now hiring: head of engineering zug, switzerland 🇨🇭 CHF 170-220K + tokens about the project: privacy-first security product - a vpn built on a web3 stack, based in crypto valley the role: lead the engineering team, own the architecture and delivery, stay close to the code where it matters the setup: remote, plus the zug office a few times a month switzerland only - based in zug or ready to relocate to zug you: en…
Open Roles 1. Senior II Product Engineer at 9fin Location: London Apply: Apply Now 2. Security Engineer at Offchainlabs Location: Remote Apply: Apply Now 3. Senior Analytics Engineer - Finance at Kraken Location: United States Apply: Apply Now 4. Frontier Engineer (Deployments) at Augur Location: London Apply: Apply Now 5. Forward Deployed Engineer at Sable finance Location: San Francisco Apply: Apply Now — jay…
🌴 Bali, we are coming for youuu 💜 JayaTalent.com @jayatalent is planning a community meetup in Bali, Canggu 🥹✨ real people, real connections, no panels, no boring speeches - just our community in real life 🌅 we have hosted 50+ events around the world, and now we want to see how many of you are actually here 👀 from jaya talent ceo zhanna 💜: as a founder i like to take care of our community. for me it is important t…
Thanks for being with Jaya Talent ❤️🫂 3 years together. 50+ events: meditations, yoga, Ayurveda, jamming, exploring meaning of live and Sufism, poetry reading, longevity and biohacking sessions 🥹 All for the community to make space better 🥹
Showing the 11 most recent of 11 posts we hold for @web3devs3. 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 18 November 2026 — this entry's latest reading, not the date you are reading this.
“Engineering · Rust / Solidity / Smart Contracts | Job Aggregator by Jaya Talent” (@web3devs3), 304 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/web3devs3.
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.