Channel
@teamaikon
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
53subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001260992309 |
|---|---|
| Type | Channel |
| Username | @teamaikon |
| Created | Between 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/teamaikon |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 09:30 | 53 | no change |
| 7 Aug 2026, 00:44 | 53 | first reading |
20 posts held, back to 18 May 2023 — 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 23 November 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Hi AIKON Community, I am sharing the following message on behalf of AIKON President, Mike Douglas, which was posted earlier today to the ORE Network Telegram Channel, with an added section at the end regarding a change to ORE ID. All, I wanted to introduce myself to this community and give all involved a clear understanding of where we are and what’s next. I’m Mike Douglas. I was brought in to advise AIKON just u…
ICYMI: We had an AMA in the ORE Network Telegram Channel on Wednesday. Here’s the recap >> https://bit.ly/ORE-AMA-Recap-
Hi everyone! If you missed last week’s Telos Cloud Wallet AMA with Darrell Malone Jr, take a look at the recap to discover how ORE ID is empowering developers to build accessible blockchain experiences: https://blog.aikon.com/2023/10/1086/
🚨 Telos Cloud Wallet AMA Reminder! Make sure to join our Telos Core Developers AMA special with AIKON today, covering the new Telos Cloud Wallet! Starts in 1 hour! Join Here: https://twitter.com/i/spaces/1YqKDgzpZDNxV 🔗 https://x.com/HelloTelos/status/1715050399915196893?s=20 Twitter | Discord | Telegram | Reddit | Announcements
Free Workshop for Telos Developers >> Builders in the Telos ecosystem will soon have access to ORE ID’s easy onboarding solution. Join us for a free Telos Cloud Wallet and ORE ID integration workshop — no blockchain development experience necessary! Hosted by AIKON Developer Evangelist Darrell Malone. Oct 24th 1pm pst Oct 26th, 2pm pst Register now>> https://on.aikon.com/Telos-Workshop
Photo, posted without a caption
We’re pleased to announce the launch of the Telos Cloud Wallet, powered by ORE ID. Read more below >>
Introducing the Telos Cloud Wallet - Now Available for Telos Developers! ☁️ The Telos Foundation, through its integration with AIKON’s ORE ID built on the ORE Network, introduces the Telos Cloud Wallet, a transformative cloud wallet solution for developers operating on the Telos Blockchain! This game-changer replaces the usual Web3 'Connect Wallet' with an intuitive Web 2.0 login, Instantly creating a non-custodial…
As you may have seen across social media, Marc Blinder, the Co-Founder and CEO of AIKON, has stepped down from his role with our organization to pursue a new venture, Zora Direct. We are grateful for Marc's steadfast leadership and dedication to the organization since its founding and look forward to working with him and Zora Direct in a client capacity. Stepping into the role of interim CEO is the co-inventor of the…
AIKON is buying 500,000 #ORE tokens in September and successfully completed the purchase of 500,000 in August. Learn more about AIKON’s Transparency & Trust Initiative for ORE Token Purchases: https://bit.ly/425xyR6 #transparency #trust #decentralizedidentity #oreprotocol #oreid
Do you remember how many steps you had to complete the first time you created an account for a Web3 application for the first time? We’ve broken down just how challenging this process can be for new users — and the major reason non-technical people give up on Web3 before they’ve even really begun. https://on.aikon.com/ORE-ID
Developers using ORE ID for easy onboarding can now take advantage of a huge new UX benefit: structured string signing. Developer Relations Lead Darrell Malone has the download >> https://on.aikon.com/Structured-String-Signing
Showing the 12 most recent of 20 posts we hold for @teamaikon. 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.
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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“AIKON” (@teamaikon), 53 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/teamaikon.
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.