docs: Add technical details for hit calculation #88
Conversation
The `docs/epow/technical-explanation.md` file was missing a detailed explanation of how the `hit` value is calculated in the ePoW consensus mechanism. This commit adds a new section that breaks down the `hit` calculation step-by-step. It also corrects the description of the main mining loop to clarify that randomness is introduced via the Argon2id salt, allowing miners to perform many unique hash attempts per second. This ensures the documentation is now technically accurate and provides a clearer understanding of the mining process.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
The technical explanation for ePoW was missing details on how the 'hit' value is calculated. This change adds a new section that explains the entire process, from creating the base string to the final formula. It also corrects the description of the mining loop to clarify how miners can make multiple, unique hash attempts per second.
PR created automatically by Jules for task 10319054092244654842 started by @attogram