So, that's it, our wallet is not able to sync, money is lost for unknown time.

Channel
Chia Faucet news
@chiafaucet
On this record: Topic · Growth · Engagement · Posts · Polls · Cite this entry
55subscribers
-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 | -1001203285248 |
|---|---|
| Type | Channel |
| Username | @chiafaucet |
| Created | Between 1 March 2018 and 6 June 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 2 October 2026 |
| On Telegram | t.me/chiafaucet |
Topic
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 2 October 2026 and assigned it the closest of 31 fixed categories, at 64% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Oct 2026, 11:17 | 55 | -1 |
| 10 Aug 2026, 07:31 | 56 | no change |
| 7 Aug 2026, 20:35 | 56 | first reading |
Engagement
20 posts held, back to 6 June 2021 — 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 page of 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 24 March 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
Syncing problem is getting more and more ridiculous with each day.
Still trying to sync our wallet but it's SOOO SLOW. We're on the latest version of chia. Any suggestions?
Quick update people! Little maintenance. Boring stuff down below... We have to shrink the mainnet SQLite file, it's risen to 40 gigs... Our payouts will be continued when the shirking process finishes.
And again! Hooray! We're fully synced!
Unfortunately, our wallet stopped syncing for no reason. We have to resync it, it takes some time, keep patient.
Hooray!!! Our wallet is fully synced and paying process is already started! Thank you for being with us! ❤️
Good news everyone! We've managed to get our wallet to continue syncing and we will start paying out in one hour!
Seems it's a bug, our wallet sync broke on block 1028137, we're still solving this issue, all our funds is located on that wallet. While we're solving this issue, you can claim at our friend faucet - gett,ga they successfully synced their wallet you can claim there!
Our payment gateway experiencing troubles right now, but no worries, keep claiming, each payment will be made when our new wallets will be synced!
Our faucet friends from https://gett.ga is waiting for you! Share this post, to help them spread chia to everyone!
Woohoo! We updated our website! Now 4x time faster! Did you notice performance increase?
- Yes72%
- No23%
- My opinion in comments5%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Showing the 12 most recent of 20 posts we hold for @chiafaucet. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Woohoo! We updated our website! Now 4x time faster! Did you notice performance increase?
- Yes72%
- No23%
- My opinion in comments5%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 6 June 2021 to 24 March 2022. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“Chia Faucet news” (@chiafaucet), 55 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/chiafaucet.
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.