From: Kristov Atlas <author@anonymousbitcoinbook.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] CoinJoin bounty fund question
Date: Tue, 17 Jun 2014 19:14:58 -0400 [thread overview]
Message-ID: <53A0CBF2.1050305@anonymousbitcoinbook.com> (raw)
In-Reply-To: <CAAS2fgSQB21gQHLZq9UdRYiRoiYqsB88yF8ViE2P8jK6ShrqLg@mail.gmail.com>
On 06/17/2014 06:46 PM, Gregory Maxwell wrote:
> The correct place for more information is the Bitcointalk forum thread
> where it was announced:
> https://bitcointalk.org/index.php?topic=279249.0
Can anyone summarize the current status of the bounty? I see nothing
definite about the bounty in that thread from the beginning of January
2014, other than that the multisig address continues to accumulate
bitcoins. Meanwhile, on other mailing lists, I've seen some talk about
paying a portion or the whole of the bounty to the Dark Wallet team.
-Kristov
prev parent reply other threads:[~2014-06-17 23:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 21:14 [Bitcoin-development] CoinJoin bounty fund question Odinn Cyberguerrilla
2014-06-17 22:46 ` Gregory Maxwell
2014-06-17 23:14 ` Kristov Atlas [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=53A0CBF2.1050305@anonymousbitcoinbook.com \
--to=author@anonymousbitcoinbook.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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