Claude 6d111626ee fix(bolt12): don't let an unverified proof grief a verified zap total ...

The payment-hash dedup kept the LOWER amount and OR'd cryptoVerified across
entries. Because a payer proof publishes its proof_preimage, once a BOLT12 zap
is public anyone can replay its payment hash in a compressed (unverifiable)
proof with a 1-msat amount; the merge would keep that amount AND inherit the
verified flag, driving the counted total to ~zero and mislabeling a fabricated
amount as verified.

Per the NIP, dedup by invoice_payment_hash applies among *validated* proofs.
Only a crypto-verified proof has a signature-bound amount, so a verified entry
now always wins over an unverified duplicate; the lower-amount rule applies only
between entries of the same verification status. Adds a two-order regression
test for the replay-griefing case.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SpgpWLKzgD7vS9Fs4CXTR3

2026-07-24 20:16:38 +00:00

..

plans

docs(plan): record note-ui-commons extraction progress + findings

2026-07-17 22:50:09 +00:00

src

fix(bolt12): don't let an unverified proof grief a verified zap total

2026-07-24 20:16:38 +00:00

.gitignore

Starting a new module for app benchmarks

2024-02-05 18:18:33 -05:00

ARCHITECTURE.md

Removes Threading checks on Commons since Main Threads don't exist over there.

2026-06-15 10:41:40 -04:00

build.gradle.kts

chore(deps): update dependencies across all modules

2026-07-19 14:06:37 +00:00

consumer-rules.pro

Starting a new module for app benchmarks

2024-02-05 18:18:33 -05:00

proguard-rules.pro

build: remove unused :ammolite module

2026-05-16 14:40:03 +00:00