From: Dennis Sullivan <dennis.jm.sullivan@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] Are Instant Confirmations safe?
Date: Wed, 18 Mar 2015 22:38:30 +0000 [thread overview]
Message-ID: <CANMKXkMSDQHWFOR+SzZW15axjXtZVD9-tsO4+e+XDYQDNBuX5w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]
Hello. This is my first time posting to this list. I wanted to ask your
opinions on something relating to confirmation times.
I recently read about a "transaction locking" proposal which claims to make
it possible to accept 0-conf transactions with guarantee they will get
mined. This seems rather dubious to me, because if there was merit to the
system, I would have already expected to see discussion on this list
regarding it.
The scheme operates as follows:
As implemented into Darkcoin, an InstantX transaction is broadcast spending
certain outputs. Certain nodes determined deterministically will sign a
message which is relayed across the network locking this tx in mempool such
it's inputs cannot be double spent. All nodes are instructed to reject any
conflicting transactions and flush out any existing txs in the mempool that
conflict with this "locked" tx. From this point onwards, the network will
refuse to relay double spends and will also reject blocks that contain a
conflicting tx thus forcing miners to play ball.
The idea is once a transaction receives a "consensus lock" across nodes in
the mempool, the tx will eventually get mined as there is no way it can be
double spent and no way a miner can mine a double spend of the consensus
locked transaction. At the very least, this seems like it could be turned
in on itself to fork the network because of the ability to cause blocks to
be rejected. I am sure there is an attack vector there somewhere.
A full explanation is published in this paper:
https://www.darkcoin.io/wp-content/uploads/2014/09/InstantTX.pdf
Dennis
[-- Attachment #2: Type: text/html, Size: 1881 bytes --]
next reply other threads:[~2015-03-18 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 22:38 Dennis Sullivan [this message]
2015-03-18 22:53 ` [Bitcoin-development] Are Instant Confirmations safe? Natanael
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=CANMKXkMSDQHWFOR+SzZW15axjXtZVD9-tsO4+e+XDYQDNBuX5w@mail.gmail.com \
--to=dennis.jm.sullivan@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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