render stale block header tree on website (like fork-observer) - #148
Merged
Merged
Conversation
0xB10C
force-pushed
the
fork-observer-tree
branch
from
September 19, 2026 16:38
88bdb55 to
2e41411
Compare
Collaborator
Author
|
Looks similar to Still testing... |
0xB10C
force-pushed
the
fork-observer-tree
branch
2 times, most recently
from
September 24, 2026 04:55
5ac6264 to
9c23a83
Compare
Contributor
|
Yeah this will be rad. And then I think we need to combine the invalid-blocks into the visualisation at some point later too!? That is, I think we ideally want a visualisation that shows all Bitcoin mined-block activity |
Collaborator
Author
|
Good idea. I guess that is something we can show on fork-observer instance by importing the blocks from stale-blocks and invalid-blocks! And/or on a static page. |
0xB10C
force-pushed
the
fork-observer-tree
branch
from
September 25, 2026 04:26
9c23a83 to
da8ca6c
Compare
0xB10C
marked this pull request as ready for review
September 25, 2026 04:26
0xB10C
changed the title
The deploy workflow now renders a header tree of every stale block with a known header next to the main chain. It seeds a fork-observer database with the main chain headers from block-dn.org and the stale headers from stale-blocks.csv, starts fork-observer on it, and exports the tree into site/tree for the dashboard to embed. The binary is the fork-observer package of the 0xb10c/nix repository, fetched from its cachix cache. The scripts and styles are those of fork-observer's main branch. The page drawing the tree is our own: it provides the little that fork-observer's main.js does on top of blocktree.js on a live instance, and leaves out everything a snapshot doesn't need. A made-up "stale-blocks dataset" node marks the tips of the stale branches, since no real node reports them, with the dataset's own statuses: full-block and header-only, for what the dataset holds of the block. Stale headers whose parent is unknown can't be placed in the tree and are skipped.
Between the stale block rate chart and the list of blocks.
0xB10C
force-pushed
the
fork-observer-tree
branch
from
September 25, 2026 04:28
da8ca6c to
e7981e4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This renders the full header tree on the website showing all stale blocks, similar to a static fork-observer.