From: Mike Hearn <mike@plan99•net>
To: Jeremy Spilman <jeremy@taplink•co>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Stealth Payments - Sample Code / Proof of Concept
Date: Mon, 13 Jan 2014 12:18:28 +0100 [thread overview]
Message-ID: <CANEZrP38DsYP4KRk1Jz_hiMrP_ZPCj6=TDKmr-t-r2BJRMjDSQ@mail.gmail.com> (raw)
In-Reply-To: <op.w9mb5dv0yldrnw@laptop-air.hsd1.ca.comcast.net>
[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]
Cool!
On Mon, Jan 13, 2014 at 10:18 AM, Jeremy Spilman <jeremy@taplink•co> wrote:
> I spent 1BTC on TestNet to a stealth address...
> TxID: df092896c1347b303da299bc84c92bef1946f455dbdc80ffdb01a18ea4ed8b4c
>
... but can you redeem it?
> Code which generated this transaction is here:
> https://gist.github.com/jspilman/8396495
That's rather interesting code. Is this using a private C# bitcoin
implementation?
> I wonder if the 0BTC OP_RETURN transactions should be hidden from the
> Transaction List?
>
Yes, of course. The transaction list should just say something like
"Payment received from Jeremy, 0.1 BTC"
Maybe the simple way to punt on this is to just show 'Merchant' in the
> address column if it is available and an address is not.
I am surprised it's not already the case! Though "merchant" is perhaps a
bit biased as a name, internally it perhaps should just be called
"Recipient". There's no requirement for you to be a merchant to create
payment protocol requests.
> I can probably make the necessary changes to IsMine, but I don't know
> where we should keep 'd2'/'Q2' unencrypted so it's available for doing the
> necessary tests, but has no chance of ever be used as a stand-alone
> private key?
>
The wallet format would need extending.
I'd feel a lot more comfortable if the protocol was reviewed by a
professional cryptographer though. I think think Gregory already brought up
an issue to do with people able to detect such payments by testing if
decrypted values are points on the curve, or something like that.
[-- Attachment #2: Type: text/html, Size: 2711 bytes --]
next prev parent reply other threads:[~2014-01-13 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 9:18 Jeremy Spilman
2014-01-13 11:18 ` Mike Hearn [this message]
2014-01-13 14:10 ` Jeremy Spilman
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='CANEZrP38DsYP4KRk1Jz_hiMrP_ZPCj6=TDKmr-t-r2BJRMjDSQ@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jeremy@taplink$(echo .)co \
/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