BTX Network Status

Changes

What changed on this page, newest first, in short words. The version number is shown at the bottom of every page.

  1. v0.16.0

    • Internal preparation of further pages; nothing changes on this page.
  2. v0.15.0

    • Internal preparation of a further page; nothing changes on this page.
  3. v0.14.1

    • Fix: a stuck height without a known cause stopped the page from updating. Such heights now appear without a note.
  4. v0.14.0

    • Our snapshot node now appears in the table of our own nodes, with height, lag behind the signed blocks and whether it is on the same chain.
    • If one of our own nodes is stuck or behind, a note at the top says so; until now this was only visible in the table further down.
  5. v0.13.0

    • Signers: below "Own mirror quorum" the page now says how many of the keys our node pins actually sign and whether a spare is left, e.g. "Pinned and active: 2 of 3, 2 needed, no spare".
    • Reorgs: one race counts once. Switches at the same fork height within 10 minutes (a node flipping back and forth) are merged, and the value is called "seen by our node".
    • Stuck peers: every height has a short note and a link to its fix, on the node help and on the status page.
    • UTXO set: a note explains why it is about 9,900 BTX below the issued amount (the shielded pool and unspendable outputs are not part of it).
    • Events: "Page values now come from our node Archive X" no longer carries block links.
    • Snapshots: the first signed datadir snapshot is out; its release title now says "signed" once Archive 2 has checked it.
  6. v0.12.1

    • Menu: new item "API" that leads to the API description.
    • Node help: own section "Setting up your own node" near the top, with links to the official BTX releases and to easynode.
  7. v0.12.0

    • New page "JSON API" (link in the footer): which files there are, what their fields mean, a list of every value, and how to use the data. Format v1 stays compatible.
    • Competing chains: the traffic light and the verdict "Stable" now count only branches that lasted 15 minutes. Two branches for a minute are a normal race and no longer turn the page red; the current number stays visible.
    • Node help: how to set up a node, with the official releases and, as a community option, easynode.
  8. v0.11.0

    • Pools: the page shows how many miners the largest pool has, as reported by the pool itself (ninjaraider.com and btx-pool), next to its name and in the producer table. Our node cannot check these numbers, so they are always marked "as reported by the pool".
  9. v0.10.0

    • Largest producer: the page now names it and says when it is a public pool, e.g. "ninjaraider.com (pool)".
    • A known pool with more than half of the blocks is a warning (yellow) instead of critical: many miners share it and can switch pools at any time. A single unknown producer with the majority stays critical. Thanks to the community for the suggestion.
  10. v0.9.3

    • Verdict history: a day now shows the worst level that held for at least 15 minutes. A flicker of a minute or two (for example two competing chains for a moment) no longer colours the whole day; the current verdict at the top still reacts at once.
  11. v0.9.2

    • "Confirmed by other sources": a source two blocks apart from our node still confirms the block height. The sources are read at slightly different moments, so that is normal timing; from three blocks on it counts as different.
  12. v0.9.1

    • Node help: the stuck heights now follow the BTX code. 184,999 and 228,000 are nodes without a GPU in consensus mode, 185,109 are old clients on an old branch; the DNS seeds at 228,000 run in relay mode on purpose and are marked as harmless.
  13. v0.9.0

    • New design: clearer and calmer, dark by default (the ◐ button switches to light). The previous design stays under /old/ for comparison.
    • Three verdicts at the top: is the network stable, performant and secure right now? Each names the values that pull it down and shows the last 30 days.
    • Confirmed by other sources: how many independent sources (our two archives and the public explorers) show the same block height and the same chain.
    • Our own figures next to the external ones: the client versions among our peers and the coins in our own UTXO set.
    • Node help reviewed with a BTX developer: clearer causes, the trusted-mirror settings and safer snapshot steps.
  14. v0.8.0

    • New page "Node help": check your own node in the browser (nothing is sent), see the known heights where nodes get stuck and how to fix them, and a checklist for every operator.
    • New in the network section: how many peers of our archives are stuck far below the tip, and at which heights. Only totals are shown, never a single node.
  15. v0.7.0

    • New: daily datadir snapshots to start a node in minutes. Each one is checked in an offline node, then downloaded, checked again and signed by our second archive. The page shows the newest signed one, its age and the key to verify it.
  16. v0.6.1

    • Calmer traffic light: a reorg counts for it only during the next 24 hours. The deepest reorg of the week and the list of the last 30 days stay visible for information.
    • Warnings of our node no longer turn the page yellow. In btxd 0.34.15 they stay until the node restarts, even after a harmless short race; the count is still shown.
  17. v0.6.0

    • Service board: each public explorer gets a verdict (in sync, behind, stale, other chain, down), checked every minute. The rules are shown below the table.
    • When our own nodes are stuck, the page says so at the top and pauses its verdicts. The block height then comes from btxscan and Byron Bay while both agree.
    • Signers: green as long as two keys sign, which is what mirror nodes need. Keys without a known operator are shown as new signers.
    • Supply is now called "Issued so far (actual block rewards)" and explains why it is lower than 20 BTX × height. Circulating supply is hidden until the gap to the UTXO set is explained.
    • The next halving is shown as an estimated month, at the block pace of the last 24 hours.
    • Our archive nodes watch themselves and this page, and recover on their own from a known stuck state of btxd 0.34.15.
    • New: this "Changes" page and a version number for the page.
  18. v0.5.0

    • Two own archive nodes. If one is stuck, the page takes its values from the other one; both are compared on the page.
  19. v0.4.0

    • Decentralisation is rated on its own, apart from the chain status, so a concentrated set of producers does not hide a real incident.
    • Block producers are named where they identify themselves; difficulty is shown more precisely; the reorg depth also counts blocks dropped above the new tip.
    • BTX Pool on the ecosystem page. The page moved to its own domain.
  20. v0.3.0

    • Plain explanations of the signer and producer risks. A lagging node is no longer counted as an incident.
    • Old warnings of the node no longer turn the fork check red. Optional automatic refresh every 60 seconds.
  21. v0.2.0

    • Live with real data from our own archive node.
    • Charts with history since the genesis block, an event log, a list of recent reorgs and links to the block explorers.
    • The block explorers are cross-checked against our node.
    • Clearer page after feedback from BTX core: jump bar, section summaries, the real issued supply instead of 20 BTX per block.
  22. v0.1.0

    • First version with sample data: status page, ecosystem page and JSON API, in English and German.