📅 Original date posted:2021-04-09
📝 Original message:>From https://bitcointalk.org/index.php?topic=1786.msg22119#msg22119:
We can't safely do OP_BLOCKNUMBER. In the event of a block chain reorg
> after a segmentation, transactions need to be able to get into the chain in
> a later block. The OP_BLOCKNUMBER transaction and all its dependants would
> become invalid. This wouldn't be fair to later owners of the coins who
> weren't involved in the time limited transaction.
>
> nTimeLock does the reverse. It's an open transaction that can be replaced
> with new versions until the deadline. It can't be recorded until it
> locks. The highest version when the deadline hits gets recorded. It could
> be used, for example, to write an escrow transaction that will
> automatically permanently lock and go through unless it is revoked before
> the deadline. The feature isn't enabled or used yet, but the support is
> there so it could be implemented later.
>
Unfortunately, limiting the maximum block height for a specific transaction
would have exactly the same problem as cited above for OP_BLOCKNUMBER.
On Fri, Apr 9, 2021 at 7:21 AM Erik Aronesty via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> is there any way to specify a maximum block height on a transaction?
>
> ie: this tx is only valid if included in a block with a certain height or
> less
>
> i feel like this would be useful
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210409/fed819a8/attachment.html>;
Russell O'Connor [ARCHIVE] /
npub1dw…8plrw
2023-06-07 22:51:37
in reply to nevent1q…3puj
Author Public Key
npub1dw88wd5gqsqn6ufxhf9h03uk8087l7gfzdtez5csjlt6pupu4pwsj8plrwPublished at
2023-06-07 22:51:37Event JSON
{
"id": "508e8c29a9f4720499d1340270c2d188ee24d8f2d63a28641b09bbadb6be3773",
"pubkey": "6b8e77368804013d7126ba4b77c7963bcfeff909135791531097d7a0f03ca85d",
"created_at": 1686178297,
"kind": 1,
"tags": [
[
"e",
"2ca67af6205ed29ec1dd161c5f9105b99f5d17e34b7b8d21e89961da7247de0a",
"",
"root"
],
[
"e",
"3bc2ead3d07594e870af9c594a278e65ac4fa9e50be468d8c56916cc60570039",
"",
"reply"
],
[
"p",
"22944ce1e29904e3826d25013a614e4665693ec514003efacc1b7586e8e5d0aa"
]
],
"content": "📅 Original date posted:2021-04-09\n📝 Original message:\u003eFrom https://bitcointalk.org/index.php?topic=1786.msg22119#msg22119:\n\nWe can't safely do OP_BLOCKNUMBER. In the event of a block chain reorg\n\u003e after a segmentation, transactions need to be able to get into the chain in\n\u003e a later block. The OP_BLOCKNUMBER transaction and all its dependants would\n\u003e become invalid. This wouldn't be fair to later owners of the coins who\n\u003e weren't involved in the time limited transaction.\n\u003e\n\u003e nTimeLock does the reverse. It's an open transaction that can be replaced\n\u003e with new versions until the deadline. It can't be recorded until it\n\u003e locks. The highest version when the deadline hits gets recorded. It could\n\u003e be used, for example, to write an escrow transaction that will\n\u003e automatically permanently lock and go through unless it is revoked before\n\u003e the deadline. The feature isn't enabled or used yet, but the support is\n\u003e there so it could be implemented later.\n\u003e\n\nUnfortunately, limiting the maximum block height for a specific transaction\nwould have exactly the same problem as cited above for OP_BLOCKNUMBER.\n\nOn Fri, Apr 9, 2021 at 7:21 AM Erik Aronesty via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e is there any way to specify a maximum block height on a transaction?\n\u003e\n\u003e ie: this tx is only valid if included in a block with a certain height or\n\u003e less\n\u003e\n\u003e i feel like this would be useful\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210409/fed819a8/attachment.html\u003e",
"sig": "2727f1f60ab86b618960ccd7dc91121142004d7c471278f1427bc13af4bd7adcc1d62f2fdfbf1ee2d4ef03aa2752553f289960ca4aca655133f7851ae9cd59dc"
}