Double-Spend Proof (DSP)
Basics
- From this (3-9-2019) Bitcoin.com article:
"The Flowee developer Tom Zander published the DSP specification on August 30 and open-sourced the code on Gitlab as well. The DSP is an adaption of Chris Pacia’s double-spend alert and Imaginary Username and Mark Lundeberg also contributed to the Flowee version. The documentation explains how the infrastructure is designed to detect double spends and SPV-based warnings can be sent to the merchant. Merchants still need to follow some protocol in order to check the validity of a received transaction that pays them. The Flowee DSP concept describes how cryptographic evidence can prevent someone from double spending and defrauding merchants. The DSP specification explains that the ability to double check zero-confirmation transactions will add great confidence to the ecosystem. “We expect this will help with countering undetected attempts of double spends,” the Gitlab description notes."
