From: Aaron Voisine <voisine@gmail.com>
To: Dan Bryant <DKBryant@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] REQ BIP # / Discuss - Sweep incoming unconfirmed transactions with a bounty.
Date: Wed, 26 Aug 2015 16:28:45 +0100 [thread overview]
Message-ID: <CACq0ZD4Audh5ROuxv6=KJ5XjH7TXkfQRHeNFvgoBGc8bVb6yjg@mail.gmail.com> (raw)
In-Reply-To: <CAAUFj13BywG8jB=bXDSx15Zdj4QS8ebfd7bTvUxtxC1yL_rFSQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
Breadwallet also implements CPFP when spending unconfirmed non-change
inputs. It was released back in May, but happy to let Andreas have the
bounty:
https://github.com/voisine/breadwallet/blob/v0.5.1/BreadWallet/BRWallet.m#L382
Aaron Voisine
co-founder and CEO
breadwallet.com
On Wed, Jul 15, 2015 at 9:26 AM, Dan Bryant via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Offering a bounty for this feature
>
> Specifically...
>
> Anyone who can put a CPFP transaction creation feature into any wallet
> featured on the bitcoin homepage (ref1) can claim this bounty. The
> funds are being raised by donation. The funds will be dispersed from
> the following address when the bounty is claimed:
> 3FEUByMeaxrNmBCVYjvsnhyAjiUdat5i7M
>
> Currently there isn't much in there, but I welcome angels to fill the
> bucket.
>
> Here's proof that the multisig address is not 1 of 1:
> https://bitcointalk.org/index.php?topic=1122956.0
>
> Bounty announce: https://bitcointalk.org/index.php?topic=1123464.0
>
> ref1: https://bitcoin.org/en/choose-your-wallet
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 2459 bytes --]
prev parent reply other threads:[~2015-08-26 15:28 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
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 [this message]
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='CACq0ZD4Audh5ROuxv6=KJ5XjH7TXkfQRHeNFvgoBGc8bVb6yjg@mail.gmail.com' \
--to=voisine@gmail.com \
--cc=DKBryant@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.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