From: Peter Todd <pete@petertodd•org>
To: Adrian Macneil <adrian@coinbase•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Double spending and replace by fee
Date: Tue, 21 Apr 2015 07:37:14 -0400 [thread overview]
Message-ID: <20150421113714.GA3455@savin.petertodd.org> (raw)
In-Reply-To: <C92CBBFE-A967-457B-B356-AF85F7BE8936@coinbase.com>
[-- Attachment #1: Type: text/plain, Size: 2215 bytes --]
On Wed, Apr 08, 2015 at 11:28:08PM -0700, Adrian Macneil wrote:
> Fwiw, Coinbase relies on the current first-seen mempool behaviour. Wide adoption of RBF (without a suitable replacement available) would make it extremely difficult to pitch bitcoin as a viable alternative to credit cards payments to large merchants.
Some questions:
1) Are you contractually obliged to accept zeroconf transactions with
existing customers?
I keep hearing rumors of this, but would like some confirmation. In
particular, it would be good to know if you have the option of turning
zeroconf off at all, contractually speaking.
2) What are your double-spend losses to date?
3) Are you actively marketing zeroconf guarantees to new customers?
You're API is a bit unclear as to what exactly those guarantees are;
looks like they only apply if a merchant has "convert to fiat" turned
on.
4) What are your short, medium, and long term plans to move away from
dependency on "first-seen" mempool policy?
e.g. hub-and-spoke payment channels, Lightning network, off-chain, etc.
5) What is your plan for new Bitcoin Core releases that break zeroconf
via changed tx acceptance rules?
Basically every release we've ever made has added a zeroconf exploit due
to different tx acceptance rules. (e.g. my 95% success rate last summer)
6) What are your plans for Bitcoin Core releases that fundementally
break zeroconf?
For instance changes like limiting the mempool size create zeroconf
vulnerabilities that can't be avoided in many situations. Yet they may
also be unavoidably needed for, for instance, DoS protection. Will you
oppose these improvements?
7) If a mining pool adopts adopted policy that broke zeroconf, e.g.
replace-by-fee, would you take any action?
8) Would you take legal action against a mining pool for adopting
replace-by-fee publicly?
9) Would you take action against a mining pool who is mining
double-spends without explanation?
e.g. one that claims not to be running non-Bitcoin Core policy, but
keeps on mining double-spends.
--
'peter'[:-1]@petertodd.org
0000000000000000089abd68efc18c03d2a294295f3706a13966613a3ff3b390
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
prev parent reply other threads:[~2015-04-21 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 13:58 Mike Hearn
2015-03-28 14:22 ` Peter Todd
2015-04-09 6:28 ` Adrian Macneil
2015-04-21 11:37 ` Peter Todd [this message]
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=20150421113714.GA3455@savin.petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=adrian@coinbase$(echo .)com \
--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