Pinned Tweet
mmm.deadmanoz.xyz/
1/ Introducing the Merge Mining Monitor, another tool in service of the Bitcoin monitoring mission.
Merge mining lets child chains ride on Bitcoin's PoW, preserving the parent headers miners hashed.
deadmanoz retweeted
Replying to @benthecarman @kcalvinalvinn
That's already plenty right there, but there is a lot more. You also brush over the details with large categories, which is where 99% of the real work is, and where the number of people contributors decreases sharply.
Every day i am frustrated by how many interesting things i did not work on while i was focusing on other things. It's happened every single day since i've been working on Bitcoin full time, there is just too many important things to do, and so few people willing to do the work.
So stating "there isn't many things to work on" is just mind boggling to me. Maybe your interest is elsewhere now, and that's fine, but there is plenty of important things to tackle for whoever is interested in contributing to Bitcoin.
I left my overflowing todo list at the office, so here a few things off the top of my head while i'm in the train:
- stale tip relay
- more robust package relay that does not rely on orphanage
- block propagation through software improvements (net processing / validation split)
- CPU DoS mitigations through software improvements (idem)
- IBD improvements (idem)
- leveraging LLMs to write better security research tooling (fuzzing harnesses inside the project, fuzzamoto / Bedrock style frameworks, extensive invariant testing through blackbox and unit test s)
- tons of security hardenings all over the place (just look at the stopgap solution we add to mitigate CVEs and never cleanup as people move on to side projects or fixing more new CVEs)
- consensus protocol level hardenings with bip 54
- hardening address relay, which is vulnerable to spam while not being a great protection against motivated eclipse attacks
- reducing latency between pools and hashers through Stratum v2
- p2pool v2
- hardening the Core mining IPC interface which is new yet quickly becoming systemic infrastructure
- formal proving for some consensus critical parts of Core
- completing the pinning fixes for Lightning
- making Lightning gossip not dox your utxos
- explore scaling solutions that make alternative tradeoffs to Lightning, like Ark
- research more scaling solutions
- make progress on conservative first steps for more scripting capabilities like bip 448
- research game theory around CRQCs more rigorously
- help with efforts to bring a PQ output type to Bitcoin without compromising on important properties
- research more rigorously what a systemic change of cryptographic assumptions would look like, if possible without sacrificing core properties
- tons to explore and bring to market in self custody and hardware..
.. But stopping there as im getting off the train now. There is more, but i hope that already gives an idea that no there isn't nothing to work on these days.
I think the root issue in this difference of perspective is this common tendency in open source to just assume that "someone else is doing it". And i'm guilty of it too, last week we had somebody visit the office who is working on something i consider to be a priority for Bitcoin, ask around "who is working on X? Who is working on Y?" (both sub projects of the broader important work) and i was extremely surprised nobody picked those up yet. Everybody is talking about this, surely somebody must be working on THAT part?! Well no. The person has his hands full with another part, there is another person helping, and.. Barely anybody else.
Once you get into the weeds and get more familiar with who does the work concretely, the bus factor in Bitcoin is crazy, especially when put in perspective with what's at stake.
I'm replying to Ben but this is really a message to anybody reading this.
If you care about Bitcoin and find something interesting: step up anon, don't assume somebody else is already doing it, pick it up and contribute.
deadmanoz retweeted
There go the videos on YouTube as well 📉
The ones on Nostr are still up 👇
primal.net
I'll comply with the legal notices and stop making Office videos.
Coming soon: a tutorial series on how I make my videos, and original comedy with my own characters 🦆
If you haven't heard of Nostr, it's a decentralised X and much more. What the studios don't realise is that autonomous bots can already make their own Office videos with open models, create their own accounts and keep posting. The genie is out of the bottle. Taking down fan memes is a boomer move by NBC.
The quantum threat to Bitcoin is like Russian roulette, except that someone else is holding the gun.
It might not even be loaded...
And if it is, you don’t know which pull fires...
But you don’t hang around to find out...
You do something!
1
2
58
deadmanoz retweeted
Replying to @jack
@jack thinks bitcoin payment adoption isn’t where it could or should be. We want your ideas on how Block, Spiral, and you can improve adoption odds within 5 years. We need a shift to change our trajectory. Here’s more on our thinking. Now we want yours.
.@jack thinks bitcoin payment adoption isn’t where it should be. We want your ideas on how @Blocks, Spiral, and you can increase adoption within 5 years. Our trajectory needs changing. Here’s more on our thinking. Now we want yours: github.com/spiralxyz/bitcoin… View article
deadmanoz retweeted
New on Maple Max and Team: DeepSeek V4.1 Flash, abliterated.
Refusals removed from the model itself, so it works through security questions instead of declining them.
- 1M context
- Runs in the same attested enclaves as every Maple model
- Built for security research, code audits and red-teaming
Attackers already run uncensored models. Defenders shouldn't be stuck with "I can't help with that."
deadmanoz retweeted
Loupe findings have been landing in Bitcoin Core. During this cycle, five PRs landed: three have been merged, two are under review. Below is a thread on what each one caught and which Core dev implemented which fix.
A Bitcoin block can carry full proof of work and still be invalid.
I've catalogued 143 established cases from 2010 to 2026, including two previously unreported F2Pool timestamp failures this year.
deadmanoz.xyz/posts/2026/inv…
1/4
Both recent F2Pool headers survived in merge-mined chains, with no known Bitcoin-side capture.
These chains also yielded ~1,400 stales new to the stale-blocks collection. Monitoring them is essential to a holistic Bitcoin monitoring effort.
3/4
1
1
83
127 of the 143 blocks have no complete body, yet their failures remain independently checkable.
10 further reports still need evidence. Old node files, pool logs or archives could help.
Contributions and corrections:
github.com/bitcoin-data/inva…
4/4
1
3
69
deadmanoz retweeted
I built an agent to hunt for live mutants in Bitcoin Core's consensus-critical code.
It found several gaps that led to two Bitcoin Core PRs adding tests for things the existing suite missed.
I wrote about how it works and what it found:
viniciuscestari.dev/posts/hu…
I am looking for chain data from a number of chains that merge mined with Bitcoin to build out the dataset.
Missing data includes Xaya, i0coin, Jincoin, Jax.Network, Fusioncoin, Huntercoin, Bitcoin Stash, BLAST, VCash, Syscoin (v2).
Please reach out if you have any!
deadmanoz retweeted
The discussion between @Blockstream and the white-hat hacker (WHH) regarding the ~4000 BTC from @Liquid_BTC is happening in public. It seems to be their preference over email. As it's hard to follow the chain of messages in OP_RETURN, here's a summary with links.
11:30 AM PDT - WHH: "we are whitehats. contact us on chain"
mempool.space/tx/c103de95817…
12:31 PM PDT - Blockstream: "Please contact [email protected]"
mempool.space/tx/91271efcbb5…
6:49 PM PDT - Blockstream: [encrypted to hacker's key, PGP-signed by [email protected]]
mempool.space/tx/bd81219691e…
7:20 PM PDT - WHH: "sending most back to bc1qdlld6antmv4xug242ed83q7k4rqw50cwfns38szx4qu2f4jwaxxsuhwxxr, is that ok"
mempool.space/tx/3a3eac4a263…
8:27 PM PDT - WHH: "Please fix the bug first. The chain is under risk at latest commit right now. Make sure every node is patched. Then we will transfer the money back safely after confirming the fix." [+ PGP-encrypted details to Blockstream]
mempool.space/tx/83825b2135d…
8:30 PM PDT - Blockstream: "Yes, thank you." (PGP-signed; answers the 7:20 question, not the 8:27 one — confirmed in the same block)
mempool.space/tx/8a444eed65c…
Status as of 9:12 PM PDT: ~3,998.5 BTC still unmoved, no further messages from either side.
Hacker address: mempool.space/address/bc1ql4…
For those that have long running nodes, the Bitcoin data community would REALLY appreciate if you could check your node for stale block data:
github.com/bitcoin-data/stal…




















