From: Matt Whitlock <bip@mattwhitlock.name>
To: Mark Friedenbach <mark@friedenbach.org>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] REQ BIP # / Discuss - Sweep incoming unconfirmed transactions with a bounty.
Date: Thu, 02 Jul 2015 00:57:21 -0400 [thread overview]
Message-ID: <1854821.ToCRAf8eXU@crushinator> (raw)
In-Reply-To: <CAOG=w-swH-_cD00Xy5yCN7LebeQSh-oG0gXFM6LxNSDwQZ64Tw@mail.gmail.com>
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
next prev parent reply other threads:[~2015-07-02 5:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 4:44 [bitcoin-dev] REQ BIP # / Discuss - Sweep incoming unconfirmed transactions with a bounty Dan Bryant
2015-07-02 4:52 ` Mark Friedenbach
2015-07-02 4:57 ` Matt Whitlock [this message]
2015-07-02 13:13 ` Tier Nolan
2015-07-03 21:56 ` Peter Todd
2015-07-06 4:14 ` Dan Bryant
2015-07-06 4:20 ` Micha Bailey
2015-07-06 4:24 ` Luke Dashjr
2015-07-09 6:17 ` Aaron Voisine
2015-07-09 6:22 ` Luke Dashjr
2015-07-09 7:19 ` Dan Bryant
2015-07-15 8:26 ` Dan Bryant
2015-08-26 15:28 ` Aaron Voisine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1854821.ToCRAf8eXU@crushinator \
--to=bip@mattwhitlock.name \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=mark@friedenbach.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox