From: Mike Hearn <mike@plan99•net>
To: Matias Alejo Garcia <matias@bitpay•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP32 Index Randomisation
Date: Fri, 13 Mar 2015 14:34:31 -0700 [thread overview]
Message-ID: <CANEZrP2E5p+oK1WHC=ZdvqFCo7Cwqrf0NXUCKJ9TPn3wdLBY-Q@mail.gmail.com> (raw)
In-Reply-To: <CA+vKqYeafvwJkwWfiMTZDhO_7nxbdLFRppptZRbRoeBJP8O9qg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
>
> You are killing us Mike! :) We really don't like to think that BWS is
> a webwallet. Note
> that private keys are not stored (not even encrypted) at the server.
Sure, sorry, by web wallet I meant a blockchain.info/CoPay type setup where
the client has the private keys and signs txns, but otherwise relies on the
server for learning about the wallet contents. I tend to call wallets where
the server has the private key BitBanks but I don't know if anyone else
uses this terminology. It might just be a personal quirk of my own ;)
> we think having some visibility of the wallet by the multisig
> facilitator will make the user experience much better (e.g: mobile
> notifications).
>
Fair enough. Yes, push notifications to mobiles in a decentralised way is
rather a hard problem.
I think what Gregory suggested is then the best approach for you to do what
you want. Whether it's worth the additional complexity is something I don't
have any feedback on, only you can judge that.
[-- Attachment #2: Type: text/html, Size: 1457 bytes --]
prev parent reply other threads:[~2015-03-13 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 3:48 Matias Alejo Garcia
2015-03-13 4:01 ` Gregory Maxwell
2015-03-13 16:40 ` Mike Hearn
2015-03-13 18:01 ` Matias Alejo Garcia
2015-03-13 18:04 ` Mike Hearn
2015-03-13 20:26 ` Matias Alejo Garcia
2015-03-13 21:34 ` Mike Hearn [this message]
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='CANEZrP2E5p+oK1WHC=ZdvqFCo7Cwqrf0NXUCKJ9TPn3wdLBY-Q@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=matias@bitpay$(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