📅 Original date posted:2014-10-01
📝 Original message:I like the proposal.
I suggest that applications and nodes should only broadcast transactions
having OP_CHECKLOCKTIMEVERIFY a few blocks after the timeout value.
If a node broadcasts a TX having OP_CHECKLOCKTIMEVERIFY and nLockTime is
equal to the current height and equal to the timeout value, but that
peer is one block behind in the blockchain, the transaction will be
rejected by the peer and the source will be banned.
Another option will be not to ban peers sending transactions failing to
verify OP_CHECKLOCKTIMEVERIFY , but I don't like this.
Still another option would be that the sender checks periodically the
height of it's peers (using the version command) in order to be sure to
send the transaction having OP_CHECKLOCKTIMEVERIFY only to the peers
that are up to date with the blockchain.
Regards,
Sergio.
Sergio Lerner [ARCHIVE] /
npub1vr…nc7jf
2023-06-07 15:26:04
in reply to nevent1q…ytkj
Author Public Key
npub1vrm6r7z5yreclgndkf90fqesh5vqpmfmaucks32zv0w0emmz4r8qznc7jfPublished at
2023-06-07 15:26:04Event JSON
{
"id": "a655ba1dd00f9aea56ce7d91270544f48c8c6ee0c196b834eaa9fd8c4fd51d58",
"pubkey": "60f7a1f85420f38fa26db24af48330bd1800ed3bef3168454263dcfcef62a8ce",
"created_at": 1686151564,
"kind": 1,
"tags": [
[
"e",
"b0d4dbe43a898155b6750ed1dce6a700ce007fe7f2dce49b1bbfe7e2cca60c4c",
"",
"root"
],
[
"e",
"a4b49d44b8f68a36fdf84b4bca6084d15f7d5e78f5dd308bec8cbbc2e7a6a7f0",
"",
"reply"
],
[
"p",
"daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa"
]
],
"content": "📅 Original date posted:2014-10-01\n📝 Original message:I like the proposal.\n\nI suggest that applications and nodes should only broadcast transactions\nhaving OP_CHECKLOCKTIMEVERIFY a few blocks after the timeout value.\nIf a node broadcasts a TX having OP_CHECKLOCKTIMEVERIFY and nLockTime is\nequal to the current height and equal to the timeout value, but that\npeer is one block behind in the blockchain, the transaction will be\nrejected by the peer and the source will be banned.\n\nAnother option will be not to ban peers sending transactions failing to\nverify OP_CHECKLOCKTIMEVERIFY , but I don't like this.\n\nStill another option would be that the sender checks periodically the\nheight of it's peers (using the version command) in order to be sure to\nsend the transaction having OP_CHECKLOCKTIMEVERIFY only to the peers\nthat are up to date with the blockchain.\n\nRegards,\n Sergio.",
"sig": "cb8ab1f74d75efd1ac7368d191f48a4cf9fb4790c7b02eb9eaf057a3c6b3c5cadb76c9a1c2565f200c4c4230b4429f74a27c971e58f22545ddbb3c42c48c83dd"
}