summaryrefslogtreecommitdiff
path: root/f5/ef0ac3affc3b79837dc65e5ed6db99b192caf2
blob: 7e76e0503a1b1e034075665e1768d1712854563b (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
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gmaxwell@gmail.com>) id 1WXLS5-0003nA-Kr
	for bitcoin-development@lists.sourceforge.net;
	Tue, 08 Apr 2014 02:07:53 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.217.174 as permitted sender)
	client-ip=209.85.217.174; envelope-from=gmaxwell@gmail.com;
	helo=mail-lb0-f174.google.com; 
Received: from mail-lb0-f174.google.com ([209.85.217.174])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WXLS4-0001uR-OY
	for bitcoin-development@lists.sourceforge.net;
	Tue, 08 Apr 2014 02:07:53 +0000
Received: by mail-lb0-f174.google.com with SMTP id u14so243814lbd.33
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 07 Apr 2014 19:07:46 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.137.5 with SMTP id qe5mr595004lbb.16.1396922866153; Mon,
	07 Apr 2014 19:07:46 -0700 (PDT)
Received: by 10.112.89.68 with HTTP; Mon, 7 Apr 2014 19:07:45 -0700 (PDT)
In-Reply-To: <6669921.kYEqrMqt0u@crushinator>
References: <CAC7yFxSE8-TWPN-kuFiqdPKMDuprbiVJi7-z-ym+AUyA_f-xJw@mail.gmail.com>
	<CAC7yFxRndCS=aEWcvmrFTf-WZg9Ht+pZmLZ-4sdBpdv+vJQoRQ@mail.gmail.com>
	<CAAS2fgT22HdS=MQU4B1vWUUKDk+pJiLGmGnBF9E9Zcs_swTN3g@mail.gmail.com>
	<6669921.kYEqrMqt0u@crushinator>
Date: Mon, 7 Apr 2014 19:07:45 -0700
Message-ID: <CAAS2fgSfiYwD-M7+k65JF0Kjeod1zEiPcxPN1iDBHLzYV7UQyA@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Matt Whitlock <bip@mattwhitlock.name>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: 1.1 (+)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(gmaxwell[at]gmail.com)
	1.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
	[Blocked - see <http://www.spamcop.net/bl.shtml?209.85.217.174>]
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
	1.5 SF_NO_SPF_SPAM         SF_NO_SPF_SPAM
X-Headers-End: 1WXLS4-0001uR-OY
Cc: bitcoin-development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Presenting a BIP for Shamir's Secret
 Sharing of Bitcoin private keys
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: Tue, 08 Apr 2014 02:07:53 -0000

On Mon, Apr 7, 2014 at 6:46 PM, Matt Whitlock <bip@mattwhitlock.name> wrote:
> On Monday, 7 April 2014, at 5:38 pm, Gregory Maxwell wrote:
>> On Mon, Apr 7, 2014 at 5:33 PM, Nikita Schmidt
>> <nikita@megiontechnologies.com> wrote:
>> > Regarding the choice of fields, any implementation of this BIP will
>> > need big integer arithmetic to do base-58 anyway.
>> Nah, it doesn't. E.g.
>> https://gitorious.org/bitcoin/libblkmaker/source/eb33f9c8e441ffef457a79d76ceed1ea20ab3059:base58.c
> That only *decodes* Base58Check. It has no encode function, which would require biginteger division.

Yes thats only a decode but the same process (long division with
manual carries) works just fine the other way. There is absolutely no
need to use big integers for this.