feat: add Antiquity Benchmarker utility for hardware auditing #82
Conversation
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
Author
|
Update: I've cross-referenced the implementation with RIP-200 specs. I admit the earlier documentation for multipliers was slightly vague regarding ARM architectures; I have clarified this in the code comments and adjusted the benchmark thresholds to match the core logic. Ready for final review. @Scottcjn |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR adds a new utility script �ntiquity_benchmarker.py that allows users to quickly audit their local hardware and see their antiquity multiplier based on the cpu_architecture_detection.py logic. This helps users understand the 'Proof-of-Antiquity' concept and their potential earnings before starting the miner.