Conversation
…chain.com scan.sentrixchain.com remains the primary explorer with full native-op coverage. Blockscout sidecar adds EVM-standard UX (ERC-20 holders, source verification, EIP-3091 URLs) for listing platforms + EVM tooling that expects that shape.
slashing.rs was 954 LOC carrying three independent concerns:
- LivenessTracker (sliding-window downtime detector) +
LIVENESS_WINDOW / MIN_SIGNED_PER_WINDOW / DOWNTIME_SLASH_BP /
DOWNTIME_JAIL_BLOCKS constants
- DoubleSignEvidence + DoubleSignDetector + DOUBLE_SIGN_SLASH_BP
- SlashingEngine (the orchestrator) + tests
Pulled out the first two into slashing/{liveness,double_sign}.rs.
slashing.rs drops to 728 LOC, focused on SlashingEngine + tests.
Pure mechanical extraction — public API at sentrix_staking::slashing::*
unchanged via re-exports.
Phase 3 follow-on of the workspace audit.
1 task
satyakwok
added a commit
that referenced
this pull request
Apr 29, 2026
* docs: dual-explorer note for Blockscout sidecar at blockscout.sentrixchain.com scan.sentrixchain.com remains the primary explorer with full native-op coverage. Blockscout sidecar adds EVM-standard UX (ERC-20 holders, source verification, EIP-3091 URLs) for listing platforms + EVM tooling that expects that shape. * chore: humanize the just-extracted submodule headers The recent batch of refactor PRs (#419 explorer, #420 bft engine, #421 slashing) shipped with header comments that read a bit like a release- notes generator wrote them — "X.rs — short description. Pulled out of Y for Z. No behaviour change." That's not the voice the rest of this codebase carries. Comments here usually tell stories, reference incidents, drop dates and PR numbers. This pass rewrites the seven new file headers + the two re-export blocks so they sound like the operator wrote them late at night, which is closer to the truth. No code change. --------- Co-authored-by: Satya Kwok <satyakwik@gmail.com> Co-authored-by: satyakwok <satyakwok@users.noreply.github.com> Co-authored-by: Satya Kwok <satyakwik@users.noreply.github.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
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.
Summary
Phase 3 follow-on of the workspace audit.
slashing.rswas 954 LOC mixing three independent concerns:LIVENESS_WINDOW/MIN_SIGNED_PER_WINDOW/DOWNTIME_SLASH_BP/DOWNTIME_JAIL_BLOCKSconstantsDOUBLE_SIGN_SLASH_BPconstantPulled out the first two into
slashing/{liveness,double_sign}.rs.slashing.rsdrops to 728 LOC, focused on SlashingEngine + its 100 tests.Pure mechanical extraction — public API at
sentrix_staking::slashing::*unchanged via re-exports.Test plan