summaryrefslogtreecommitdiff
path: root/83/0082d782c9c819374cb64983cf1169ae026300
blob: da7f0cd752a85f6aa756c396e9271abe7b182d5e (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
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 3502EEA1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 13 Dec 2015 08:18:58 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f177.google.com (mail-ig0-f177.google.com
	[209.85.213.177])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A05D9EC
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 13 Dec 2015 08:18:57 +0000 (UTC)
Received: by igbxm8 with SMTP id xm8so65220499igb.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 13 Dec 2015 00:18:57 -0800 (PST)
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-type;
	bh=cby4Xrs7kSkxI0aKyn36YY1Y0U9pzebWcmtIzTUz3hs=;
	b=jJB9MZ94iSUvPHVnsXfazVdtzH1BSS/wCiugiYUJSR6nQ+PlfSI6dETiALTMXPq9tK
	sbnPFRO0IwJqnN69G6PQ4ldntTME8jjO0NaQNVjAbs1xZSpSarz1KoSEQ3mxcx5NFIv0
	z3/pRQ5YKbFUHgf5QfnBjAm2Dr9uB0jMVNZKRmskO47cl6zC/g0eAskmFtCJK52vurL/
	+E5d655Ze7lBKa8nNm8qqAbyjlwP+nWs2lHBuWVCkhJk7w05cK5yDzWFnLcsqx5vW6l5
	adDxuSi/PY7vwNve+tPQSLdZRLynqmNQDoCmDJOFtQf6FIFxBnPRT7YwZCK+S1qPhKnv
	aUTA==
MIME-Version: 1.0
X-Received: by 10.50.61.204 with SMTP id s12mr386198igr.66.1449994737140; Sun,
	13 Dec 2015 00:18:57 -0800 (PST)
Sender: gmaxwell@gmail.com
Received: by 10.107.192.70 with HTTP; Sun, 13 Dec 2015 00:18:57 -0800 (PST)
In-Reply-To: <CAAcC9yuSX67ckhBUCsvTk+7PB6vzufuuBsJikSqqqU_4LXoCfA@mail.gmail.com>
References: <50e629572d8de852eb789d50b34da308@xbt.hk>
	<1449961269.2210.5.camel@yahoo.com>
	<CACrzPenXGQZBrx8QC+1QE2oCE3N=qmfgc_OWrowtjtLjGkZrRA@mail.gmail.com>
	<CAAS2fgQi7aiwyOaVBiMbp6t9D58aFAmDdKPzFiscB6ouGzBK6A@mail.gmail.com>
	<CAAcC9yuSX67ckhBUCsvTk+7PB6vzufuuBsJikSqqqU_4LXoCfA@mail.gmail.com>
Date: Sun, 13 Dec 2015 08:18:57 +0000
X-Google-Sender-Auth: wHio7uVD-QqS4KlJzb70vY4S4pI
Message-ID: <CAAS2fgSchJFk1Ejd8ZfMSzxEO-1TWYR6ag-seQNH_QHrc9Cn3w@mail.gmail.com>
From: Gregory Maxwell <greg@xiph.org>
To: Chris Priest <cp368202@ohiou.edu>
Content-Type: text/plain; charset=UTF-8
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 Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Forget dormant UTXOs without confiscating bitcoin
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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: Sun, 13 Dec 2015 08:18:58 -0000

On Sun, Dec 13, 2015 at 8:13 AM, Chris Priest <cp368202@ohiou.edu> wrote:
> Lets say it's 2050 and I want to sweep a paper wallet I created in
> 2013. I can't just make the TX and send it to the network, I have to
> first contact an "archive node" to get the UTXO data in order to make
> the TX. How is this better than how the system works today?

You already are in that boat. If your paper wallet has only the
private key (as 100% of them do today). You'll have no idea what coins
have been assigned to it, or what their TXids are. You'll need to
contact a public index (which isn't a service existing nodes provide)
or synchronize the full blockchain history to find it. Both are also
sufficient for jl2012's (/Petertodd's STXO), they'd only be providing
you with somewhat more data.  If instead, you insist that you'd
already be running a full node and not have to wait for the sync, then
again you'd also be your own archive. In none of these cases do you
lose anything.