š
Original date posted:2013-11-05
š Original message:On Tue, Nov 5, 2013 at 12:14 PM, Peter Todd <pete at petertodd.org> wrote:
> On Tue, Nov 05, 2013 at 12:05:41PM -0500, Peter Todd wrote:
> > On Tue, Nov 05, 2013 at 11:56:53AM -0500, Ittay wrote:
>
> Oh, and I don't want to give the wrong impression: there's no need to
> rush to get this problem fixed. Even if someone wanted to launch an
> attack right now, with a fair amount of resources, there's a lot of
> counter-measures based on human intervention that can definitely stop
> the attack in the short-term
The attack can be easily hidden. And be sure that before today, today,
and after today, very smart people are at their computer planning attacks
on Bitcoin. Exploits must be published and fixed FAST.
Nevertheless, I agree that, as you say, we must not rush it. Look at the
BIP, find if we missed anything, and let's discuss it.
> In addition, keep in mind
> that this attack is very easy to detect, so if one is actually launched
> we will know immediately and can start taking direct counter-measures at
> that time.
>
Not really. Please see the discussion section in our paper.
> That Gregory Maxwell so quickly identified a flaw in this proposed
> solution suggests we should proceed carefully.
>
There is no flaw. You were just reiterating that the solution does not give
us the 51% percent security you thought you had before. We showed that
we're not getting this back, I'm afraid.
Best,
Ittay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131105/8c0bd106/attachment.html>;
Ittay [ARCHIVE] /
npub1n8ā¦637cg
2023-06-07 15:08:50
in reply to nevent1qā¦47sg
Author Public Key
npub1n8ytpf4jzavm7hl9t5zksuefcguu6k3frvztqqc4kgcdkwduqesq0637cgPublished at
2023-06-07 15:08:50Event JSON
{
"id": "7b260b570f6f1ad24dd928c0be8fae5843a100c7ff4792836fd33b5354cf20c7",
"pubkey": "99c8b0a6b21759bf5fe55d05687329c239cd5a291b04b00315b230db39bc0660",
"created_at": 1686150530,
"kind": 1,
"tags": [
[
"e",
"6d3f2b033dee2609b17c739a2c08a8dad9f58ca1e382056f88a3fdcc51c33a75",
"",
"root"
],
[
"e",
"c4c6e2ba50326f4ac6f72d61a6a94c16ed66b88d50d1d6314ea8ce092f5ddbd5",
"",
"reply"
],
[
"p",
"daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa"
]
],
"content": "š
Original date posted:2013-11-05\nš Original message:On Tue, Nov 5, 2013 at 12:14 PM, Peter Todd \u003cpete at petertodd.org\u003e wrote:\n\n\u003e On Tue, Nov 05, 2013 at 12:05:41PM -0500, Peter Todd wrote:\n\u003e \u003e On Tue, Nov 05, 2013 at 11:56:53AM -0500, Ittay wrote:\n\u003e\n\u003e Oh, and I don't want to give the wrong impression: there's no need to\n\u003e rush to get this problem fixed. Even if someone wanted to launch an\n\u003e attack right now, with a fair amount of resources, there's a lot of\n\u003e counter-measures based on human intervention that can definitely stop\n\u003e the attack in the short-term\n\n\nThe attack can be easily hidden. And be sure that before today, today,\nand after today, very smart people are at their computer planning attacks\non Bitcoin. Exploits must be published and fixed FAST.\n\nNevertheless, I agree that, as you say, we must not rush it. Look at the\nBIP, find if we missed anything, and let's discuss it.\n\n\n\u003e In addition, keep in mind\n\u003e that this attack is very easy to detect, so if one is actually launched\n\u003e we will know immediately and can start taking direct counter-measures at\n\u003e that time.\n\u003e\n\nNot really. Please see the discussion section in our paper.\n\n\n\u003e That Gregory Maxwell so quickly identified a flaw in this proposed\n\u003e solution suggests we should proceed carefully.\n\u003e\n\nThere is no flaw. You were just reiterating that the solution does not give\nus the 51% percent security you thought you had before. We showed that\nwe're not getting this back, I'm afraid.\n\nBest,\nIttay\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131105/8c0bd106/attachment.html\u003e",
"sig": "bc125eacdcd1400d4b242a6e2fcd2fc732536391010bca0f1f3d633144d63d4df71bab6b1c1abd752a22587ceac7a6f5e814ea01367c033f60fae3fea579aec6"
}