On 12/16/2013 07:28 PM, Mike Hearn wrote:
> I don't know how to solve this. Badly designed software that looks
> appealing will always be a danger.
One way would be to explicitly warn against some services. For example,
on the "Choose you wallet" page of bitcoin.org.
-
On Mon, Dec 16, 2013 at 3:37 AM, Wladimir wrote:
> What we should really do is:
> - Use deterministic wallets. Making regular backups becomes optional (to
> retain label and transaction data and such) instead of mandatory.
> - Don't support importing private keys. Replace the importing of private
On Mon, Dec 16, 2013 at 11:13 AM, Drak wrote:
> It just occurs to me this kind of sad story could be averted if wallets
> implemented a confirmation box if the fee amount seems crazy - for example,
> if it's >10x what the default fee should be, or if it's greater than x% of
> the sending amount.
On Mon, Dec 16, 2013 at 12:31 PM, Pieter Wuille wrote:
> Will that also mean no longer reusing (change) addresses?
>
Jim seems to be planning some parallel development to what I'm doing, but
HD wallets and stopping address re-use is the current feature I'm working
on for bitcoinj. Only code revie
Providing people with a great user experience is something that Hive Wallet is
enthusiastic about, so this is stuff we’re thinking about constantly. For
example, how do you alert the user to abnormal activity (i.e. sending “too
much” on accident[1])? The removal of extraneous UI and functionalit
On Mon, Dec 16, 2013 at 11:46 AM, Jim wrote:
> For the HD version of MultiBit we are removing the import
> of individual private keys entirely and only supporting HD
> addresses, primarily for safety reasons.
>
I'd love to have the same in Bitcoin-Qt as well. Too many sob stories about
people wi
On Mon, Dec 16, 2013 at 11:46 AM, Jim wrote:
> For the HD version of MultiBit we are removing the import
> of individual private keys entirely and only supporting HD
> addresses, primarily for safety reasons.
Will that also mean no longer reusing (change) addresses?
--
Pieter
-
On Mon, Dec 16, 2013 at 11:13 AM, Drak wrote:
> It just occurs to me this kind of sad story could be averted if wallets
> implemented a confirmation box if the fee amount seems crazy - for example,
> if it's >10x what the default fee should be, or if it's greater than x% of
> the sending amount.
Jim,
It's great to see the many ways wallet authors try to protect users from
easy to make mistakes, especially against losing funds.
But this issues isn't confined to custom transaction - some wallet
implementations have a fee field and almost all wallets allow the fee rate
to be configured in p
Yes I saw that on reddit too.
I think it applies mainly to custom transactions rather
than where fees are calculated automatically.
Another variant of not understanding change that loses
people's bitcoins I have encountered is:
1) Import a private key of a brainwallet/ paper wallet.
2) Send a sma
Not sure if this is the right place, but since a few wallet authors
congregate here I though it might be the best place.
It seems every once in a while you see stories of people accidentally
paying huge fees. Today I read about a man who paid a 20.14BTC fee for a
0.05 BTC transaction[1], oops. The
11 matches
Mail list logo
