š
Original date posted:2015-11-13
š Original message: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.
Greetings and thanks for your work!
[1]
https://github.com/bitcoin/bips/blob/d0cab0379aa50cdf4a9d1ab9e29c3366034ad77f/bip-0065.mediawiki
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151113/81565bca/attachment.sig>;
xor [ARCHIVE] /
npub14aā¦g6tv3
2023-06-07 17:44:50
in reply to nevent1qā¦t4z8
Author Public Key
npub14a7v3r4ppfy007s0tk2h0ujh38h9x4t6jyrndev9qmmazd2vrsvqxg6tv3Seen on
wss://relay.nostr.bandPublished at
2023-06-07 17:44:50Event JSON
{
"id": "14424f8123bd3fc2a6f093e0d6a4ab2ce6359d56fd6bdaf3a5f1b2d78c3eb6fd",
"pubkey": "af7cc88ea10a48f7fa0f5d9577f25789ee53557a910736e58506f7d1354c1c18",
"created_at": 1686159890,
"kind": 1,
"tags": [
[
"e",
"daf39e0a1dbaca24b6e2fe7def727146701a8f2511c7e675caee839a069071e5",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "š
Original date posted:2015-11-13\nš Original message:BIP65 [1] says this:\n\u003e Motivation\n\u003e [...]\n\u003e However, the nLockTime field can't prove that it is impossible to spend a\n\u003e transaction output until some time in the future, as there is no way to\n\u003e know if a valid signature for a different transaction spending that output\n\u003e has been created.\n\nI'd interpret \"can't prove that it is impossible to spend\" = cannot be used \nfor freezing funds.\n\nThen later, at \"Motivation\", it says:\n\u003e Freezing Funds\n\u003e \n\u003e In addition to using cold storage, hardware wallets, and P2SH multisig\n\u003e outputs to control funds, now funds can be frozen in UTXOs directly on the\n\u003e blockchain.\n\nThis clearly says that funds can be frozen.\nCan the BIP65-thing be used to freeze funds or can it not be?\n\nNotice: I am by no means someone who is able to read Bitcoin script. I'm \nrather an end user. So maybe I'm misinterpreting the document?\nI'm nevertheless trying to provide a \"neutral\" review from an outsider who's \ntrying to understand whats new in 0.11.2.\nYou may want to discard my opinion if you think that BIP65 is aimed at an \naudience with more experience.\n\nGreetings and thanks for your work!\n\n[1] \nhttps://github.com/bitcoin/bips/blob/d0cab0379aa50cdf4a9d1ab9e29c3366034ad77f/bip-0065.mediawiki\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 836 bytes\nDesc: This is a digitally signed message part.\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151113/81565bca/attachment.sig\u003e",
"sig": "68e1a08b8383f05efd465630b79fffa343ff12e4e198707e7a28da8e757fc7b854020a02cc5c782b1f776558ea7e24dd5d81b4dfe2238fe5e19efdca44ccba95"
}