Report settled wallet repetition separately from caller identity - #178
Merged
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
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.
Anonymous wallets can pay repeatedly while
repeat_paid_callersstays zero because the operation history has no caller key. Add a separatesettled_payer_activityaggregate to global revenue and commercial reports so confirmed wallet repetition is visible without treating it as agent identity, independent ownership or useful work.The read-only aggregate groups by EVM network and payer address, counts distinct transactions, excludes known first-party settlements, and discloses invalid or conflicting bindings. Duplicate ledger records cannot create repetition. Existing revenue totals, caller metrics and scoped experiment eligibility remain unchanged; individual wallet identifiers are not added to the aggregate.
Validation: the new anonymous-repeat case failed before the change. Twelve regression cases cover anonymity, case normalization, network separation, duplicate/conflicting records, first-party and unconfirmed exclusion, incomplete bindings, scoped experiments and both public routes. Focused checks: 28 passed. Full local suites: JSON 2,018 passed / 17 skipped; SQLite 2,019 passed / 16 skipped. Contract regeneration produced no drift.