Repository navigation
Offender rule: 10% of 200 shares, not 0.5% of 50; honest v0.5.0beta wording - #83
Merged
Merged
Conversation
…f 50 Every build, v0.5.0beta included, mines the odd pool-only share right after a reconnect or a new height. On 2026-10-19 every live session but two was at 1.1% or less; the two gateways that pay only the pool were at 99.98%. The old line (0.5% of 50+ accepted) warned Knotzi, on v0.5.0beta, for ~15 minutes after one such share, and the fee wallet would have charged the custody fee in that window. New line, same in the fee wallet and admin dashboard (lazarus-ops): at least 10% of 200 or more accepted. The block half of the rule (latest block in 30 days pool-only or partial) is unchanged. On live data it drops 2 of 15 flagged identities, both one-share blips. Wording: v0.5.0beta is the current release, but its blocks still come out partial at times, so the site and MCP no longer imply that updating ends it. The miner-page notice says "producing bad coinbases" and clears once the next block splits; MCP gateway_status tells a current build that is flagged to wait for its next block or ask on Discord instead of "update"; FAQ 2026-10-19.2. Tests: pool 9 files pass, site build/indexing/lastmod/language pass, MCP 147 pass. 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.
Every build, v0.5.0beta included, mines the odd pool-only share right after a reconnect or a new
height. On 2026-10-19 every live session but two was at 1.1% or less; the two gateways that pay
only the pool were at 99.98%. The old line (0.5% of 50+ accepted) warned Knotzi, on v0.5.0beta,
for ~15 minutes after one such share, and the fee wallet would have charged the custody fee in that
window. New line, same in the fee wallet and admin dashboard (lazarus-ops): at least 10% of 200 or
more accepted. The block half of the rule (latest block in 30 days pool-only or partial) is
unchanged. On live data it drops 2 of 15 flagged identities, both one-share blips.
Wording: v0.5.0beta is the current release, but its blocks still come out partial at times, so
the site and MCP no longer imply that updating ends it. The miner-page notice says "producing bad
coinbases" and clears once the next block splits; MCP gateway_status tells a current build that
is flagged to wait for its next block or ask on Discord instead of "update"; FAQ 2026-10-19.2.
Tests: pool 9 files pass, site build/indexing/lastmod/language pass, MCP 147 pass.
🤖 Generated with Claude Code