summaryrefslogtreecommitdiff
path: root/99/450a11c1be83fad7713f267314d27ceeb75d09
blob: f8b4279bae1825ffec056d07dfc3acef8a30bf47 (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
115
116
117
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <moon@justmoon.de>) id 1R9F6Z-0005Bz-0L
	for bitcoin-development@lists.sourceforge.net;
	Thu, 29 Sep 2011 11:48:43 +0000
X-ACL-Warn: 
Received: from sulfur.webpack.hosteurope.de ([217.115.142.104])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1R9F6U-0001nq-LW for bitcoin-development@lists.sourceforge.net;
	Thu, 29 Sep 2011 11:48:42 +0000
Received: from 84-72-69-153.dclient.hispeed.ch ([84.72.69.153]
	helo=[192.168.0.21]); authenticated
	by sulfur.webpack.hosteurope.de running ExIM with esmtpsa
	(TLSv1:AES256-SHA:256)
	id 1R9F6O-0000NB-Id; Thu, 29 Sep 2011 13:48:32 +0200
Message-ID: <4E845B09.8040400@justmoon.de>
Date: Thu, 29 Sep 2011 13:48:25 +0200
From: Stefan Thomas <moon@justmoon.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:7.0) Gecko/20110922 Thunderbird/7.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <4E80D591.2080100@nilsschneider.net>
	<CAJNQ0stW-7HMw-O_C9Go8ViRrxBNtEpsbhSRyc3aOzm6OvR6dA@mail.gmail.com>
	<4E845935.8060601@nilsschneider.net>
In-Reply-To: <4E845935.8060601@nilsschneider.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-bounce-key: webpack.hosteurope.de;moon@justmoon.de;1317296918;40defa93;
X-Spam-Score: 0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	0.5 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1R9F6U-0001nq-LW
Subject: Re: [Bitcoin-development] Deprecating "midstate" in getwork?
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: Thu, 29 Sep 2011 11:48:43 -0000

BitcoinJS uses OpenSSL to calculate midstate:

https://github.com/bitcoinjs/node-bitcoin-p2p/blob/master/native.cc#L380


On 9/29/2011 1:40 PM, Nils Schneider wrote:
> Yes, that's possible and what
> https://github.com/bitcoin/bitcoin/pull/535 does. However, deprecating
> midstate (and hash1) would allow for much cleaner code.
>
> A pull request for marking midstate (and hash1) as deprecated can be
> found at https://github.com/bitcoin/bitcoin/pull/538
>
> On 29.09.2011 12:23, John Smith wrote:
>> Nils,
>>
>> Sounds good. I'm also doubtful of depending on two crypto libraries when
>> OpenSSL does perfectly well.
>>
>> However, losing compatibility with miners is not very nice. Is there
>> really not a way to compute midstate with OpenSSL?
>>
>> JS
>>
>> On Mon, Sep 26, 2011 at 7:42 PM, Nils Schneider<nils@nilsschneider.net
>> <mailto:nils@nilsschneider.net>>  wrote:
>>
>>      Hey,
>>
>>      I'd like to simplify the internal reference miner and remove all
>>      dependencies on cryptopp (it's the only place we use cryptopp instead of
>>      OpenSSL).
>>
>>      Unfortunately, cryptopp is also used to calculate getwork "midstate".
>>      This field is redundant and the miner could easily calculate it from the
>>      blockheader so I'd like to remove it.
>>
>>      Any thoughts? Where should such a change should be announced so all
>>      miners can be upgraded?
>>
>>      ------------------------------------------------------------------------------
>>      All the data continuously generated in your IT infrastructure contains a
>>      definitive record of customers, application performance, security
>>      threats, fraudulent activity and more. Splunk takes this data and makes
>>      sense of it. Business sense. IT sense. Common sense.
>>      http://p.sf.net/sfu/splunk-d2dcopy1
>>      _______________________________________________
>>      Bitcoin-development mailing list
>>      Bitcoin-development@lists.sourceforge.net
>>      <mailto:Bitcoin-development@lists.sourceforge.net>
>>      https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>