📅 Original date posted:2014-02-12
📝 Original message:It's also not necessary for wallet software - it's really just for
human consumption.
A wallet can easily detect inputs being respent in another
transaction. You don't need a static hash for that (which wouldn't
need with all hash types, non-malleability double spends, ...).
On Wed, Feb 12, 2014 at 6:13 PM, Jeff Garzik <jgarzik at bitpay.com> wrote:
> On Wed, Feb 12, 2014 at 10:12 AM, Rune Kjær Svendsen
> <runesvend at gmail.com> wrote:
>> Instead of trying to remove the possibility of transaction
>> malleability, would it make sense to define a new, "canonical
>> transaction hash/ID" (cTxID),
>
> Yes, that is one proposal: https://github.com/sipa/bitcoin/commits/normtxid
>
> But it is not a complete solution for all transaction types.
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
> ------------------------------------------------------------------------------
> Android apps run on BlackBerry 10
> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
> Now with support for Jelly Bean, Bluetooth, Mapview and more.
> Get your Android app in front of a whole new audience. Start now.
> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Pieter Wuille [ARCHIVE] /
npub1tj…jtl6r
2023-06-07 15:13:31
in reply to nevent1q…zx4u
Author Public Key
npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6rPublished at
2023-06-07 15:13:31Event JSON
{
"id": "8e1da77ad92146e6aed38a9b36e24a0203999f248734e023bfa8575c4ccb020e",
"pubkey": "5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6",
"created_at": 1686150811,
"kind": 1,
"tags": [
[
"e",
"76969a008b621e54c247029127aebdfbea1794fb79dd58e07b32a76157512d29",
"",
"root"
],
[
"e",
"ad6b113de970fe2440a37010d50415956556f4b527575fcfc6646764fcef8ea7",
"",
"reply"
],
[
"p",
"b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11"
]
],
"content": "📅 Original date posted:2014-02-12\n📝 Original message:It's also not necessary for wallet software - it's really just for\nhuman consumption.\n\nA wallet can easily detect inputs being respent in another\ntransaction. You don't need a static hash for that (which wouldn't\nneed with all hash types, non-malleability double spends, ...).\n\nOn Wed, Feb 12, 2014 at 6:13 PM, Jeff Garzik \u003cjgarzik at bitpay.com\u003e wrote:\n\u003e On Wed, Feb 12, 2014 at 10:12 AM, Rune Kjær Svendsen\n\u003e \u003crunesvend at gmail.com\u003e wrote:\n\u003e\u003e Instead of trying to remove the possibility of transaction\n\u003e\u003e malleability, would it make sense to define a new, \"canonical\n\u003e\u003e transaction hash/ID\" (cTxID),\n\u003e\n\u003e Yes, that is one proposal: https://github.com/sipa/bitcoin/commits/normtxid\n\u003e\n\u003e But it is not a complete solution for all transaction types.\n\u003e\n\u003e --\n\u003e Jeff Garzik\n\u003e Bitcoin core developer and open source evangelist\n\u003e BitPay, Inc. https://bitpay.com/\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Android apps run on BlackBerry 10\n\u003e Introducing the new BlackBerry 10.2.1 Runtime for Android apps.\n\u003e Now with support for Jelly Bean, Bluetooth, Mapview and more.\n\u003e Get your Android app in front of a whole new audience. Start now.\n\u003e http://pubads.g.doubleclick.net/gampad/clk?id=124407151\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",
"sig": "425b0013247c5e756c25799860f952b3018b0e56f32ad289884befc9086a034632b597d13dab78d3cab6de1e292696a5cfd0f7366e023960d7b164b51bcb442d"
}