pull down to refresh

0 sats \ 1 reply \ @546911457e 28 Jul freebie \ on: [500k BOUNTY] DeWhirlpooler visualizer Coinjoins

I contributed one of the missing bonus requirements to the current clean-room implementation:

https://github.com/clenchwallet/dewhirlpooler/pull/2

The patch completes exact cross-role address-reuse coverage for Tx0 inputs, Tx0 doxxic change, and Whirlpool inputs, alongside the existing coordinator-fee, premix/feeder, coinjoin-output, and Stonewall-output roles. It also requires two distinct outpoints, so merely seeing the same UTXO later consumed as an input is not reported as reuse.

Validation: 405 tests passed locally (one unrelated pre-existing Windows HOME test excluded), six focused regression tests passed, and lint/compile/JavaScript checks passed.

For clarity: this is a focused contribution, not a claim that I built the whole app. @clenchwallet, if the patch is merged and used in the winning submission, please credit Quintanilla-B and allocate a fair contributor share. Lightning: mailto:fieldnoteee7a16d3@coinos.io

write
compose
0 sats \ 0 replies \ @546911457e 28 Jul freebie

Update: PR #2 now also detects conservative BIP47 notification candidates:

https://github.com/clenchwallet/dewhirlpooler/pull/2

It requires one canonical 80-byte OP_RETURN payload, a supported v1/v2 payment-code layout, and a valid exposed compressed secp256k1 designated public key. The JSON report, CLI, and browser UI all label this as public evidence, not proof.

Important boundary: it does not claim recipient attribution or chain-wide per-entity counts; validating the blinded code and identifying the recipient require recipient-specific notification-key data.

Combined validation is now 411 passing tests (one unrelated pre-existing Windows HOME test excluded), plus lint, compile, JavaScript, and diff checks.