Prices are aggregated reference prices served by the site API. Dates shown are source observation dates when available; availability and freshness vary by asset.
Different assets may share a name or symbol. Compare their stable identifiers.
Loading assets…
Dated context
Selected facts about the software or network, not price signals. No daily news feed.
Bitcoin (BTC)
Open the Bitcoin (BTC) pageBitcoin: a fix concerns nodes running outside LinuxSource dated 28 October 2026This concerns node software rather than a change in BTC’s price.
Bitcoin Core’s October 28 notice describes possible memory exhaustion on non-Linux nodes. It lists fixes in 29.5, 30.4, 31.2 and 32.1. Linux is outside this issue’s scope; the fixes have different release dates.
This notice does not establish lost BTC or an issue affecting every wallet.
Source: Bitcoin Core, October 28, 2026 — original notice. Original factual summary rewritten in English by HubTrade; no project endorsement.
Ethereum (ETH)
Open the Ethereum (ETH) pageHoodi: keep the October 26 postponement in viewSource dated 22 October 2026For Ethereum followers, this helps distinguish a cancelled test milestone from a confirmed launch.
The October 22 notice withdraws Hoodi’s planned October 26 Glamsterdam activation and associated gas-limit increase. That post gives no replacement date. It concerns a test network and does not set a mainnet launch date.
No price effect or action for ETH holders is inferred.
Source: Ethereum Foundation Protocol Cluster, 2026-10-22 — original post. Source text under CC BY 4.0. English summary rewritten by HubTrade; no endorsement by the source.
BNB
Open the BNB pageBNB Chain: the Jenner upgrade starts on testnetSource dated 22 October 2026For BNB followers, this separates a testnet trial from a confirmed mainnet activation.
BNB Chain’s October 22 guide schedules the Jenner hard fork on testnet for October 28, 2026. It plans reserved block capacity for payments (BEP-703), the CAS20 asset standard (BEP-702, announced separately) and millisecond timestamps for contracts (BEP-706). Mainnet timing will be announced separately.
The listed actions target node operators, validators and developers; no action for BNB holders or price effect is inferred.
Source: BNB Chain, 2026-10-22 — original publication. Original factual summary written in English by HubTrade; no endorsement by the source.
XRP
Open the XRP pageXRP Ledger: two flaws fixed, version 3.4.1 requiredSource dated 9 October 2026For XRP followers, this separates an already shipped software fix from an incident affecting funds.
The XRP Ledger’s October 9 report describes two defects fixed in xrpld 3.4.1, released on September 25: a Batch transaction validation issue and a payment-engine integer overflow rated critical. According to the report, no exploitation was found on any public network; for the Batch defect, no funds were lost. Since fixBatchV1_2 activated on October 9, older servers are amendment-blocked.
This report is dated October 9; it is not today’s news. No price effect or action for XRP holders is inferred.
Source: XRP Ledger (xrpl.org), 2026-10-09 — original publication. Original factual summary written in English by HubTrade; no endorsement by the source.
Solana (SOL)
Open the Solana (SOL) pageSolana: Agave 4.4.0 becomes the recommended stable releaseSource dated 28 October 2026For SOL followers, this flags a validator software change without treating it as a network activation.
On October 28, 2026, Anza published version 4.4.0 of its Agave validator client, described as a “stable release recommended for general adoption”, and also for Testnet and Devnet. It follows the 4.4.0-rc.1 candidate of October 26.
Agave is one of several Solana clients; the note gives no activation date or share of upgraded validators. No price effect is inferred.
Source: Anza — Agave repository (GitHub), 2026-10-28 — original publication. Original factual summary written in English by HubTrade; no endorsement by the source.
Understand a data point and prepare an issue report. HubTrade is an independent information service, not affiliated with any exchange.
This help page sends no message. You can prepare a description without your name or email address.
Never share passwords, codes, sign-in links, private keys or card numbers.
Where does the data come from?
Prices, market caps, volumes, changes, categories and per-exchange markets are aggregated reference data. HubTrade updates them periodically and each value shows its date. Values older than 24 hours, or with an unknown date, are removed. Prices are in USD; there is no euro conversion and no real-time quote. The date shown may be the source’s update time or HubTrade’s collection time.
Periodic updates with no guaranteed delay. These are not real-time quotes.
Prices in US dollars (USD). Euro conversion not available.
Partial coverage: not all assets are refreshed at the same pace. Check the date on each row.
Understand prices, changes and timestamps
Different assets may share a name or symbol. Check the stable identifier with the source before comparing numbers. If you cannot verify it, state that uncertainty.
Check the currency beside the price. Copy all visible digits and separators as displayed.
For a change, record the stated period. An unavailable change is not zero.
Record the timestamp label and time zone, or note “timestamp not displayed”. A declared timestamp alone does not guarantee market freshness.
TEST — FICTIONAL VALUES — NOT A CURRENT MARKET PRICE
Fictional asset ALPHA-TEST: 0.00001234 USD; 24-hour change unavailable. With two decimal places, the display would be 0.00 USD, but the original value is greater than zero. An unavailable change is not 0%.
Data is missing
Identify the asset, the expected data and what appears instead: blank space, dash, “N/A”, loading state or error. Distinguish missing information from an actual zero.
Record the steps and observation time, including your time zone.
A price is unreadable or cut off
Copy only the characters you can read. Do not guess hidden digits. Describe whether the price is cut off, covered, rounded to zero or too small.
Include the device, browser and orientation. Hide personal information and other tabs in any optional screenshot.
Sign-in or account access issue
You can browse the public pages without signing in.
Identify the step: opening sign-in, receiving a link, returning to the website or accessing a feature. Copy the error after removing personal information.
Describe the expected and actual result. Never attach a sign-in link, emailed code or complete payment receipt. Account checks require a separately confirmed channel.
Outline for your description
Page: public URL without sign-in parameters.
Asset: name, symbol and displayed identifier if available.
Observation: exact data or message; price, currency, period and timestamp if relevant.
Time and device: date, time, time zone, device, browser and orientation.
Steps: actions, expected and actual result.
Optional screenshot: limited to the issue, without personal information.
No request has been sent. This page promises no submission channel or response time.