Repository navigation
Recognise a release's node as the reference; install programs as new files - #12
Merged
Merged
Conversation
…files
Trying the published v31.99-7 files the way a new Mac install uses them
found two faults that need a real release to show.
- The console did not recognise the release's ready-made node as its
unmodified reference. A release build names itself by its tag
("v31.99-7"), and the console only understood a commit suffix. With no
reference, every ready-made experiment asked for a compile first. The
console now resolves either, and a ready-made node is installed with a
note of the commit it was built from. Both are believed only while the
build folder has never been shared with a build of changed source, and
compiling there removes the note.
- Installing a ready-made node over an earlier one overwrote the program
in place. macOS on Apple silicon silently kills a program changed that
way after it has been run. Programs are now put in place as new files,
in the console and in the installer.
The installer no longer says the first experiment compiles the node: the
ready-made experiments do not.
Verified against the published release files: checksum and commit match,
the node is adopted as the reference, and the three changed nodes give
their documented outcomes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Why
After #11 merged, the release workflow ran for the first time and published
v31.99-7. All three platforms passed. I then used the published files on an Apple silicon Mac the way a new install uses them, before publishing the site. That found two faults that no test had caught, because both need a real release to show.v31.99-7is marked a pre-release, so it is not offered as the latest, and the site has not been updated.What was wrong and what changes
v31.99-7); the console only understood a commit suffix. With no reference, every ready-made experiment asked for a compile first, which defeats "no compiler needed"How it was checked
v31.99-7files: the checksum and commit matched, the node was adopted as the reference, and the doubled-reward, halved-reward and earlier-halving nodes gave "loosened", "tightened" and "tightened". The rule-breaking-miner scene refused all thirty blocks.Not checked
A complete install from nothing on a clean machine, and the ready-made files on Linux. The Mac app that the release built has not been opened.
Cost and effort
Cost: TBD (no rate card applies; the work is already done). Effort: S, on a scale where sizes are relative to each other and not to a calendar.
🤖 Generated with Claude Code