Channel
@sha256io
On this record: Growth · Engagement · Posts · Cite this entry
181subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001122900996 |
|---|---|
| Type | Channel |
| Username | @sha256io |
| Created | 12 April 2019 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/sha256io |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 19:06 | 181 | -2 |
| 16 Aug 2026, 07:38 | 183 | -2 |
| 8 Aug 2026, 12:16 | 185 | no change |
| 7 Aug 2026, 23:27 | 185 | first reading |
14 posts held, back to 12 April 2019 — 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 14 posts for this entry, the most recent from 28 October 2025. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 8 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 20 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 29 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
Payouts were paused for some hours for a some exception issue. It has been fixed and everything is up and running now. All pending payouts will be processed within 1-2 hours. Thank you for you patience!
Payout service for SHA256 PPLNS pool has some unexpected issues. Mining is not affected, all work will be paid. It is safe to continue mining. Payouts will be resumed ASAP.
There is an emergency issue at payout service hosting place. PPLNS and Combine Service payouts can be delayed for a few next hours. It is safe to continue mining, nothing will be lost. Mining is not affected.
PPLNS pools payout service and Combine service will be paused for next 10-12 hours for an emergency reason at the hosting place. I remind that all payout processing located at physically secure place, which allows keep mind coins at the safest level. But it has not so perfect Internet connectivity and electricity supply in compare with pool mining servers which are located in the best datacenters across the world.. …
Within time range since 31/10/2020 02:00 UTC up to 31/10/2020 14:00 UTC time, both PPLNS pools (SHA256 & ODO) will be unavailable for a short period up to 60 minutes maximum, both web and stratum servers will be unreachable. Please be sure that your mining devices configured properly and using stratum servers hostnames but no self-resolved IP addresses. Also please be sure that your mining machine has backup pools c…
Mining payouts Consolidation Service is available, it allows to combine multiple per-block payouts into a single one. https://combine.dgb256.online/
PPLNS Qubit pool is up and running https://qubit.dgb256.online/
PPLNS Scrypt pool is up and running https://scrypt.dgb256.online/
Digibyte Odocrypt pools are up and running on the Testnet and ready to go for the Mainnet immediately after launch. Odocrypt PPLNS Pool https://odo.dgb256.online/ Odocrypt Solo Pool https://dgb.solomining.io/odo These are only truly working at the present moment and tested with a live hashrate pools, but not like some others which are just declared Odocrypt support but never working. Pools are configured for se…
Showing the 12 most recent of 14 posts we hold for @sha256io. 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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“sha256io” (@sha256io), 181 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/sha256io.
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.