📅 Original date posted:2015-11-13 📝 Original message:On Fri, Nov 13, 2015 at ...

Gregory Maxwell [ARCHIVE] /

npub1f2n…rwet

2023-06-07 17:44:50

in reply to nevent1q…wvl0

📅 Original date posted:2015-11-13
📝 Original message:On Fri, Nov 13, 2015 at 9:48 PM, xor via bitcoin-dev
<bitcoin-dev at lists.linuxfoundation.org> wrote:
> BIP65 [1] says this:
>> Motivation
>> [...]
>> However, the nLockTime field can't prove that it is impossible to spend a
>> transaction output until some time in the future, as there is no way to
>> know if a valid signature for a different transaction spending that output
>> has been created.
>
> I'd interpret "can't prove that it is impossible to spend" = cannot be used
> for freezing funds.
>
> Then later, at "Motivation", it says:
>> Freezing Funds
>>
>> In addition to using cold storage, hardware wallets, and P2SH multisig
>> outputs to control funds, now funds can be frozen in UTXOs directly on the
>> blockchain.
>
> This clearly says that funds can be frozen.
> Can the BIP65-thing be used to freeze funds or can it not be?
>
> Notice: I am by no means someone who is able to read Bitcoin script. I'm
> rather an end user. So maybe I'm misinterpreting the document?
> I'm nevertheless trying to provide a "neutral" review from an outsider who's
> trying to understand whats new in 0.11.2.
> You may want to discard my opinion if you think that BIP65 is aimed at an
> audience with more experience.

The first text is explaining nlocktime without BIP65 in order to
explain the reason for having BIP65.

Author Public Key

npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet

Seen on

wss://relay.noswhere.com

Show more details

Published at

2023-06-07 17:44:50

Kind type

1 Short Text Note

Event JSON

{ "id": "3959ca46d4be045c24102015b2c3264fe1d6dfe0c992266f5a484d45ea123edd", "pubkey": "4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73", "created_at": 1686159890, "kind": 1, "tags": [ [ "e", "daf39e0a1dbaca24b6e2fe7def727146701a8f2511c7e675caee839a069071e5", "", "root" ], [ "e", "14424f8123bd3fc2a6f093e0d6a4ab2ce6359d56fd6bdaf3a5f1b2d78c3eb6fd", "", "reply" ], [ "p", "af7cc88ea10a48f7fa0f5d9577f25789ee53557a910736e58506f7d1354c1c18" ] ], "content": "📅 Original date posted:2015-11-13\n📝 Original message:On Fri, Nov 13, 2015 at 9:48 PM, xor via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e BIP65 [1] says this:\n\u003e\u003e Motivation\n\u003e\u003e [...]\n\u003e\u003e However, the nLockTime field can't prove that it is impossible to spend a\n\u003e\u003e transaction output until some time in the future, as there is no way to\n\u003e\u003e know if a valid signature for a different transaction spending that output\n\u003e\u003e has been created.\n\u003e\n\u003e I'd interpret \"can't prove that it is impossible to spend\" = cannot be used\n\u003e for freezing funds.\n\u003e\n\u003e Then later, at \"Motivation\", it says:\n\u003e\u003e Freezing Funds\n\u003e\u003e\n\u003e\u003e In addition to using cold storage, hardware wallets, and P2SH multisig\n\u003e\u003e outputs to control funds, now funds can be frozen in UTXOs directly on the\n\u003e\u003e blockchain.\n\u003e\n\u003e This clearly says that funds can be frozen.\n\u003e Can the BIP65-thing be used to freeze funds or can it not be?\n\u003e\n\u003e Notice: I am by no means someone who is able to read Bitcoin script. I'm\n\u003e rather an end user. So maybe I'm misinterpreting the document?\n\u003e I'm nevertheless trying to provide a \"neutral\" review from an outsider who's\n\u003e trying to understand whats new in 0.11.2.\n\u003e You may want to discard my opinion if you think that BIP65 is aimed at an\n\u003e audience with more experience.\n\n\nThe first text is explaining nlocktime without BIP65 in order to\nexplain the reason for having BIP65.", "sig": "3090bffea983b5b001309ebdcb9c5afa07d097798ab572301393675c317325d0faebf1fcc7737700be0abd92f33a879d49b9df7c305e8257578814208e717a4b" }