Video, posted without a caption
Signed Ally Haire | Lilypad

Channel
@lilypadnetwork
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
1,602subscribers
-14 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002088976662 |
|---|---|
| Type | Channel |
| Username | @lilypadnetwork |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/lilypadnetwork |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 16:09 | 1,602 | -2 |
| 18 Aug 2026, 23:26 | 1,604 | -4 |
| 15 Aug 2026, 16:13 | 1,608 | -5 |
| 11 Aug 2026, 20:52 | 1,613 | -3 |
| 7 Aug 2026, 22:00 | 1,616 | no change |
| 7 Aug 2026, 21:52 | 1,616 | first reading |
20 posts held, back to 1 November 2024 — 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 9 July 2025. An engagement rate over an empty window would be a number about nothing.
21 reactions across 8 posts, in 5 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 7 | 33.3% | |
| 👍 | 6 | 28.6% | |
| ❤ | 5 | 23.8% | |
| 🤣 | 2 | 9.52% | |
| 👏 | 1 | 4.76% |
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 8 of the 20 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 21reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 1 November 2024 to 9 July 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Video, posted without a caption
Signed Ally Haire | Lilypad
🐸
📢 Update: Resource Provider Beta program details 👋 gm Resource Providers! 👋 Thank you for supporting the Lilypad Testnet and providing feedback while the network scales. Work to grow Testnet is yielding exciting results! Job reliability continues to increase while the community creates new modules to run on the network https://github.com/Lilypad-Tech/awesome-Lilypad. For the next phase of Resource Provider incenti…
Want to get more involved with Lilypad? 🐸 We’re rolling out an Ambassador Program and looking for passionate builders, researchers, and AI enthusiasts to help shape the future of compute. If you’re excited about AI, DeSci, open source, and the power of decentralized infrastructure—this is for you. Apply now 👇 https://docs.google.com/forms/d/e/1FAIpQLSdsJHkYlVVm9YILPodExa4AgGCfW-8bHZanf9OS57QxQee3SA/viewform
🔥7🤣1
We are LIVE! Watch here 👇 https://x.com/lilypad_tech/status/1881884659233308944?s=46
🤣1
📢 Update: Work in progress to launch RP Beta program 👋 gm Resource Providers! 🐸 Work continues to rearchitect the Testnet rewards system including planning for the Resource Provider Beta program. In order to align the rewards system closely with how RPs will operate on Mainnet, the rewards system will require RPs to run jobs in order to receive rewards. More on this soon! Thank you to all RPs who submitted the Beta…
📢 Update: Retroactive rewards drop status 👋 gm Resource Providers! 🐸 A retroactive Lilybit rewards drop has been planned and is on schedule to be applied early next week. The retroactive drop will provide Lilybits to RPs that are missing rewards through no fault of their own due to IncentiveNet scaling issues. Stay tuned for more IncentiveNet updates as we rearchitect the backend system and begin testing the next …
Incentivised Testnet Update gm gm Resource Providers After multiple fixes for the recent issues with Resource Providers not receiving rewards on the Incentivised Testnet, we’ve decided to temporarily pause the system. This pause will help address scaling challenges in the Lilybit rewards system and make necessary enhancements for Mainnet. During the IncentiveNet pause, we’ll rework the rewards system to resolve ou…
👍1
📢 Update: Rewards system investigation 👋 gm Resource Providers! 🐸 We are aware that nodes across the network are not receiving Lilybit rewards as expected. Our team investigated this issue and believe the root cause have been identified. The Lilybit rewards system continues to face scaling issues, so in response, our team is scaling up the system backend to handle the increased load. This work has been on-going ove…
📢 Update: Rewards system investigation 👋 gm Resource Providers! 🐸 Over the last week, our team has pushed backend updates to the Lilybit rewards system and continues to resolve points issues with some Resource Providers (RP). An important part of the fix includes scaling up the rewards system to handle the large volume of RPs online. We will keep the community updated as this work continues. A huge thanks to the c…
🚨 Action Required - New Release - Goethe (v2.10.0) "As soon as you trust yourself, you will know how to live." – Johann Wolfgang von Goethe gm Resource Providers! 🐸 Lilypad v2.10.0 - Goethe was released requiring RPs to update! https://github.com/Lilypad-Tech/lilypad/releases/tag/v2.10.0 The Docker Compose file has been updated to run Bacalhau in a separate Docker container. This change will help to ensure Bacalh…
❤1👍1
📢 Update: Rewards system investigation 👋 gm Resource Providers! 🐸 Our team greatly appreciates the patience while edge cases of some RPs not receiving rewards are investigated. We have been running test cases to identify the root cause and believe this is related to how the rewards system backend handles recent rewards changes. Testing continues and in the meanwhile we are specing out a fix. This has taken some ti…
❤4
Showing the 12 most recent of 20 posts we hold for @lilypadnetwork. 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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Lilypad Network Announcements” (@lilypadnetwork), 1,602 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/lilypadnetwork.
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.