📅 Original date posted:2013-04-27
📝 Original message:On 24 April 2013 16:46, Craig B Agricola <craig at theagricolas.org> wrote:
> Maybe I'm missing something crucial, but what benefit does this dance give
> over
> the slightly more obvious mechanism of simply:
> 1) Alice generates a new address with her bitcoin client and sends the BTC
> to
> this new address
> 2) Alice exports the private key for that address (there is a well
> supported
> format for that)
> 3) Alice writes a nice email to Bob, including that exported private key
> 4) Alice encrypts the email with Bob's public key using GPG and sends it
> to him
> by email
> 5) Bob decrypts the email
> 6) Bob imports the private key into his wallet
>
Yes this works too.
However is it dependent on the bitcoin client address generation algorithm?
I think what I'm trying to describe is something more akin to the way a
shared secret is generated by TLS.
Agree, that the wallet is also shared, ive not yet worked out a way to
'blind' one side of the wallet, but nor have a proved it's impossible, so
still working onthat :)
>
> There's no need for sending a whole wallet; just the one key is needed.
> Every
> bit of infrastructure needed above already exists. And of course, the
> above
> has the same issue as your proposal; this is a way for two trusting
> parties to
> send BTC without using the Bitcoin network, but it's not a payment
> mechanism.
> They now share control of an address; whoever spends that BTC first wins,
> so
> until Bob uses the Bitcoin network to spend that BTC to another address
> that
> only he controls, it's still in joint custody. And if ensuring that he has
> control of the BTC is the last (implicit) step in the procedure above, as
> well
> as yours, then they might as well have simply used the Bitcoin network to
> do
> the transfer in the first place.
>
> Did I miss the point entirely?
>
Perhaps I've not described the problem statement as clearly as I could,
I'll work on it. Essentially it's an automated way to bootstrap the RSA
key community together with bitcoin. e.g. 99% of GPG users probably dont
have a bitcion wallet or address or client. I think maybe a user story
will help.
>
> -Craig
>
> PS. Re-reading, I realize that the above might come off sounding snarky or
> dismissive; it's not intended that way. I'm wondering if I'm missing
> the
> big picture.
>
Not snarky at all! Appreciate the feedback...
>
> On Wed, Apr 24, 2013 at 04:18:38PM +0200, Melvin Carvalho wrote:
> > 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 ...
>
> >
> ------------------------------------------------------------------------------
> > Try New Relic Now & We'll Send You this Cool Shirt
> > New Relic is the only SaaS-based application performance monitoring
> service
> > that delivers powerful full stack analytics. Optimize and monitor your
> > browser, app, & servers with just a few lines of code. Try New Relic
> > and get this awesome Nerd Life shirt!
> http://p.sf.net/sfu/newrelic_d2d_apr
>
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130427/cf515b60/attachment.html>;
Melvin Carvalho [ARCHIVE] /
npub1uv…saxrt
2023-06-07 11:48:41
in reply to nevent1q…m0lc
Author Public Key
npub1uvtfvcegcn9kds68r8he57emc480vqtx8t22kpsctxgjxae44gvsksaxrtPublished at
2023-06-07 11:48:41Event JSON
{
"id": "e028fcd34cee10c07c65a2225f34dafd459d1eddda0a0862f2b00da2911b9efc",
"pubkey": "e316966328c4cb66c34719ef9a7b3bc54ef601663ad4ab06185991237735aa19",
"created_at": 1686138521,
"kind": 1,
"tags": [
[
"e",
"61133492f073aa0db5810138bc3030a9c742c6397a38ebc38dbfe67b0be029fc",
"",
"root"
],
[
"e",
"826287443e3cfa0d5722112644c2a6c8e3ae35d4a123f7eb4dab50bc5076c589",
"",
"reply"
],
[
"p",
"fca9a07b146d5ae03df0e92345c0aabee670e5ffbaa52a6151686ea8eb2c7b71"
]
],
"content": "📅 Original date posted:2013-04-27\n📝 Original message:On 24 April 2013 16:46, Craig B Agricola \u003ccraig at theagricolas.org\u003e wrote:\n\n\u003e Maybe I'm missing something crucial, but what benefit does this dance give\n\u003e over\n\u003e the slightly more obvious mechanism of simply:\n\u003e 1) Alice generates a new address with her bitcoin client and sends the BTC\n\u003e to\n\u003e this new address\n\u003e 2) Alice exports the private key for that address (there is a well\n\u003e supported\n\u003e format for that)\n\u003e 3) Alice writes a nice email to Bob, including that exported private key\n\u003e 4) Alice encrypts the email with Bob's public key using GPG and sends it\n\u003e to him\n\u003e by email\n\u003e 5) Bob decrypts the email\n\u003e 6) Bob imports the private key into his wallet\n\u003e\n\nYes this works too.\n\nHowever is it dependent on the bitcoin client address generation algorithm?\n\nI think what I'm trying to describe is something more akin to the way a\nshared secret is generated by TLS.\n\nAgree, that the wallet is also shared, ive not yet worked out a way to\n'blind' one side of the wallet, but nor have a proved it's impossible, so\nstill working onthat :)\n\n\n\u003e\n\u003e There's no need for sending a whole wallet; just the one key is needed.\n\u003e Every\n\u003e bit of infrastructure needed above already exists. And of course, the\n\u003e above\n\u003e has the same issue as your proposal; this is a way for two trusting\n\u003e parties to\n\u003e send BTC without using the Bitcoin network, but it's not a payment\n\u003e mechanism.\n\u003e They now share control of an address; whoever spends that BTC first wins,\n\u003e so\n\u003e until Bob uses the Bitcoin network to spend that BTC to another address\n\u003e that\n\u003e only he controls, it's still in joint custody. And if ensuring that he has\n\u003e control of the BTC is the last (implicit) step in the procedure above, as\n\u003e well\n\u003e as yours, then they might as well have simply used the Bitcoin network to\n\u003e do\n\u003e the transfer in the first place.\n\u003e\n\u003e Did I miss the point entirely?\n\u003e\n\nPerhaps I've not described the problem statement as clearly as I could,\nI'll work on it. Essentially it's an automated way to bootstrap the RSA\nkey community together with bitcoin. e.g. 99% of GPG users probably dont\nhave a bitcion wallet or address or client. I think maybe a user story\nwill help.\n\n\n\u003e\n\u003e -Craig\n\u003e\n\u003e PS. Re-reading, I realize that the above might come off sounding snarky or\n\u003e dismissive; it's not intended that way. I'm wondering if I'm missing\n\u003e the\n\u003e big picture.\n\u003e\n\nNot snarky at all! Appreciate the feedback...\n\n\n\u003e\n\u003e On Wed, Apr 24, 2013 at 04:18:38PM +0200, Melvin Carvalho wrote:\n\u003e \u003e So there's a slight world divide in digital payments with bitcoin using\n\u003e \u003e ECDSA and GPG, payswarm / webid etc using largely RSA\n\u003e \u003e\n\u003e \u003e Here's how to bring the two worlds together and enable bitcoins be sent\n\u003e \u003e over webid or payswarm\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e Problem: Alice and Bob have RSA key pairs, but no public bitcoin\n\u003e \u003e addresses. Alice wants to send 1 BTC to Bob.\n\u003e \u003e\n\u003e \u003e 1. Alice takes Bob's WebID and encrpyts it with her private key (to\n\u003e create\n\u003e \u003e entropy) ...\n\u003e \u003e\n\u003e \u003e 2. Alice uses that message as the seed to produce btc address (as per\n\u003e \u003e http://brainwallet.org ) with ECDSA key pair\n\u003e \u003e\n\u003e \u003e 3. Alice sends coins to this address\n\u003e \u003e\n\u003e \u003e 4. Alice and then encrypts the seed again with Bob's public key\n\u003e \u003e\n\u003e \u003e 5. Bob decrypts the seed using his private key\n\u003e \u003e\n\u003e \u003e 6. Bob can now use the seed to recreate the wallet and spend the coins\n\u003e \u003e\n\u003e \u003e Unless I've made an error, I believe this unites the web paradigm and\n\u003e \u003e crypto currency paradigm into one potentially giant eco system ...\n\u003e\n\u003e \u003e\n\u003e ------------------------------------------------------------------------------\n\u003e \u003e Try New Relic Now \u0026 We'll Send You this Cool Shirt\n\u003e \u003e New Relic is the only SaaS-based application performance monitoring\n\u003e service\n\u003e \u003e that delivers powerful full stack analytics. Optimize and monitor your\n\u003e \u003e browser, app, \u0026 servers with just a few lines of code. Try New Relic\n\u003e \u003e and get this awesome Nerd Life shirt!\n\u003e http://p.sf.net/sfu/newrelic_d2d_apr\n\u003e\n\u003e \u003e _______________________________________________\n\u003e \u003e Bitcoin-development mailing list\n\u003e \u003e Bitcoin-development at lists.sourceforge.net\n\u003e \u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130427/cf515b60/attachment.html\u003e",
"sig": "ab66bf37391ef90507f56aa84d9e93f0d054526596d193b14f15f7fcde336caf66d9807616ce46bf97977d5f6e34f9203403a2f169574f51362e169d4dfca583"
}