![Telegram profile photo for [Official] Findora Announcement Channel](https://cdn.tgregister.com/av/5b/5b6c5bec46b0b090fdef0b499cc94bbe8b5b47900c8c4130b792864a545e2df1.jpg)
Channel
@FindoraANN
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
349subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001369524573 |
|---|---|
| Type | Channel |
| Username | @FindoraANN |
| Created | Between 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/FindoraANN |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 09:57 | 349 | -2 |
| 6 Aug 2026, 21:17 | 351 | no change |
| 6 Aug 2026, 20:55 | 351 | first reading |
20 posts held, back to 17 October 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 21 December 2023. An engagement rate over an empty window would be a number about nothing.
91 reactions across 15 posts, in 6 distinct kinds. The most used accounts for 31.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 29 | 31.9% | |
| 🔥 | 23 | 25.3% | |
| 👍 | 20 | 22.0% | |
| 🙏 | 16 | 17.6% | |
| ⚡ | 2 | 2.20% | |
| 👏 | 1 | 1.10% |
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 15 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 91reactions 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 17 October 2023 to 21 December 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Join us in ~24 hours for an X/Twitter Space on FRAgments: BRC-20 Inscriptions on Findora! Without realizing it, Findora created a UTXO network that is perfect for inscriptions. Our technology arrived ahead of its time, but we are now moving quickly to deploy "Fragments." Fragments are inscriptions on Findora that are BRC-20 compatible. We are issuing an upgrade to Findora custom asset codes that will make them comp…
❤14🔥4👍1👏1
EVM Staking Update - December 5th | 11:30 PM PST This is likely the penultimate update in the EVM Staking saga 🎉. Tomorrow, the new EVM Staking portal will be live, making it easier than ever to stake FRA and manage which validators you stake with. Additionally, the engineers have rolled out an optional upgrade, v0.4.4, which allows validators to manually claim their commissions without waiting for delegator to cl…
❤9🔥7🙏6👍2
Brief Update - November 27th | 9:15 PM PST Summary: Our top priority is fixing an issue affecting validator commission collection. The fix will be in the form of a mandatory update, with details to be announced once we gather more information from the Engineering team. We're also in the process of collecting feedback from a small group of volunteer QA testers helping us iron out issues with the EVM staking portal. …
👍4
Brief Update - November 15th | 10:15 PM PST Current Status: The iOS and Android Mobile wallets have been updated. The latest mobile version, v0.4.4, seems to have fixed the bugs mentioned in the last update, and though there have been a few reports of the app crashing, the new mobile wallet seems to be running reliably for the community overall. The actual APY earned by delegators is still low, but the engineering…
❤2
Brief Update - November 13th | 10:35 PM PST Mobile wallets have been updated for iOS and Android. The latest mobile version, v0.4.4, includes several bug fixes listed below. ++++++++++++++++++ Mobile Wallet 0.4.4 Bug Fixes Apple iOS: — Resolved a display issue for the staked and total staked amounts when unstaking. — Fixed the decimal place of the staking and unbonding amounts. — Resolved an issue where users c…
👍1🔥1🙏1
Brief Update - November 8th | 11:45 PM PST Current Status: The engineering team has implemented a fix that allows delegators to undelegate from offline validators. They also believe they will be able to deploy a fix that allows validators to manually claim their commission next week. The team is continuing QA testing on the EVM Staking Portal and making adjustments on the front end. The engineering team believes th…
Brief Update - November 7th | 1:53 PM PST (Apologies for the delayed update; I had intended to send this last night. - Daniel Finley) Current Status: The engineering team is working on internal QA testing for the new EVM Staking portal and has implemented a number of improvements. Those test will continue before being released to a 3rd parties to help conduct QA testing. Engineers continued to make progress in crea…
👍1🔥1
Brief Update - November 3rd | 11:15 PM PST Current Status: The engineering team continues to work to improve the performance of the desktop wallet which is currently slow, but stable. They are also investigating display issues with the Android wallet and hope to deploy a fix for the stability issues with the iOS wallet by early next week. The team is continuing QA testing on the EVM Staking Portal. ++++++++++++++++…
Brief Update - November 1st | 10:25 PM PST Current Status: Desktop wallets continue to show stability in displaying staking information, though data is still loading slowly. The team continues to work on new RPC endpoints that are optimized for EVM related traffic. These will help improve the performance of the wallet and make the EVM Staking portal reliable and stable for users when it goes live. The team is also …
👍2
Brief Update - October 30 | 10:30 PM PST Current Status: Desktop wallets continue to show stability in displaying staking information. The team is working to resolve an issue with newly built RCP endpoints optimized to handle only EVM related traffic. Once resolved, the Findora wallet will be redirected to use the new endpoints, further improving the performance of the wallet. The team is also looking into potentia…
⚡1❤1
Brief Update - October 27 | 11:50 PM PST Current Status: DevOps installed a new update to Findora full nodes. The new release, v0.4.3-4-release, brings stability improvements, which means a more reliable display of staking data on the Findora wallet. The time it takes to display staking data is longer than ideal, but users should see fewer instances of zero balances and timeouts. The team will continue to monitor t…
👍2❤1🔥1
Brief Update - October 25 | 11:50 PM PST Current Status: The balance and staking data display in the Findora wallet is sporadic due to backend issues with full nodes. Users may see balance and staking data in the wallet if the query reaches a working full node. The wallet will display zero values for other users if the query reaches a non-working full node. Tokens are safe, though the symptoms may prevent staking f…
Showing the 12 most recent of 20 posts we hold for @FindoraANN. 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 — 1,480,007 of 1,481,217entries 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 1 registered channel — 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“[Official] Findora Announcement Channel” (@FindoraANN), 349 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/FindoraANN.
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.