Telegram RegisterThe public register of Telegram

Channel

Pi Community(DAOs, DeFi, NFTs)

@PI_NETWORK0314

On this record: Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

520subscribers

+1 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-1001490169729
TypeChannel
Username@PI_NETWORK0314
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 7 August 2026
On Telegramt.me/PI_NETWORK0314

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

519520519.57 Aug 2026, 04:17 — 519 subscribers7 Aug 2026, 14:10 — 520 subscribers7 Aug 2026, 04:177 Aug 2026, 14:10
2 measurements taken within a single day, net +1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 519–520 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 14:10520+1
7 Aug 2026, 04:17519first reading

Engagement

19 posts held, back to 19 June 2026the 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.

ERR · 30 days
4.19%
avg views ÷ 520 subscribers
Avg views / post
21.8
5 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
5
of 19 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 5 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 26 July 2026
Posts held19 (19 June 202626 July 2026)
Views total109
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 04:17 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.

Reaction mix

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
150.0%
👍150.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 4 of the 19 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 19 June 2026 to 26 July 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

26 Jul 2026, 11:52 UTC14 views0 reactionsread 7 August 2026
Forwarded from @PiAnnouncementsPhoto

Pi Launchpad has completed the distribution of its second Testnet token, SLICE! Explore the post-launch experience and see how liquidity pools work through the new price tracking feature! The Launchpad app in Pi Browser shows individual allocation details, the launch and effective token prices, access to the SLICE liquidity pool, and a chart tracking changes in the SLICE price relative to Test-Pi. Go to the Pi min

23 Jul 2026, 14:42 UTC30 viewsread 7 August 2026
Forwarded from @PiAnnouncementsPhoto

The Pi mining app side menu and app profile page have been redesigned! As the first step of a broader mining app design refresh, this update makes important Pioneer info and ecosystem features easier to find, understand, and navigate. Tap the hamburger (☰) icon in the top left of the Pi mining app to check it out. Since the mining app is a central part of the Pioneer experience and its interface has supported the P

23 Jul 2026, 14:42 UTC27 viewsread 7 August 2026
Forwarded from @PiAnnouncementsPhoto

On July 22, Pi is scheduled to upgrade to Protocol v25, which primarily focuses on improving network stability and reliability, and supports new capabilities for more efficient, privacy-preserving smart contracts. Go to the Pi mining app to learn more!

23 Jul 2026, 14:42 UTC6 viewsread 7 August 2026
Forwarded from @PiAnnouncements

Pi App Studio backend support has been enabled! Backend capabilities begin with persistent storage for newly created App Studio apps, allowing apps to save and retrieve user-specific data across sessions. Creators can now build App Studio apps with user experiences that continue even after users leave and return. For example: - Game apps can remember a user’s high scores - Productivity apps can remember a user’s to

14 Jul 2026, 23:10 UTC32 viewsread 7 August 2026
Forwarded from @PiAnnouncements

Pi App Studio backend support has been enabled! Backend capabilities begin with persistent storage for newly created App Studio apps, allowing apps to save and retrieve user-specific data across sessions. Creators can now build App Studio apps with user experiences that continue even after users leave and return. For example: - Game apps can remember a user’s high scores - Productivity apps can remember a user’s to

9 Jul 2026, 19:38 UTC31 viewsread 7 August 2026
Forwarded from @PiAnnouncements

Pi App Studio backend support has been enabled! Backend capabilities begin with persistent storage for newly created App Studio apps, allowing apps to save and retrieve user-specific data across sessions. Creators can now build App Studio apps with user experiences that continue even after users leave and return. For example: - Game apps can remember a user’s high scores - Productivity apps can remember a user’s to

9 Jul 2026, 19:38 UTC26 views1 reactionsread 7 August 2026
Forwarded from @PiAnnouncementsPhoto

Pi App Studio has released two updates to help creators build more engaging and useful app experiences. 1. Backend support enables persistent user experiences for newly created App Studio apps: Apps can save and retrieve user-specific data across sessions, enabling experiences that continue even after users leave and return. 2. AI-assisted App Planning Phase: Creators can develop their ideas with the help of AI bef

1

4 Jul 2026, 11:54 UTC37 views1 reactionsread 7 August 2026
Forwarded from @PiAnnouncements

Pi2Day 2026 reflects how Pi’s utility continues to grow through infrastructure and participation. - Through SoloHost, Pi Desktop and Nodes can support new local AI app and compute use cases - Pi Sign-in can help connect those experiences across users, devices, and services - PiVerify can extend Pi’s real-human verification capabilities to third-party clients. Together, these releases point to a broader direction fo

👍1

4 Jul 2026, 11:54 UTC32 viewsread 7 August 2026
Forwarded from @PiAnnouncementsPhoto

PiVerify is a KYC identity verification service available to third-party companies, making Pi’s real-human verification capabilities available outside the Pi ecosystem. With PiVerify, external platforms can verify their users, reduce fake or duplicate accounts, and support compliance-related identity workflows. For businesses and platforms, the need is straightforward: many digital services need to know whether use

4 Jul 2026, 11:54 UTC24 viewsread 7 August 2026
Forwarded from @PiAnnouncementsPhoto

Pi Sign-in allows supported third-party websites and apps to offer Pi accounts as a sign-in or sign-up option. It helps provide the infrastructure that allows applications and services to recognize, connect, and serve users across and outside the ecosystem. This means Pioneers can access supported services with their Pi account instead of creating a new account or password for every app. Why would third-party serv

4 Jul 2026, 11:54 UTC24 viewsread 7 August 2026
Forwarded from @PiAnnouncementsPhoto

SoloHost expands the utility of Pi Nodes beyond just blockchain validation. Released in Beta on Pi2Day 2026, SoloHost on Pi Desktop gives Pioneers new ways to use their computers to run local apps, AI utilities, distributed computing, and other compute-based use cases. Pioneers can also remotely engage with the corresponding app through mobile devices on Pi Browser. SoloHost also lets developers build and list the

4 Jul 2026, 11:54 UTC28 viewsread 7 August 2026
Forwarded from @PiAnnouncements

The three key Pi2Day 2026 releases extend Pi’s services to businesses and developers outside the Pi ecosystem, while inviting them to join Pi Network and take advantage of Pi’s unique benefits and resources. Read the full Pi2Day blog to learn more about the SoloHost, Pi Sign-in, and PiVerify releases. https://minepi.com/blog/pi2day2026

Showing the 12 most recent of 19 posts we hold for @PI_NETWORK0314. 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.

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.

“Pi Community(DAOs, DeFi, NFTs)” (@PI_NETWORK0314), 520 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/PI_NETWORK0314.

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.