Feature/sc 002 claim lifecycle - #338
Merged
Merged
Conversation
added 3 commits
July 28, 2026 21:16
- Add VerificationAggregation contract with ClaimOutcome enum, AggregationResult struct - Implement deterministic weighted consensus: TRUE/FALSE weight calculation, confidence scoring - Add configurable thresholds: min verification count, min total stake, min confidence - Handle ties deterministically (INCONCLUSIVE) - Emit ClaimAggregated event for indexers - Add IVerificationSource interface for future extensibility (reputation weighting, quadratic voting, etc.) - Add view functions to TruthBountyWeighted for voter iteration: getClaimVoterCount, getClaimVoterAt, getVerificationWeight, getVerificationSupport, getClaimVerificationWindowEnd, getClaimSubmitter - Write comprehensive Foundry tests: successful cases, tie handling, determinism, stress tests, gas benchmarks - Pure integer arithmetic, no floating-point - Order-independent aggregation guarantees identical output across all nodes
…SC-009) - Rewrite ReputationDecay.sol: inherit GovernanceOwnable, minimum reputation floor, inactivity tracking, linear decay, recordActivity, applyDecay, view functions, full IReputationOracle compliance. - Rewrite tests (ReputationDecay.ts, RBAC.test.ts): 57 tests across deployment, decay, governance, access control, edge cases. - Add Foundry fuzz tests (test/fuzz/ReputationDecayFuzz.t.sol). - Fix pre-existing compilation errors in BootstrapController.sol and MigrationManager.sol (missing PAUSER_ROLE). Enable viaIR in hardhat config for stack-too-deep in RewardEngine.sol.
Contributor
|
resolve conflicts @Tobi-8 |
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
2 participants
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
Implement the canonical Claim Lifecycle State Machine (SC-002) defining all legal
claim state transitions and preventing invalid protocol behaviour.
ClaimStatusenum: Pending, UnderVerification, VerificationEnded, UnderDispute,VerifiedTrue, VerifiedFalse, Inconclusive, Cancelled
_canTransition(current, next)— pure validator for all state machine rules_startVerification,_endVerification,_markVerifiedTrue,_markVerifiedFalse,_markInconclusive,_openDispute,_cancelClaim— each validates transition, updates storage, emits eventClaimStatusChangedevent with indexedclaimIdandactorfor fullon-chain history reconstruction
dispute deadline — all checked against
block.timestampisPending,isUnderVerification,isResolved,isDisputed,canReceiveVotes,canBeCancelled__gap[50]for upgrade-safe storageGas Benchmarks
Testing
_canTransition)validateTransitionrevert on illegal, pass on legalCloses #282