summaryrefslogtreecommitdiff
path: root/c3/b9ebfd6cfd6544567a7b5916c52c637d26b31d
blob: ef112c5856a1ca8c99d01c20ab31df04cde361d1 (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
102
103
104
105
106
107
108
109
110
111
112
113
114
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <doug@bitcoinarmory.com>) id 1YqpO6-0008Lm-Jo
	for bitcoin-development@lists.sourceforge.net;
	Fri, 08 May 2015 21:00:50 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of
	bitcoinarmory.com designates 157.56.110.102 as permitted
	sender) client-ip=157.56.110.102;
	envelope-from=doug@bitcoinarmory.com;
	helo=na01-bn1-obe.outbound.protection.outlook.com; 
Received: from mail-bn1bn0102.outbound.protection.outlook.com ([157.56.110.102]
	helo=na01-bn1-obe.outbound.protection.outlook.com)
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1YqpO3-0001mS-7N
	for bitcoin-development@lists.sourceforge.net;
	Fri, 08 May 2015 21:00:50 +0000
Authentication-Results: lists.sourceforge.net; dkim=none (message not signed)
	header.d=none;
Received: from [192.168.1.230] (209.6.53.207) by
	BLUPR0601MB1458.namprd06.prod.outlook.com (25.163.85.28) with Microsoft
	SMTP Server (TLS) id 15.1.154.19; Fri, 8 May 2015 19:27:35 +0000
Message-ID: <554D0E1E.8070905@bitcoinarmory.com>
Date: Fri, 8 May 2015 15:27:26 -0400
From: Douglas Roark <doug@bitcoinarmory.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10;
	rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [209.6.53.207]
X-ClientProxiedBy: CO2PR11CA0024.namprd11.prod.outlook.com (10.141.242.162) To
	BLUPR0601MB1458.namprd06.prod.outlook.com (25.163.85.28)
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR0601MB1458;
X-Microsoft-Antispam-PRVS: <BLUPR0601MB14580870B3F694035910BDE1C2DE0@BLUPR0601MB1458.namprd06.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0;
	RULEID:(601004)(5005006)(3002001); SRVR:BLUPR0601MB1458; BCL:0;
	PCL:0; RULEID:; SRVR:BLUPR0601MB1458; 
X-Forefront-PRVS: 0570F1F193
X-Forefront-Antispam-Report: SFV:NSPM;
	SFS:(10019020)(6049001)(6009001)(33656002)(16799955002)(50466002)(5001960100002)(107886002)(110136002)(36756003)(64126003)(92566002)(54356999)(117156001)(65816999)(50986999)(87266999)(86362001)(122386002)(15975445007)(47776003)(450100001)(65806001)(62966003)(189998001)(65956001)(561944003)(19580395003)(66066001)(229853001)(19580405001)(46102003)(59896002)(40100003)(77096005)(23676002)(77156002)(42186005)(575784001);
	DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR0601MB1458;
	H:[192.168.1.230]; FPR:; SPF:None; MLV:sfv; LANG:en; 
X-OriginatorOrg: bitcoinarmory.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 08 May 2015 19:27:35.0819 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0601MB1458
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
	no trust [157.56.110.102 listed in list.dnswl.org]
	-0.0 SPF_HELO_PASS          SPF: HELO matches SPF record
	-0.0 SPF_PASS               SPF: sender matches SPF record
X-Headers-End: 1YqpO3-0001mS-7N
Subject: [Bitcoin-development] Softfork signaling improvements
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, 08 May 2015 21:00:50 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello. I've seen Greg make a couple of posts online
(https://bitcointalk.org/index.php?topic=1033396.msg11155302#msg11155302
is one such example) where he has mentioned that Pieter has a new
proposal for allowing multiple softforks to be deployed at the same
time. As discussed in the thread I linked, the idea seems simple
enough. Still, I'm curious if the actual proposal has been posted
anywhere. I spent a few minutes searching the usual suspects (this
mailing list, Reddit, Bitcointalk, IRC logs, BIPs) and can't find
anything.

Thanks.

- ---
Douglas Roark
Senior Developer
Armory Technologies, Inc.
doug@bitcoinarmory.com
PGP key ID: 92ADC0D7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJVTQ4eAAoJEGybVGGSrcDX8eMQAOQiDA7an+qZBqDfVIwEzY2C
SxOVxswwxAyTtZNM/Nm+8MTq77hF8+3j/C3bUbDW6wCu4QxBYA/uiCGTf44dj6WX
7aiXg1o9C4LfPcuUngcMI0H5ixOUxnbqUdmpNdoIvy4did2dVs9fAmOPEoSVUm72
6dMLGrtlPN0jcLX6pJd12Dy3laKxd0AP72wi6SivH6i8v8rLb940EuBS3hIkuZG0
vnR5MXMIEd0rkWesr8hn6oTs/k8t4zgts7cgIrA7rU3wJq0qaHBa8uASUxwHKDjD
KmDwaigvOGN6XqitqokCUlqjoxvwpimCjb3Uv5Pkxn8+dwue9F/IggRXUSuifJRn
UEZT2F8fwhiluldz3sRaNtLOpCoKfPC+YYv7kvGySgqagtNJFHoFhbeQM0S3yjRn
Ceh1xK9sOjrxw/my0jwpjJkqlhvQtVG15OsNWDzZ+eWa56kghnSgLkFO+T4G6IxB
EUOcAYjJkLbg5ssjgyhvDOvGqft+2e4MNlB01e1ZQr4whQH4TdRkd66A4WDNB+0g
LBqVhAc2C8L3g046mhZmC33SuOSxxm8shlxZvYLHU2HrnUFg9NkkXi1Ub7agMSck
TTkLbMx17AvOXkKH0v1L20kWoWAp9LfRGdD+qnY8svJkaUuVtgDurpcwEk40WwEZ
caYBw+8bdLpKZwqbA1DL
=ayhE
-----END PGP SIGNATURE-----