BlockDeep Labs takes over Polkadot JS https://www.parity.io/blog/js-blockdeep

Channel
Parity Technologies
@parity_technologies
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
880subscribers
+0 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 | -1001166579464 |
|---|---|
| Type | Channel |
| Username | @parity_technologies |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/parity_technologies |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 20:49 | 880 | no change |
| 7 Aug 2026, 01:17 | 880 | first reading |
Engagement
20 posts held, back to 22 August 2022 — 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.
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 3 June 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
https://x.com/paritytech/status/1882056875773960574
Excited to announce the Polkadot Alpha Program is getting deep expertise from the Blockdeep Labs team to enhance help for ecosystem projects at various stages of growth: https://www.parity.io/blog/alpha-program-blockdeep-collab/
Today in Dubai, Parity founder Gavin Wood proposed JAM, a new protocol combining elements of both Polkadot and Ethereum. It is a prospective path to replace Polkadot's Relay Chain with a more modular, minimalistic design that more easily supports scalable smart contracts and enshrines Agile Coretime in favour of the older parachain model. https://graypaper.com
✨ We've updated our logo and relaunched our website. Parity Technologies is a global collective of tech experts. We're building the open-source technologies needed to power an unstoppable, decentralized web. ➡️https://parity.io
Channel photo updated
"JAM A to Z" by Gavin Wood is now available to watch here https://youtu.be/tdvqkKdFTlw
Want to catch a live stream of Parity's Gavin Wood in Bangkok tomorrow at #sub0 (11.10am local time)? You'll need to register for a free online ticket. Also use the same link for last-minute in-person tickets! ➡️https://events.polkadot.network/event/sub0-asia
Live stream finished (37 minutes)
Live stream started
Agile Coretime is coming to Kusama very soon. Read all about it on the Polkadot Forum, and make sure you check the FAQs! By the way, this upgrade will bring an end to parachain auctions on Kusama. Existing leases won from previous auctions will be automatically converted into bulk coretime. https://forum.polkadot.network/t/agile-coretime-coming-to-kusama/663
Elaine Zhu, general manager Parity Asia, features in this story exploring the potential of Singapore - which is also the next destination of the Polkadot Blockchain Academy - as a Web3 hub... https://www.straitstimes.com/business/web3-firms-in-s-pore-hope-for-budget-help-to-grow-talent-pool-build-cyber-crime-defences
Showing the 12 most recent of 20 posts we hold for @parity_technologies. 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.
Mentions
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
@parity_technologies 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 1 post, 8 August 2026 – 8 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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“Parity Technologies” (@parity_technologies), 880 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/parity_technologies.
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.