feat(privacy): add amount-based privacy term - #2
Open
bc1cindy wants to merge 5 commits into
Open
Conversation
arminsabouri
force-pushed
the
develop
branch
from
September 4, 2026 22:01
a876183 to
9a2d17c
Compare
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.
adds
PrivacyTerm::evaluate(mine, theirs) -> [0,1]: each of my coins gets a score for how well it hides among the other users' amounts, combined with a generalized mean, which is a formula where the exponent slides from "worst coin dominates" (min) through harmonic and arithmetic up to max. Default is harmonic (-1.0), so a poorly covered coin drags the result downper-coin scoring lives behind the
CoinScoretrait, with a placeholder for now and the real subset-sum backend plugs in later without changing the term. The "dense enough" threshold semantics land with that backend, where the count gets normalized.property-tested: the result stays in [0,1] (empty mine -> 1.0). adding a not-mine amount never lowers the term, for any exponent. The optimized mean matches a naive implementation of the power-mean definition (oracle)
closes #1