Dennis Sullivan [ARCHIVE] / is on Nostr

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2015-03-18 to 2015-03-18
💬 Posted a total of 1 messages
📚 Participated in the following categories:
🔇 Please do not DM this user as it's used for archive purposes only.

Last Notes

2023-06-07 15:32:11

- reply

📅 Original date posted:2015-03-18
📝 Original message: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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150318/6f45755c/attachment.html>

2023-06-07 15:32:11

- reply