From: Tao Effect <contact@taoeffect•com>
To: Anthony Towns <aj@erisian•com.au>
Cc: Anthony Towns via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Replay attacks make BIP148 and BIP149 untennable
Date: Tue, 6 Jun 2017 16:31:17 -0700 [thread overview]
Message-ID: <A6627D4B-F127-4213-A4B0-8040CF91F3CD@taoeffect.com> (raw)
In-Reply-To: <38DDC3A2-2727-477E-A6FF-7638842AAB03@taoeffect.com>
[-- Attachment #1.1: Type: text/plain, Size: 1761 bytes --]
> CPFP can be used by an attacker to get your original txn into the 148 chain.
*err, my bad that's unlikely to happen, if I remember correctly CPFP can only be done by the person you're sending the coins to. Coin-mixing seems the better option of the two, but shouldn't the BIP148 folks wait until it's clear that will be supported by exchanges?
--
Please do not email me anything that you are not comfortable also sharing with the NSA.
> On Jun 6, 2017, at 4:27 PM, Tao Effect <contact@taoeffect•com <mailto:contact@taoeffect•com>> wrote:
>
>> CoinJoin works as a method of both improving fungibility and mixing with
>> coinbase transactions.
>
> My understanding is that the two situations are quite different.
>
> Unlike mixing to coin-split, CoinJoin doesn't create a high demand exclusively for coinbase transactions.
>
> However, of the proposed methods, coin-mixing seems the better option, because it might be reasonably easy (I don't know) for exchanges to obtain 148 coinbase coins, and mix their coins with them, extending the coin-splitting capability beyond just miner coins and then using that to split incoming coins.
>
> That seems like the most reasonable approach I've heard so far. Whether exchanges would be willing to do that is a separate question.
>
>> When it's confirmed on one chain, but not on the other, you
>> can then "double-spend" on the lower hashrate chain with a higher fee,
>> to end up with different coins on both chains.
>
> This method is time consuming and not guaranteed to work. CPFP can be used by an attacker to get your original txn into the 148 chain.
>
>> (also, no double-n in untenable)
>
> Why thank you aj, you're so good at spelling. :-)
>
> Cheers,
> Greg
>
[-- Attachment #1.2: Type: text/html, Size: 5334 bytes --]
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-06-06 23:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 22:39 Tao Effect
2017-06-06 23:02 ` Gregory Maxwell
2017-06-06 23:12 ` Tao Effect
2017-06-07 13:25 ` Nick Johnson
2017-06-07 16:27 ` Tao Effect
2017-06-07 17:35 ` Nick Johnson
2017-06-08 5:44 ` Conner Fromknecht
2017-06-08 6:38 ` Nick Johnson
2017-06-06 23:08 ` Luke Dashjr
2017-06-06 23:19 ` Tao Effect
2017-06-06 23:20 ` Anthony Towns
2017-06-06 23:27 ` Tao Effect
2017-06-06 23:31 ` Tao Effect [this message]
2017-06-06 23:59 ` Kekcoin
2017-06-07 0:04 ` Tao Effect
2017-06-07 0:19 ` Kekcoin
2017-06-07 0:26 ` Tao Effect
2017-06-07 0:29 ` Kekcoin
2017-06-07 0:38 ` Tao Effect
2017-06-07 0:46 ` Kekcoin
-- strict thread matches above, loose matches on Subject: below --
2017-06-06 20:43 Tao Effect
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=A6627D4B-F127-4213-A4B0-8040CF91F3CD@taoeffect.com \
--to=contact@taoeffect$(echo .)com \
--cc=aj@erisian$(echo .)com.au \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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