As the mempool clears out, many chunky consolidations are confirming after languishing for months
For example this one was pending for 10 months
First Seen
2024-02-07 07:23:09 UTC
Unix time: 1707290589
Confirmation Time
2024-11-03 22:45:09 UTC
Unix time: 1730673909
At 2 Sat/vB block space is practically free, great for coffee purchases
Learn to process raw .blk data directly
I'm excited for DATUM to bring back coinbase tag flame wars
Why would it be concerning if the coinbase outputs of block 539209 were all spent?
I think we will be hearing a lot more about Core Untouched Soft Forks (CUSF).
I was skeptical, but knowing 60% of pools are merge mining I think it’s worth paying attention.
If you hear or read any useful discussion (pro or anti CUSF) let me know
IYKYK

This is a great read and addresses some awkward truths.
In addition to quality topics the editing of the Bitcoin Brief is top notch. Give it a listen nostr:note18ekqe4zggvr9p5n9yrchcq8zhy4fv4nd99m8arr4g0a4clxwdhns939ra2
In undertaking the latest mempool research report I was really surprised at the prevalence of merged mining.
60% of hashrate runs non bitcoin software altering their coinbase tx. How well reviewed & isolated is this code?
Would love to hear from miners
Hoping to clarify what seems to be a misunderstanding by nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx about how the Pi Zero hardware shapes the nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl security model.
(see: nostr:npub10uthwp4ddc9w5adfuv69m8la4enkwma07fymuetmt93htcww6wgs55xdlq #320)
I'm not about drama, certainly not looking to increase it.
Please give this a read and hit me back w/any questions:
https://gist.github.com/kdmukai/e270dd1c7b53b8daea4a9fc1ac89847c
1) Wholesale Replacement
If the total amount being secured by all users of the device is significant *to the attacker* wholesale replacement is a real risk.
This doesn’t require a malicious party within the intended sharing group, just for someone to make an undetected substitution while the device is not in use.
2) Shared Access “done right”
Shared access “done right” requires the device to be kept secure at all times, requires each user to verify software signatures and have access to a computer to reflash their SD prior to each use. If the amount being secured is small a mobile wallet sufficient IMO. For larger amounts the users should use their own devices.
If you are a bitcoin developer building something cool and you want tBTC4 coins for testing hit me up
The (free) distribution of tTBC4 coins to bitcoin projects continues.
I'm avoiding speculation, just reporting what I see from the onchain data.
The gap does appear to be specific to only a subset (there are pools which didn't have any interruption) so I don't think it's an issue regarding the progress of the reliant chains.
It would appear that something caused all the pools in group 3 to behave in a similar manner at the same time. More research is required but I thought it was worth noting
Approximately 60% of bitcoin blocks are merge mining other chains (since the last halving).
That's down from a peak of 96% in April 2020.
For our latest nostr:npub1m7qjg4hsa2q32rtekewpdn54guh508tlh6ztml7ssluj6vgflensy6m4gz report, nostr:npub18h0w55nsp839ezxnggf00jd2xc6yl0ht62mf5p8wwllu8s80wdcs83ws8m analysed which merge mining schemes are in use, and which miners are using them.
Looking at recent data we see different miner / pool groups.
Group 1. No Merge Mining
Foundry, MARA, SBI Crypto
Group 2. AuxPow & “Chain A”
ViaBTC, F2Pool & Luxor
Group 3. Distinct switching pattern
Binance Pool, BTCcom, Poolin, Braiins, ULTIMUS
Group 4. Other
Antpool, SECPOOL
Taking a longer view looking back to the genesis block we see that adoption of schemes has fluctuated wildly over time!
Read the short report here:
https://research.mempool.space/merge-mining-report/

Any Q's hit me up
Just published the latest nostr:npub18d4r6wanxkyrdfjdrjqzj2ukua5cas669ew2g5w7lf4a8te7awzqey6lt3 reseearch report for nostr:npub1m7qjg4hsa2q32rtekewpdn54guh508tlh6ztml7ssluj6vgflensy6m4gz

