summaryrefslogtreecommitdiff
path: root/8c/972d3b2acae9f6a696a01d28564b38c5efc262
blob: 813a6f19cd7bc2128ef39a3f6f6112c9b816599b (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
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jgarzik@exmulti.com>) id 1SfYVS-0003ky-FU
	for bitcoin-development@lists.sourceforge.net;
	Fri, 15 Jun 2012 15:32:14 +0000
X-ACL-Warn: 
Received: from mail-lpp01m010-f47.google.com ([209.85.215.47])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1SfYVR-0007zJ-CG
	for bitcoin-development@lists.sourceforge.net;
	Fri, 15 Jun 2012 15:32:14 +0000
Received: by lags15 with SMTP id s15so2375877lag.34
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 15 Jun 2012 08:32:06 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type:x-gm-message-state;
	bh=waV5IoPClWFdBTpMBF4hBMD0rSh4/h/JHpO1Sb0f6Mc=;
	b=PYAMZSe4UD5OGK2fU9wOGh/r31ChP1u0fSdynnaYI5n5SphcUZmdEVdTA8oJeAehmM
	M8h9Ex/NWsQnkQdPYvbGFfX+CVo4Ih1OAugiWyenpPqc83L9eBKZA4UsORzCscW+eW6f
	prVbX3BXrvbwb1Rl5m6UDQCMLWndzYaOno8wwPEqkYXGyknQpNo6yje53ms9NFCH/lgI
	5UThLUZsAkCgUBSbDQHnvtk7yMPWZ7212LG56eDKQvA0QjabJVM1ILTJXdsUwOVvVZui
	3cmmjrnoiy7U6m2IfQWJnCTkK5HKAhRVCa+I8fobOVWb1Jdo5Jvk6g4hpDWJpyWP5qxn
	23hQ==
MIME-Version: 1.0
Received: by 10.152.148.169 with SMTP id tt9mr5857750lab.49.1339774326280;
	Fri, 15 Jun 2012 08:32:06 -0700 (PDT)
Received: by 10.114.19.70 with HTTP; Fri, 15 Jun 2012 08:32:06 -0700 (PDT)
X-Originating-IP: [2001:4830:1603:2:21c:c0ff:fe79:c8c2]
In-Reply-To: <CANEZrP39RHfCDX-x4ARo+oPphLv-70RxuMh3+AJzsNPxzOd=bA@mail.gmail.com>
References: <CA+8xBpecVQcTTbPxUm_3_GWC99dEd4=-VFWb+QT6jUy4rg8U4w@mail.gmail.com>
	<CANEZrP0kNZDByHpK2=UjP+ag0X1KmqHxnJdm=e_pWMitP4QvvA@mail.gmail.com>
	<CA+8xBpcwhQPQRe=stYb9xksLsTbiABKLS7PZnRtvPga6AmSg4Q@mail.gmail.com>
	<CANEZrP39RHfCDX-x4ARo+oPphLv-70RxuMh3+AJzsNPxzOd=bA@mail.gmail.com>
Date: Fri, 15 Jun 2012 11:32:06 -0400
Message-ID: <CA+8xBpfHpMX5FUJz4HSYxOoeDEGZ0S4Ufz1pRYbwJLcPiVw_CA@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnDVaplzL0gWGqaNDWcgseWxLzkt/3q5hwbLLQnfs/0nQpA7gapstAkXPi1f9ZsjCEaWEeb
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1SfYVR-0007zJ-CG
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] New P2P commands for diagnostics,
	SPV clients
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 15:32:14 -0000

On Fri, Jun 15, 2012 at 9:43 AM, Mike Hearn <mike@plan99.net> wrote:
> How about see this project as a three part change?
>
> First step - add the mempool command and make nodes sync up their
> mempools on startup.

Here's the "mempool" implementation:
https://github.com/bitcoin/bitcoin/pull/1470

SPV nodes would definitely want to sync up their mempool upon startup.
 As for full nodes... I like the organic growth and random nature of
the mempools.  On the fence, WRT full node mempool sync at startup.

-- 
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com