Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 9EA4674 for ; Thu, 3 Mar 2016 13:11:16 +0000 (UTC) X-Greylist: delayed 00:09:03 by SQLgrey-1.7.6 Received: from librelamp.com (librelamp.com [45.79.96.192]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8866EF0 for ; Thu, 3 Mar 2016 13:11:15 +0000 (UTC) Received: from localhost.localdomain (68-189-42-147.dhcp.rdng.ca.charter.com [68.189.42.147]) by librelamp.com (Postfix) with ESMTPSA id 130531232 for ; Thu, 3 Mar 2016 13:02:12 +0000 (UTC) To: bitcoin-dev@lists.linuxfoundation.org From: Alice Wonder Message-ID: <56D835D3.9070902@librelamp.com> Date: Thu, 3 Mar 2016 05:02:11 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Thu, 03 Mar 2016 14:57:34 +0000 Subject: [bitcoin-dev] consensus rule change for TX fee safety X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2016 13:11:16 -0000 I think the next hard fork should require a safety rule for TX fees. https://blockchain.info/tx/6fe69404e6c12b25b60fcd56cc6dc9fb169b24608943def6dbe1eb0a9388ed08 15 BTC TX fee for < 7 BTC of outputs. Probably either a typo or client bug. My guess is the user was using a client that does not adjust TX fee, and needed to manually set it in order to get the TX in the block sooner, and meant 15 mBTC or something. I suggest that either : A) TX fee may not be larger than sum of outputs B) TX fee per byte may not be larger than 4X largest fee per byte in previous block Either of those would have prevented this TX from going into a block. Many people I know are scared of bitcoin, that they will make a TX and make a mistake they can't undo. Adding protections may help give confidence and there is precedence to doing things to prevent typo blunders - a public address has a four byte checksum to reduce the odds of a typo. This kind of mistake is rare, so a fix could be included in the coming HF for the possible July 2017 block increase. Thank you for your time. Alice Wonder