Channel
@goliathupdates
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1subscribers
-686 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003001744574 |
|---|---|
| Type | Channel |
| Username | @goliathupdates |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 8 times, most recently 16 October 2026 |
| On Telegram | t.me/goliathupdates |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 15:03 | 1 | -686 |
| 8 Aug 2026, 02:30 | 687 | no change |
| 7 Aug 2026, 19:23 | 687 | first reading |
20 posts held, back to 11 February 2026 — 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 26 June 2026. An engagement rate over an empty window would be a number about nothing.
Please be aware that there will be routine maintenance conducted over this coming weekend (27th-28th June). While no issues are anticipated, some minor transaction delays could occur with delays of 1-2 minutes.
We are currently performing bridge maintenance on the Layer 1 Bridge for @Onyx While delays are unlikely, some delays are possible over the next two hours and are normal.
Community Update: Bridge Transaction Display Change We are updating the bridge flow to use Ethereum-compatible transactions instead of Goliath-native transactions. How does this affect users? There is no practical impact at all. The bridging process remains the same, and no action is required from your side. The only visible change is how the transaction is displayed after bridging from Ethereum to Goliath. Prev…
Please be aware that some transaction delays are anticipated over the coming hours due to ongoing maintenance upgrades to Goliath. Any delays are expected and as a result of ongoing maintenance.
Goliath will undergo a maintenance window tomorrow, the 14th of May, between 14:00-16:00 UTC. While no noticeable impact is expected, it is possible that services could be disrupted for approximately 10 minutes.
As part of our ongoing commitment to providing the best experience possible for the Onyx Layer 1 Blockchain, we will be conducting planned maintenance on the Goliath Mainnet this weekend (May 9-10). While we anticipate no noitceable interuptions to the network, some delays in TX processing are possible.
The Goliath testnet will be undergoing upgrades from approximately 21:00 UTC today (04/13). This may include brief freezes. Following successful testnet implementation, we anticipate similar freezes when upgrading the Goliath mainnet on 04/14 and 04/15. Freezes for both the Goliath mainnet and testnet are expected to last up to 20 minutes.
Goliath updates and maintenance will occur this weekend (Friday-Monday). These updates will include upgrading all nodes to the latest version that Goliath will run going forward and short freezes are to be expected. Additionally, these nodes will all be restarted simultaneously.
Goliath RPC Relay Upgrade — Mainnet Prep We've just upgraded all JSON-RPC relay nodes across the testnet with zero downtime. Here's what's new: - Mainnet-ready branding — Goliath chain ID and configuration baked into the relay for seamless mainnet launch - Pectra EIP support — authorisation lists in transaction data, keeping us aligned with the latest Ethereum standards - Paymaster support — multiple paymaster …
Faucet Update: Anti-Arbitrage Protection Enabled Goliath has enabled dynamic pricing for ERC20 token distributions. The faucet now uses real-time Slingshot Swap prices to calculate token amounts, ensuring fair distribution. What changed: - BTC, USDC, and ETH faucet amounts are now calculated based on live Uniswap V2 prices - A 5% discount is applied so faucet tokens are always worth slightly less than requesting …
Please be aware that Onyx will be conducting maintenance from today (6th of March) until Monday (9th of March). Goliath is preparing mainnet infrastructure and performing tests on the testnet with network configuration updates. Brief freezes are expected.
Please be aware that Onyx will be conducting maintenance today (4th of March) related to the validator configuration update. This maintenance is necessary as part of preparing Goliath for external validator onboarding.
Showing the 12 most recent of 20 posts we hold for @goliathupdates. 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“Goliath Updates” (@goliathupdates), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/goliathupdates.
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.