{"type":"rich","version":"1.0","author_name":"npub1jjaydndmznp5g07v9cf83dq6667rdgk4j52f662qv5k6klsky53sruchtw","author_url":"https://nostr.ae/npub1jjaydndmznp5g07v9cf83dq6667rdgk4j52f662qv5k6klsky53sruchtw","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2017-01-09\n📝 Original message:Would there be an objection to making op_return outputs with two\npushdatas standard (same max data size)?\n\nUse case is mostly tagging transactions so they can be returned by bloom\nfiltering nodes:\n\nOP_RETURN \u003ctag\u003e \u003cdata\u003e\n\nSince bip37 nodes test each data element in each output script (which I\nbelieve applies to op_return as well?) it provides a lightweight way of\nfetching transactions where the tag matches a specific pattern.\n\nIt appears a sizable number of nodes/miners already accept such\ntransactions as this one was mined in the first block...\nhttps://blockchain.info/tx/400b4738f1e4eab4062e085623b9a3a71670f5c0d42e32dbe5a4e71da5baabe0\n\n- Chris"}
