BitcoinLizard

At this point BIP444 proponents are either: A) Nefarious B) Bots C) Willfully ignorant D) Just plain ignorant There is no longer a reason to engage with them any longer.

Joining team filter has been a massive engagement boon for D level #Bitcoin influencers.

nostr:nprofile1qqsx8lnrrrw9skpulctgzruxm5y7rzlaw64tcf9qpqww9pt0xvzsfmgppemhxue69uhkummn9ekx7mp0qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09u47mdqx - I'm seeing this error when trying to zap with snort.social: webln.enable() failed (rejecting further window.webln calls until the next reload) This used to be a problem with btcpay: https://github.com/v0l/snort/issues/332 Has something broken with Snort and btcpay?

#Bitcoin Core 30 is malware! I started it up and my CPU usage jumped! Knots node runners were right! nostr:nevent1qqsvxzru60a8wfk98dcp0nen5g9a6mkhy4m3uqvjyjwk9tmpnnw0wespzfmhxue69uhkummnw3eryvfwvdhk6tczyzmf9l8rhwnmml5sl0vl5f9jz8j5ena2yqagg8zxa088t4wau4pp7qcyqqqqqqg43jh5y

PSA for Core 30 node runners. If you have coinstatsindex enabled (not default) a re-indexing will occur upon first startup which will cause a notable increase in CPU and disk activity until the re-indexing is complete. https://github.com/bitcoin-core/bitcoin-devwiki/wiki/30.0-Release-Candidate-Testing-Guide/#81-coinstatsindex-change

This 2679 byte op_return containing a png file was confirmed on chain. I broadcast it using Core version 29.1 to the regular Bitcoin relay network (no out of band service needed). Core 30 makes no difference in the ability of a "spammer" to confirm transactions with large op_returns. Here is the TXID: 0d5f273d09c1a4665634fd25d5a17b879d8843de5edc40b8b7d8671500dd16b6 It took a little while to be mined, I must have gained a new peer that would relay it to a miner. I broadcast it block height 916259 and it was confirmed at 619343. I paid less than 1 Sat/vB. Knots users didn't have this transaction in their mempool but now they store it on their node. Filters won't keep these transactions off your node. Filters do not work. You can view it for yourself with this command (Thank you nostr:nprofile1qqsdnpcgf3yrjz3fpawj5drq8tny74gn0kd54l7wmrqw4cpsav3z5fgpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uq3jamnwvaz7tmjv4kxz7fwwdhx7un59eek7cmfv9kz74rw7n6): bitcoin-cli getrawtransaction 0d5f273d09c1a4665634fd25d5a17b879d8843de5edc40b8b7d8671500dd16b6 true | jq -r '.vout[0].scriptPubKey.asm' | cut -d ' ' -f2 | xxd -r -ps | base64 -d > filters.png Here are my node settings that allowed me to send this transaction and get it relayed (and mined): minrelaytxfee=0.00000100 mempoolminfee=0.00000100 incrementalrelayfee=0.00000100 datacarriersize=100000 If you are running Knots because you believe it will prevent "spam", you are being fooled by Mechanic. The only way to keep this type of transaction off your node it to fork #Bitcoin consensus rules.

Running Bitcoin Core 29.1 datacarriersize=100000 minrelaytxfee=0.00000100 mempoolminfee=0.00000100 incrementalrelayfee=0.00000100