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.
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.