{"type":"rich","version":"1.0","author_name":"npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpx","author_url":"https://nostr.ae/npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpx","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-11-27\n📝 Original message:Eric Lombrozo via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e writes:\n\u003e\u003eFrom an app developer's perspective, I think it is pretty blatantly \n\u003e clear that relative timelock is *the* critical exposed functionality \n\u003e intended here.\n\nAs someone who actually developed scripts using CSV, I agree with Mark\n(and Matt).  The relative locktime stuff isn't in this opcode, it's in\nthe nSequence calculation.\n\nSo, I vote to keep CSV called as it is.\n\nThanks,\nRusty."}