I've been trying to find ways to make HD keychain wallets (BIP0032) really
usable from an application development perspective. I think we all know a
number of solid use cases and possible applications for the D in HD, but nobody
seems to have really found a way to make use of the H in a way
You can make the same argument against Bitcoin itself you know...
A Bitmessage-like network would be trivial to front-run via a sybil
attack. It's the fundemental problem with marketplaces - the data
they're trying to publish has to be public.
I don't see the Bitcoin analogy...
This is not bitcoin-philosophy, it's bitcoin-development. Existential
philosophy belongs on IRC or the forums.
On Sat, Mar 1, 2014 at 1:28 PM, Mark Friedenbach m...@monetize.io wrote:
Only if you view bitcoin as no more than a payment network.
On Mar 1, 2014 10:24 AM, Jeff Garzik
Only if you view bitcoin as no more than a payment network.
On Mar 1, 2014 10:24 AM, Jeff Garzik jgar...@bitpay.com wrote:
This is wandering far off-topic for this mailing list.
On Sat, Mar 1, 2014 at 12:45 PM, Troy Benjegerdes ho...@hozed.org wrote:
You can make the same argument against
Another example use-case to back up devrandom's point is using a twitter
handle as the merchant name. In that example, a 3rd party service hosts
and signs the PaymentRequest, but when someone opens that PaymentRequest in
their wallet, they should know that they are paying the specified twitter
From BIP70:
If pki_type is x509+sha256, then the Payment message is hashed using
the
SHA256 algorithm to produce the message digest that is signed. If
pki_type
is x509+sha1, then the SHA1 algorithm is used.
A couple minor comments;
- I think it meant to say the field to be
6 matches
Mail list logo
