summaryrefslogtreecommitdiff
path: root/ac/cb029abd336de8ea0d769cd489d825e3c553e3
blob: 1a39ca5f505143b7db6160fb84f0f1ca5e76e48c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
Return-Path: <gmaxwell@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 9B6BD74
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 10 May 2016 02:12:05 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lf0-f43.google.com (mail-lf0-f43.google.com
	[209.85.215.43])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B163719A
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 10 May 2016 02:12:04 +0000 (UTC)
Received: by mail-lf0-f43.google.com with SMTP id y84so220552386lfc.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 09 May 2016 19:12:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date:message-id:subject
	:from:to:cc:content-transfer-encoding;
	bh=27UZgNedO4UUNnjWHbGOUhzDGFcbepNWPAg4Qx2AL9A=;
	b=UW66znqg6LTjjlZoknDSQV9EkUP+bwGIi2zBVGIoZvNxeMki9n3swgX5lsNFf+k64G
	6qBFEJcF0XvsRxMInrdkafEJt4nuC4l5ETZDBEZxgRzN05q4HJ0RBgkkYLqqGkhCP+G2
	EthZEdb+wWd22E7Ebm4DZGYiz2grt0jfXpJfPo3V+OdgiKROzG1VQogBnbAqSkFGyH+C
	AvFRF0muKEzKQiaGMS0clBC3N7SxY4ektV6AyD8tKTETijLZzmn0AWEm5OG78oBC2U4h
	Vo+tZMmwgOochcMEmGIbLc/rJ8rR6ttiVhYwGi5kSM+gfSW18eBM3QrXeaFOPx6EaFZr
	hqQQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:sender:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-transfer-encoding;
	bh=27UZgNedO4UUNnjWHbGOUhzDGFcbepNWPAg4Qx2AL9A=;
	b=IZKfRjGUqwEpBrhcJSBeNK7V25r+E4LivH9n4+rp2PVhLRBQNSSAhfOrvyy35GAxg2
	TJfRYnE1TG/85d3CIwEpoNPFWpoPLUSeUFO+ma63YSmK/txdngsY2dETIm0Buyjg5l4/
	QDVkNOkCc5vMD2kd40AzZU6OIqZ4G98XlmaleqPWPqVqBpa7mYBPpjClTouMXpmcAITo
	eJxdcXwGP4Lk/tT0nM96bQMDZFET8HnXwTAQniuIyMOZUHWDjOOoFJ+TD0oaAVS2fVcW
	yrfGylzrWhReKaXIPBsyhSXz6GBgce0YikWLz5vkoc7eHp4ALNiURULMA6tjISd3iIz2
	qNJg==
X-Gm-Message-State: AOPr4FUBVOEywOwadSHQBrgEUX2WHwegCX22bEnMInwZtIV9UV6eTMcMKM4JLXo8lJO5VLvplBXenKUtAbtS0g==
MIME-Version: 1.0
X-Received: by 10.25.77.204 with SMTP id a195mr16967617lfb.14.1462846323121;
	Mon, 09 May 2016 19:12:03 -0700 (PDT)
Sender: gmaxwell@gmail.com
Received: by 10.112.65.108 with HTTP; Mon, 9 May 2016 19:12:03 -0700 (PDT)
In-Reply-To: <5C2809F9-286D-49E4-89DB-7109B73F6076@gmx.com>
References: <5727D102.1020807@mattcorallo.com> <86058327.pdmfHP132A@kiwi>
	<CAAS2fgRiSNNHA5psaUYOM6rHfjJ1aOgWhnsT8Z-pU4FBcR_65w@mail.gmail.com>
	<2273040.Bd6rtJjYLF@garp>
	<CAAS2fgR01=SfpAdHhFd_DFa9VNiL=e1g4FiguVRywVVSqFe9rA@mail.gmail.com>
	<CAAS2fgRL1=YSrAZVES0WBySyL1brZcvQsvZdsqUEY2-8UOFFiA@mail.gmail.com>
	<5C2809F9-286D-49E4-89DB-7109B73F6076@gmx.com>
Date: Tue, 10 May 2016 02:12:03 +0000
X-Google-Sender-Auth: QfQGgRhoNcYgSC-1Qs4mTPT8NX8
Message-ID: <CAAS2fgR8j5QJkVb2rEfpi27OvN4gVw2ROaehLRvsojQd7yrpXg@mail.gmail.com>
From: Gregory Maxwell <greg@xiph.org>
To: Peter R <peter_r@gmx.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: Bitcoin Development Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Compact Block Relay BIP
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 02:12:05 -0000

On Mon, May 9, 2016 at 11:37 PM, Peter R <peter_r@gmx.com> wrote:
> It is a standard result that there are
>     m! / [n! (m-n)!]
> ways of picking n numbers from a set of m numbers, so there are
>
>     (2^32)! / [2! (2^32 - 2)!] ~ 2^63
> possible pairs in a set of 2^32 transactions.  So wouldn=E2=80=99t you ha=
ve to perform approximately 2^63 comparisons in order to identify which pai=
r of transactions are the two that collide?
>
> Perhaps I made an error or there is a faster way to scan your set to find=
 the collision.  Happy to be corrected=E2=80=A6

$ echo -n Perhaps. 00000000f2736d91 |sha256sum
359dfa6d4c2eb2ac81535392d68af4b5e1cb6d9c6321e8f111d3244329b6a4d8
$ echo -n Perhaps. 0000000011ac0388 |sha256sum
359dfa6d4c2eb2ac44d54d0ceeb2212500cb34617b9360695432f6c0fde9b006

Try search term "collision", or there may be an undergrad Data
structures and algorithms coarse online-- you want something covering
"cycle finding".

(Though even ignoring efficient cycle finding, your factorial argument
doesn't hold... you can simply sort the data... Search term
"quicksort" for a relevant algorithm).