A message to those on team #fixthefilters - your time would be better spent earning sats, which you can then use to fund development of a bitcoin node implementation which implements your desired configuration options. It's a cat and mouse game and the cat is currently asleep.

adding policy rules as a non mining node makes about as much difference as posting your opinion on the github pull request both sides agree on this 😂

The recent pull request to bitcoin core made by peter todd (pull 32359) removes the code to enforce a policy limit on the size and number of OP_RETURN outputs. Additionally, he proposes the removal of the configuration options to allow node runners to modify the maximum size of data carrying transactions.

If bitcoin core doesn’t have the functionality that you want you can build it, and share it with the world. If other people share your views they can also run that code.

You are making a transaction, you check mempool and set what seems like an appropriate fee, but then a new degen mint drops and your transaction gets buried. New transactions coming in push your transaction further back, and 24 hours later it's 10 blocks deep. Fortunately you used Mempool Auto Accelerator with a 24h Time Delay trigger, and your transaction confirms in the next block. I have 10 beta access spots, dm me.

unusual 151 sat/vB tx

The Mempool Open Source Project®

Explore the full Bitcoin ecosystem with The Mempool Open Source Project®. See the real-time status of your transactions, get network info, and more.

If you are building something on bitcoin and use @mempool every day I want to hear from you, drop me a message.

confused about the different mining options with @OCEAN ? I've made a table to compare STRATUM (V1) with DATUM. Will add in STRATUM V2 & DEMAND in the future.

Mining Pool Comparison

Compare different mining pools including STRATUM and DATUM options

confused about the different mining options with @OCEAN ? I've made a table to compare STRATUM (V1) with DATUM. Will add in STRATUM V2 & DEMAND in the future. http://poolcomparison.orange.surf

"solo mining" is currently confusing as a term because it's being used to mean different things by different people (often with an agenda). Sovereign Mining: You select the transactions Lotto Mining: You get the full block reward

Miners use picks, not hammers 🔨 -> ⛏️

The Mempool Open Source Project®

Explore the full Bitcoin ecosystem with The Mempool Open Source Project®. See the real-time status of your transactions, get network info, and more.

Babylon unstaking continue to account for a significant proportion of all bitcoin transaction fees, even hitting 50% on 11th April.

Blockspace is currently so cheap that a 4MvB inscription tx costs just 0.02 BTC

The Mempool Open Source Project®

Explore the full Bitcoin ecosystem with The Mempool Open Source Project®. See the real-time status of your transactions, get network info, and more.

At OP_NEXT Day 1 (2h15m) Ryan Rasmussen mentioned that BitwiseInvest had to deal with dusting attacks shortly after BITB addresses were published. I've noticed that many (22) of the wallet addresses which are no longer used have received address poisoning attack transactions. example:

The Mempool Open Source Project®

Explore the full Bitcoin ecosystem with The Mempool Open Source Project®. See the real-time status of your transactions, get network info, and more.

Live view of @mononaut announcing the release of v3.2

The Mempool Open Source Project® v3.2.0 is here 🚀 Highlights: - Support for v3 transactions - Support for anchor outputs - New UTXO bubble chart on the address page - DATUM miner tags - Tags to identify runestone messages and inscriptions - Package broadcast - Stratum job data visualizations - Taproot multisig labels - Transaction & PSBT preview feature - Address poisoning detection

GitHub

Release v3.2.0 · mempool/mempool

The Mempool Open Source Project® v3.2.0 Highlights Support for v3 transactions Support for anchor outputs New UTXO bubble chart on the address...

babylon unstaking transactions are accounting for a large proportion of all transaction fees, because they use a hard coded fee rate

who could have predicted this

Even with the mempool this empty, it's possible to get your transaction stuck for 1 hour by using 1 sat/vB instead of 1.1 sat/vB