summaryrefslogtreecommitdiff
path: root/aa/e411330996fd3791d7ae1b041728f3dd4e1ea7
blob: 6172e113973fa1dddd0e71591f50bdda5d2bd908 (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
Return-Path: <bip@mattwhitlock.name>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 0A8CC982
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu,  2 Jul 2015 05:05:36 +0000 (UTC)
X-Greylist: delayed 00:08:11 by SQLgrey-1.7.6
Received: from resqmta-ch2-12v.sys.comcast.net
	(resqmta-ch2-12v.sys.comcast.net [69.252.207.44])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 7D2EAF4
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu,  2 Jul 2015 05:05:35 +0000 (UTC)
Received: from resomta-ch2-15v.sys.comcast.net ([69.252.207.111])
	by resqmta-ch2-12v.sys.comcast.net with comcast
	id nGxQ1q0022Qkjl901GxQ15; Thu, 02 Jul 2015 04:57:24 +0000
Received: from crushinator.localnet
	([IPv6:2601:186:c000:825e:e9f4:8901:87c7:24a0])
	by resomta-ch2-15v.sys.comcast.net with comcast
	id nGxM1q00D4eLRLv01GxNzb; Thu, 02 Jul 2015 04:57:23 +0000
From: Matt Whitlock <bip@mattwhitlock.name>
To: Mark Friedenbach <mark@friedenbach.org>
Date: Thu, 02 Jul 2015 00:57:21 -0400
Message-ID: <1854821.ToCRAf8eXU@crushinator>
User-Agent: KMail/4.14.9 (Linux/4.0.5-gentoo; KDE/4.14.9; x86_64; ; )
In-Reply-To: <CAOG=w-swH-_cD00Xy5yCN7LebeQSh-oG0gXFM6LxNSDwQZ64Tw@mail.gmail.com>
References: <CAAUFj10D37A1kfqFNPWz6bOMYSFXQbecJ+RxxOnw6HtwUg70mg@mail.gmail.com>
	<CAOG=w-swH-_cD00Xy5yCN7LebeQSh-oG0gXFM6LxNSDwQZ64Tw@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net;
	s=q20140121; t=1435813044;
	bh=KylRoUyWJN5i79BvbPTKsxGM98vafZ3LroSGRWiyJeY=;
	h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version:
	Content-Type;
	b=JGdOi+XTOBvBoUr19E/buDREEoukaZo95a21OwaeFOZpL3soN+vE5UgAGlYlR71Qn
	C9GFDzBxvSHWM2p1qBdWI+bUKjZznz37P6nd7zHjxmMcRECppBRXMoA6nvmTH+t1B7
	Q1pX/rh7tlxRMPef5GkK8XafKTZ5aizOhsjNOrn+gwoNNTYLfUam9p9B+NJAT6tFbY
	G5X1Fl9LrovEkfhNSwyiDx5xFiaK3oWUCnurF5EfktkfBlCTl7LH6zlA/Pyed1JpGh
	fAdjA/4ImJcf+i/ODHAdoSLkl1dRwQ/LCeuXMP6cv2p9ts46w2hYWzsp+2ixJ44PWU
	ouILir2w1Qq8g==
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,RCVD_IN_DNSWL_NONE 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@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] REQ BIP # / Discuss - Sweep incoming unconfirmed
	transactions with a bounty.
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: Thu, 02 Jul 2015 05:05:36 -0000

PR#1647 only addresses miner policy, though, right? I believe the BIP is addressing the user-facing side of this functionality. CPFP mining policy does very little good if wallets don't offer any way for users to goose up incoming transactions.


On Wednesday, 1 July 2015, at 9:52 pm, Mark Friedenbach wrote:
> This is called child pays for parent and there is a three year old pull
> request implementing it:
> 
> https://github.com/bitcoin/bitcoin/pull/1647
> 
> The points regarding sweep transaction UI is out of scope for a BIP I'm
> afraid. I suggest talking with wallet authors, and if agreement can be
> found writing a pull request.
> On Jul 1, 2015 9:44 PM, "Dan Bryant" <dkbryant@gmail.com> wrote:
> 
> > This is a process BIP request to add functionality to the Bitcoin-Core
> > reference implementation.  If accepted, this could also add
> > flexibility into any future fee schedules.
> >
> > https://github.com/d4n13/bips/blob/master/bip-00nn.mediawiki