Published on: 2015-01-23T19:19:40+00:00
The email thread revolves around the potential risks associated with isolated signing devices without memory and discusses possible solutions to mitigate these risks. One suggestion made by Tamas Blummer is that nodes should not relay excessive fee transactions in order to reduce financial risk. While this proposal aims to address the issue, it is not a complete fix and does not provide detailed information on the specific risks or how they can be mitigated.On January 23, 2015, slush posted on the Bitcoin development mailing list about the progress and discussion surrounding the SIGHASH_WITHINPUTVALUE proposal. This proposal involves a hardfork that allows users to sign input values with the TxOut scripts, making it easier to transfer large amounts of data over communication channels. Slush highlights the relevance of this proposal as hardware wallets become more widespread. Slush mentions TREZOR as an example of a hardware wallet that streams and validates complex transactions. The proposed solution would significantly reduce the time required for signature verification, simplifying firmware and reducing security risks. However, existing coins would not be compatible with this proposal, necessitating software updates for senders to adopt new transaction methods.The proposal itself is considered non-intrusive as it does not alter TxOut scripts or tx/block parsing, except for verification purposes. Software developers are not obliged to implement the proposal unless they choose to upgrade their signers. Additionally, the proposal expands options for online-offline communication channels, improving overall security. Alan Reiner strongly encourages considering the inclusion of this proposal at some point.The writer of the email asks if there has been any progress or discussion regarding the increasing prevalence of hardware wallets. They stress the importance of finding a solution without specifying a particular one. They provide a link to a BitcoinTalk forum post and describe sitting next to a TREZOR device for 40 minutes during the streaming and validation of a complex transaction. The writer argues that finding a solution would optimize time, resources, and hardware costs, simplify firmware, and enhance security. They urge the community to collaborate in finding a widely agreed-upon solution to this real-world problem.
Updated on: 2023-08-01T11:15:45.461109+00:00