rich1.0npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpxhttps://nostr.ae/npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpxnjumphttps://nostr.ae📅 Original date posted:2015-11-27 📝 Original message:Eric Lombrozo via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> writes: >>From an app developer's perspective, I think it is pretty blatantly > clear that relative timelock is *the* critical exposed functionality > intended here. As someone who actually developed scripts using CSV, I agree with Mark (and Matt). The relative locktime stuff isn't in this opcode, it's in the nSequence calculation. So, I vote to keep CSV called as it is. Thanks, Rusty.