<oembed><type>rich</type><version>1.0</version><author_name>npub1jjaydndmznp5g07v9cf83dq6667rdgk4j52f662qv5k6klsky53sruchtw</author_name><author_url>https://nostr.ae/npub1jjaydndmznp5g07v9cf83dq6667rdgk4j52f662qv5k6klsky53sruchtw</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2017-01-09&#xA;📝 Original message:Would there be an objection to making op_return outputs with two&#xA;pushdatas standard (same max data size)?&#xA;&#xA;Use case is mostly tagging transactions so they can be returned by bloom&#xA;filtering nodes:&#xA;&#xA;OP_RETURN &lt;tag&gt; &lt;data&gt;&#xA;&#xA;Since bip37 nodes test each data element in each output script (which I&#xA;believe applies to op_return as well?) it provides a lightweight way of&#xA;fetching transactions where the tag matches a specific pattern.&#xA;&#xA;It appears a sizable number of nodes/miners already accept such&#xA;transactions as this one was mined in the first block...&#xA;https://blockchain.info/tx/400b4738f1e4eab4062e085623b9a3a71670f5c0d42e32dbe5a4e71da5baabe0&#xA;&#xA;- Chris</html></oembed>