From: Mike Hearn <mike@plan99•net>
To: Kristov Atlas <kristovatlas.lists@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] bitcoinj 0.12
Date: Sat, 4 Oct 2014 15:26:39 +0200 [thread overview]
Message-ID: <CANEZrP3p3CKV-PeXsN6AtDc1=65SCnhQdhvZOd-iA7ZG_3HLnA@mail.gmail.com> (raw)
In-Reply-To: <CAGH37SJ_vdpM6iWbegggRULVKkg7GV=yNQafWv-hyC4MbfccvA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
Hey Kristov,
> I hate to reply to a release that includes a huge number of new features
> with yet another feature request, so -- with apologies -- any plans for
> bitcoinj to support stealth address sending and/or receiving?
>
Stealth addresses and SPV don't mix well, so no. I wrote up a description
of how to do something similar with the payment protocol here:
https://medium.com/@octskyward/ecdh-in-the-payment-protocol-cb2f81962c1b
Because you can send data around outside the block chain on private
channels, with the pp the same issues don't crop up.
At the moment there are no concrete plans what goes into the next release.
I will be focusing on fully launching Lighthouse and crowdfunding for
decentralisation/crypto related projects, so I won't be doing any major
feature work on bitcoinj. Luckily it's become quite an active project now
and there are lots of contributors, so things won't stand still.
If I were to tackle a big project the next one would not be privacy
related. It'd be refactoring the wallet so it doesn't store transactions
directly anymore, just unspent outputs. Bitcoinj has always been largely
driven by the needs of Andreas' mobile app, and right now the top user
reported problem there is people hitting the scalability limits of the
current design (e.g. they are mining directly into their phone's wallet).
[-- Attachment #2: Type: text/html, Size: 1865 bytes --]
prev parent reply other threads:[~2014-10-04 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 12:49 Mike Hearn
2014-10-03 13:02 ` Pavol Rusnak
2014-10-03 13:25 ` Wladimir
2014-10-03 23:29 ` Tom Harding
2014-10-04 6:44 ` Kristov Atlas
2014-10-04 13:26 ` Mike Hearn [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='CANEZrP3p3CKV-PeXsN6AtDc1=65SCnhQdhvZOd-iA7ZG_3HLnA@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=kristovatlas.lists@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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