Repository navigation
node: Jarek confirms chain snapshots, as an operator and not a pin - #218
Merged
Merged
Conversation
Adds Jarek (Byron Bay, btxchain/btx#239) to the snapshot operator list with his validator's key 02d12c32. A statement he and the 3060 both signed counts as confirmed, so a new node starts from it instead of block 245,300. His key is not added to the mirrors' pins: it confirms snapshots, has no authority over blocks, and trim_to_pinned keeps it away from the engine. The test uses the real mainnet manifests both signed at 251,000 (the same 229-byte statement, the same file): each alone is one operator, merged they confirm as Mende and Jarek, and only the 3060's signature reaches the engine. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 17, 2026
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
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.
Adds Jarek (Byron Bay, btxchain/btx#239) to
crates/btx-core/snapshot-operators.jsonwith his validator's key02d12c32…fe030.What it changes. A statement Jarek and the 3060 both signed now counts as two operators, so it is confirmed and new nodes start from it instead of the compiled pair at 245,300. His cuts land on every multiple of 1,000, so a new node would start at most about a day from the tip.
What it does not change. His key is not added to
mirror_pins/BTX_TRUSTED_ATTESTATION_PUBKEYS: it has no authority over blocks, andtrim_to_pinnedkeeps his signature away from the engine. TheAuthorityNamespacedoes not move.Evidence
3d539a87…).confirmed_snapshot::tests::mende_and_jarek_confirm_251000_on_mainnetruns on the two real mainnet manifests (new fixtures). Each alone is refused as one operator. Merged, they confirm as["Mende", "Jarek"], and only the 3060's signature reaches the engine.snapshot-rendezvous-local.mjs) on the real 251,000 manifests and file. After the pickup job ran,latestserved 251,000 confirmed by Mende and Jarek.attested_snapshot::prepare_confirmeddownloaded the pair, checked it, and handed 1 of 2 signatures. That last check was a temporary test and is not committed.Tests:
cargo test --libin btx-core: 1203 passed.apps/nodevitest: 280 passed.cargo checkinsrc-tauricould not run in this fresh worktree, because the git-ignoredresources/node-pkgis not staged there.The website side, with the same list and an hourly job that picks up his cuts as co-signatures only, is MendeMatthias/EasyBTX (linked below). Per
check-snapshot-operators.mjs, it merges after the release that carries this list. The release is stacked on this PR.🤖 Generated with Claude Code