Channel
@aerenetwork
On this record: Growth · Engagement · Posts · Citations · Cite this entry
675subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002654621409 |
|---|---|
| Type | Channel |
| Username | @aerenetwork |
| Created | 24 April 2025 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/aerenetwork |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 14:33 | 675 | -1 |
| 6 Aug 2026, 20:17 | 676 | first reading |
7 posts held, back to 24 April 2025 — 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 7 posts for this entry, the most recent from 13 July 2026. An engagement rate over an empty window would be a number about nothing.
AERE now verifies NIST FIPS 205 SLH-DSA-SHA2-128s (SPHINCS+) on-chain, validated bit for bit against NIST ACVP vectors. A full verifyAndRecord landed at block 8916065, lastResult true. AereSphincsVerifier: 0xAfFc9F8d950969b46b54e77758BbFf7e000c87e6 (AERE team)
ERC-4337 account abstraction runs on AERE through AereEntryPointV2 at 0x8D6f40598d552fF0Cb358b6012cF4227B86aF770, with smart accounts from AerePasskeyAccountFactoryV2 at 0x5FFa9a6487DA4641a1A1e7900ff2bD4525D34fdA. Because the account is a contract, its rules are programmable. That unlocks session keys (scoped, temporary, limited) and social recovery via guardians, with no single fatal seed phrase. EIP-7702 delegati…
AereSphincsVerifier runs NIST FIPS 205 SLH-DSA-SHA2-128s (SPHINCS+) fully on-chain, validated against NIST ACVP test vectors. verifyAndRecord executes on-chain and records its result. 0xAfFc9F8d950969b46b54e77758BbFf7e000c87e6 Verify on chain 2800.
AereSphincsVerifier runs NIST FIPS 205 SLH-DSA-SHA2-128s (SPHINCS+) on-chain. Stateless hash-based signatures, validated against NIST ACVP test vectors. verifyAndRecord returned true within the EIP-7825 per-tx gas limit; verify on chain 2800 at block 8916065. 0xAfFc9F8d950969b46b54e77758BbFf7e000c87e6
AereSphincsVerifier now runs NIST FIPS 205 SLH-DSA-SHA2-128s (SPHINCS+) on-chain, validated against NIST ACVP vectors. A verifyAndRecord call recorded on-chain within the EIP-7825 per-tx gas limit. 0xAfFc9F8d950969b46b54e77758BbFf7e000c87e6 Verify on chain 2800.
AERE Network is live on chain 2800: a public EVM Layer 1 with 0.5s deterministic finality and a fully open codebase. This channel carries real updates only. What ships, the contract addresses you can verify yourself, and the code at github.com/aerenetwork. No hype. Just what is on-chain.
Channel created
Showing the 7 most recent of 7 posts we hold for @aerenetwork. 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 — 303,107 of 1,169,250entries 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.
Named by 2 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.
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.
“Aere Network” (@aerenetwork), 675 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/aerenetwork.
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.