From: "MⒶrtin HⒶboⓋštiak" <martin.habovstiak@gmail•com>
To: Natanael <natanael.l@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Standardizing automatic pre-negotiation of transaction terms with BIP70? (Emulating Amazon one-click purchase at all merchants)
Date: Tue, 10 Feb 2015 12:33:13 +0100 [thread overview]
Message-ID: <CALkkCJYDUvtuWGQ5Pq85krGQp=bRYQ1sazg-3T0B8ipr8SGuYA@mail.gmail.com> (raw)
In-Reply-To: <CAAt2M19F2fWj7Ovw_aWvJ5+7osQG6WA=RuT3G+QYiYm-mnNnyg@mail.gmail.com>
2015-02-10 12:19 GMT+01:00 Natanael <natanael.l@gmail•com>:
>
> Den 10 feb 2015 12:08 skrev "Mike Hearn" <mike@plan99•net>:
>>
>> We can certainly imagine many BIP70 extensions, but for things like
>> auto-filling shipping addresses, is the wallet the best place to do it? My
>> browser already knows how to fill out this data in credit card forms, it
>> would make sense to reuse that for Bitcoin.
>>
>> It sounds like you want a kind of Star-Trek negotiation agent thing, where
>> your computer knows how to seek out the best deal because all the metadata
>> is standardised. Such a thing would be an interesting project, but it's
>> probably not best done in BIP70 given how it's deployed and used today.
>> Rather, I'd suggest looking at the various HTML5 data standards which would
>> allow merchants to advertise things like where they ship to in a machine
>> readable and crawlable form.
>
> BIP70 doesn't have to be the place, but not needing to make sure the device
> in question have that information stored already would be an improvement.
> What protocol is used doesn't matter much, I just thought reusing BIP70
> would simplify implementation.
In what universe is that simple? Your solution: browser extension +
wallet + comminucation API + all the wallets need to implement it
Our solution: just browser extension.
If you hate writing browser extensions in Javascript, you can say it
directly. ;)
>
> HTML5 elements could definitely be supported, through adding a tag in the
> HTML form that says "prompt the Bitcoin wallet about the following payment
> details".
Just no.
>
> As one example, your browser could ask your hardware wallet over BLE for
> this data. This way you barely have to trust the computer you're using at
> all, as everything it does is confirmed on the hardware wallet before
> payment (assuming it has a screen, which it should). Linking your hardware
> wallet over BLE to new devices which you then use for browsing and shopping
> could be trivial and yet allow secure auto-fill of this kind.
This looks more interesting but is information about your location
really so secret that you need to hold it in HW wallet? Because if so,
you probably don't want to use untrusted machine anyway. (Or just use
Qubes OS.)
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
next prev parent reply other threads:[~2015-02-10 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAt2M18H0K99bmD4H_FRSeE+O9nGFDruCmo63GOQt1kxAdVBmQ@mail.gmail.com>
2015-02-10 10:21 ` Natanael
2015-02-10 10:34 ` MⒶrtin HⒶboⓋštiak
2015-02-10 10:41 ` Natanael
2015-02-10 10:48 ` MⒶrtin HⒶboⓋštiak
2015-02-10 11:12 ` Natanael
2015-02-10 11:21 ` MⒶrtin HⒶboⓋštiak
2015-02-10 10:50 ` Oleg Andreev
2015-02-10 10:59 ` Eric Voskuil
2015-02-10 11:08 ` Mike Hearn
2015-02-10 11:19 ` Natanael
2015-02-10 11:33 ` MⒶrtin HⒶboⓋštiak [this message]
2015-02-10 11:58 ` Natanael
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='CALkkCJYDUvtuWGQ5Pq85krGQp=bRYQ1sazg-3T0B8ipr8SGuYA@mail.gmail.com' \
--to=martin.habovstiak@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=natanael.l@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