{"type":"rich","version":"1.0","author_name":"npub1a9uelw8hswrmps0ayl2dzkh625xjznd5glvqrkhpxngdzupjw8kqqlc2j9","author_url":"https://nostr.ae/npub1a9uelw8hswrmps0ayl2dzkh625xjznd5glvqrkhpxngdzupjw8kqqlc2j9","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2013-12-16\n📝 Original message:Yes I saw that on reddit too.\n\nI think it applies mainly to custom transactions rather\nthan where fees are calculated automatically.\n\nAnother variant of not understanding change that loses\npeople's bitcoins I have encountered is:\n1) Import a private key of a brainwallet/ paper wallet.\n2) Send a small amount of bitcoin from that key.\n3) The user then secure deletes all copies of the wallet\n'for security'. If they are not careful they can delete\na change address with funds on it.\n\nIn MultiBit I have tried to reduce this possibility by:\n1) Hiding the ability to delete wallet (in the next version\nI am removing it entirely)\n2) There is always a single key in a new wallet. When\na user imports a key then that makes two. I always send\nthe change to the second address, if it is available.\n(This is bad for privacy but at least lessens the chances\nthat the funds become lost). \n\nIf users are determined to use a brain wallet and \nsecure delete every copy of the wallet after they use\nthem you cannot stop them (it is their machine after all)\nBut these two options help lessen the chance of bitcoin\nloss if they do.\n\nFor the HD version of MultiBit we are removing the import\nof individual private keys entirely and only supporting HD\naddresses, primarily for safety reasons.\n\nJim\n\nOn Mon, Dec 16, 2013, at 10:13 AM, Drak wrote:\n\u003e Not sure if this is the right place, but since a few wallet authors\n\u003e congregate here I though it might be the best place.\n\u003e \n\u003e It seems every once in a while you see stories of people accidentally\n\u003e paying huge fees. Today I read about a man who paid a 20.14BTC fee for a\n\u003e 0.05 BTC transaction[1], oops. There was another recently where someone\n\u003e paid a fee of about 200BTC which fortunately the pool operator refunded.\n\u003e \n\u003e It just occurs to me this kind of sad story could be averted if wallets\n\u003e implemented a confirmation box if the fee amount seems crazy - for example,\n\u003e if it's \u003e10x what the default fee should be, or if it's greater than x% of\n\u003e the sending amount. \"the fee seems unusually high, are you really sure you\n\u003e want to pay X in fees?\"\n\u003e \n\u003e I realise the exact details of this might need to be fleshed out given we\n\u003e want flexible fees, but it should be pretty simple to agree with what looks\n\u003e like an unusually large fee according to the going rate.\n\u003e \n\u003e Drak\n\u003e \n\u003e [1]\n\u003e http://www.reddit.com/r/Bitcoin/comments/1syu3h/i_lost_all_my_bitcoins_in_an_erroneous/\n\u003e ------------------------------------------------------------------------------\n\u003e Rapidly troubleshoot problems before they affect your business. Most IT \n\u003e organizations don't have a clear picture of how application performance \n\u003e affects their revenue. With AppDynamics, you get 100% visibility into your \n\u003e Java,.NET, \u0026 PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!\n\u003e http://pubads.g.doubleclick.net/gampad/clk?id=84349831\u0026iu=/4140/ostg.clktrk\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\n\n-- \nhttp://bitcoin-solutions.co.uk"}