<oembed><type>rich</type><version>1.0</version><author_name>npub1g5zswf6y48f7fy90jf3tlcuwdmjn8znhzaa4vkmtxaeskca8hpss23ms3l</author_name><author_url>https://nostr.ae/npub1g5zswf6y48f7fy90jf3tlcuwdmjn8znhzaa4vkmtxaeskca8hpss23ms3l</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2018-05-14&#xA;📝 Original message:Good morning Luke,&#xA;&#xA;&gt; (Maybe it should be the first output&#xA;&gt; &#xA;&gt; instead of the last... Is there any legitimate reason one would have multiple&#xA;&gt; &#xA;&gt; such dummy outputs?)&#xA;&#xA;None, but how about use of `SIGHASH_SINGLE` flag? If a dummy output is added as the first, would it not require adjustment of the inputs of the transaction?&#xA;&#xA;In context you are discussing the transaction serialization, though, so perhaps `SIGHASH_SINGLE`, is unaffected?&#xA;&#xA;Regards,&#xA;ZmnSCPxj</html></oembed>