public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: public-rww <public-rww@w3.org>,
	Web Payments <public-webpayments@w3.org>,
	 Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Sending Bitcoins using RSA keys
Date: Wed, 24 Apr 2013 16:18:38 +0200	[thread overview]
Message-ID: <CAKaEYhLNS-9MLVr1AWB0mWUMoADvd03-7KMQp77ZGCfcu8E1Qg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 901 bytes --]

So there's a slight world divide in digital payments with bitcoin using
ECDSA and GPG, payswarm / webid etc using largely RSA

Here's how to bring the two worlds together and enable bitcoins be sent
over webid or payswarm


Problem: Alice and Bob have RSA key pairs, but no public bitcoin
addresses.  Alice wants to send 1 BTC to Bob.

1. Alice takes Bob's WebID and encrpyts it with her private key (to create
entropy) ...

2. Alice uses that message as the seed to produce btc address (as per
http://brainwallet.org ) with ECDSA key pair

3. Alice sends coins to this address

4. Alice and then encrypts the seed again with Bob's public key

5. Bob decrypts the seed using his private key

6. Bob can now use the seed to recreate the wallet and spend the coins

Unless I've made an error, I believe this unites the web paradigm and
crypto currency paradigm into one potentially giant eco system ...

[-- Attachment #2: Type: text/html, Size: 1140 bytes --]

             reply	other threads:[~2013-04-24 14:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 14:18 Melvin Carvalho [this message]
2013-04-24 14:46 ` [Bitcoin-development] Sending Bitcoins using RSA keys Craig B Agricola
2013-04-27 14:14   ` Melvin Carvalho

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=CAKaEYhLNS-9MLVr1AWB0mWUMoADvd03-7KMQp77ZGCfcu8E1Qg@mail.gmail.com \
    --to=melvincarvalho@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=public-rww@w3.org \
    --cc=public-webpayments@w3.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