🏷️ Categories: bitcoin-dev
quoting naddr1qq…kag8📝 Summary: Peter Todd proposed removing restrictions on OP_Return outputs, despite potential transaction pinning vectors. John Light emailed Peter with questions about the impact on full node operators. ZmnSCPxj asked if there are tools for full node operators to prune OP_RETURN data, and Murch mentioned an HTML attachment that was removed.
👥 Authors: • Murch ( Murch [ARCHIVE] (npub148n…tkk4) ) • Peter Todd ( Peter Todd [ARCHIVE] (npub1m23…2np2) ) • John Light ( John Light [ARCHIVE] (npub1zss…aenv) ) • ZmnSCPxj ( ZmnSCPxj [ARCHIVE] (npub1g5z…ms3l) )
📅 Messages Date Range: 2023-08-03 to 2023-08-09
✉️ Message Count: 4
📚 Total Characters in Messages: 5127
Messages Summaries
✉️ Message by Peter Todd on 03/08/2023: The author of the pull request intends to remove restrictions on OP_Return outputs, despite potential transaction pinning vectors.
✉️ Message by John Light on 06/08/2023: John Light has sent an email to Peter regarding his proposal on removing OP_RETURN output count and data size limits, asking questions about the impact on full node operators.
✉️ Message by ZmnSCPxj on 08/08/2023: The question is about whether there are tools available for full node operators to prune
OP_RETURNdata from their nodes. The answer explains thatOP_RETURNoutputs are already pruned and discusses the concept of pruning in the context of the UTXO database.✉️ Message by Murch on 09/08/2023: The text contains an HTML attachment that was removed. The URL for the attachment is provided for reference.
Follow Bitcoin Mailing List (npub15g7…08lk) for full threads
⚠️ Heads up! We've now started linking to replaceable long-form events (NIP-23), which allow for dynamic display of thread details like summaries, authors, and more. If you're unable to see this, your client may not support this feature yet.