<oembed><type>rich</type><version>1.0</version><author_name>npub1qf6k0f8p0h89d43l0vnx2xp5yrfgjyl8tg3hkg8jtyudrllgw2usdlfn9a</author_name><author_url>https://nostr.ae/npub1qf6k0f8p0h89d43l0vnx2xp5yrfgjyl8tg3hkg8jtyudrllgw2usdlfn9a</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-06-19&#xA;📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----&#xA;Hash: SHA512&#xA;&#xA;On 2015-06-19 17:50, Jeff Garzik wrote:&#xA;&gt; No.  You cannot know which is the &#39;right&#39; or wrong transaction.  One tx &#xA;&gt; has&#xA;&gt; obvious nSequence adjustments, the other - the refund transaction - may &#xA;&gt; not.&#xA;&#xA;I&#39;m still not seeing a case where a node could see conflicting &#xA;transactions on the network as part of a micropayment channel, and not &#xA;know it was observing the resolution of a channel rather than a likely &#xA;retail double spend.&#xA;&#xA;If both transactions have been broadcast, then one of the conflicting &#xA;members of the set will have nSequence adjustments.&#xA;&#xA;Maybe a clever griefer could try to make their retail double spend look &#xA;like a micropayment channel, but it seems like they&#39;d be missing the &#xA;other identifiable markers of that protocol.&#xA;&#xA;-----BEGIN PGP SIGNATURE-----&#xA;Version: GnuPG v2&#xA;&#xA;iQIcBAEBCgAGBQJVhFhqAAoJECpf2nDq2eYjWtgP/2ir11TUfxoIIzK9t0groKY3&#xA;yMR32HP3caDLKdc5ML41jf0l0cp7a54sFPuRE+Am8rkg9ogcf6fho/hCwLnhhNb4&#xA;YYBqJ2pzqCU1uN8jwPYSwSw3AO+F+hPE8gcm7lKD297a1k9xpYayAFjChJowoyNT&#xA;Wuq9YDkakQeSjV1aCiRHuXNxqnnbymf9xHEiB0buVnSgnyXrgZNCnefAo8DeXYqi&#xA;FTSceakNwdkklddK5ObNNK9ZoLpjHhX6hZwRiXsOoG+WUzXhLQ+BsyIFzsCKxQk1&#xA;cXjTvLn+Ub9FasRCK5KXMBkkPa1U5JLs1nTn6eTbPyroTs10WLkXWjIpZHrkf7ZW&#xA;9RsxoKIRaJur8gbYd6BMvV5rgkfGdb6j24pVNxFF2t89SLo44H0NvqE6koNzgubG&#xA;4DyXZ+UlzxzwRVBNDeF4pdlKZGsz2ycvQPuNHRoaZY2IsieMBN/5HEqGNOmXsvKf&#xA;tCg1SInO/FkE4njCxSW0R31s2KXCpgVCuq3qmoIKZobDdx7AC8GnpY1rdxUGpVoy&#xA;USJwZ2IOgtNfl/rBtOpkp/BaUCmCYOiUj13/ycDrqWvnM4TmiDdzJNEZNfez5UQp&#xA;Uvgvstoo88sewv9hGsuBWX0nC+ze/m43ZRReFhQDsypEaOw6pL2LSG9dD3tzulax&#xA;TrbPXPlN55NarQ3nmPIW&#xA;=Hj0x&#xA;-----END PGP SIGNATURE-----</html></oembed>