rich1.0npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58https://nostr.ae/npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58njumphttps://nostr.ae📅 Original date posted:2015-06-19 📝 Original message:On Fri, Jun 19, 2015 at 10:48 AM, <justusranvier at riseup.net> wrote: > On 2015-06-19 17:40, Jeff Garzik wrote: > >> Making multiple incompatible versions of a spend is a -requirement- of >> various refund contract protocols. >> > > Is there not a dedicated field in a transaction (nSequence) for express > purpose of indicating when a protocol like this is in use? > No. You cannot know which is the 'right' or wrong transaction. One tx has obvious nSequence adjustments, the other - the refund transaction - may not. -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150619/260466f9/attachment.html>