From: Mike Hearn <mike@plan99•net>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Double spending and replace by fee
Date: Sat, 28 Mar 2015 14:58:53 +0100 [thread overview]
Message-ID: <CANEZrP3Prp6EFUdH_VDWkq508HkeFBMn+swzZ9ycAMsrOazFZA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
I've written a couple of blog posts on replace by fee and double spending
mitigations. They sum up the last few years (!) worth of discussions on
this list and elsewhere, from my own perspective.
I make no claim to be comprehensive or unbiased but I keep being asked
about these topics so figured I'd just write up my thoughts once so I can
send links instead of answers :) And then so can anyone who happens to
agree.
(1) Replace by fee scorched earth, a counter argument:
https://medium.com/@octskyward/replace-by-fee-43edd9a1dd6d
This article lays out the case against RBF-SE and argues it is harmful to
Bitcoin.
(2) Double spending and how to make it harder:
https://medium.com/@octskyward/double-spending-in-bitcoin-be0f1d1e8008
This article summarises a couple of double spending incidents against
merchants and then discusses the following techniques:
1. Risk analysis of transactions
2. Payment channels
3. Countersigning by a trusted third party
4. Remote attestation
5. ID verification
6. Waiting for confirmations
7. Punishment of double spending blocks
I hope the material is useful / interesting.
[-- Attachment #2: Type: text/html, Size: 1557 bytes --]
next reply other threads:[~2015-03-28 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 13:58 Mike Hearn [this message]
2015-03-28 14:22 ` Peter Todd
2015-04-09 6:28 ` Adrian Macneil
2015-04-21 11:37 ` Peter Todd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANEZrP3Prp6EFUdH_VDWkq508HkeFBMn+swzZ9ycAMsrOazFZA@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox