LesLie retweeted
There is no shortage of important things to tackle in Bitcoin, and there is not enough of us to tackle it all.
If you care anon, get involved. Don't assume "it's being worked on".
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.
LesLie retweeted
To secure your Bitcoin simply roll 100 dice, shuffle a deck of cards, use pencil and paper and set up a multi-vendor multisig using hardware wallets buried in three different time zones.
What the fuck is wrong with you guys.
LesLie retweeted
Note: The primary purpose of disclosing vulnerabilities is to ensure that potential victims are as informed as those who exploit them.
en.wikipedia.org/wiki/Full_d…
LesLie retweeted
Bitcoin Core v32.1: a deeper look
First, why no 32.0?
It was tagged on October 21 but never fully announced or released. A remotely triggerable TCP crash was reported on October 23 and 32.1 shipped on October 27 (yesterday) with that fix and two others.
I'll dig into the security updates, but this release also represents months of testing, maintenance, and work to make Bitcoin easier to verify and use.
What went into these v32.1 changes and what do Bitcoin users get from them?
LesLie retweeted
Some thoughts about hardware, especially wallet-specific UX.
Until very recently, I was strongly against "non-standard" products, like Bitkey for example.
I'm now realizing that trying to support everything that comes out in Bitcoin is impossible, the amount of work to just follow all the new stuff (Silent Payments, Ark, Bip89 CCD, etc etc) and the work needed in UX to show that clearly to the user (so they don't fuck up) is just near impossible.
We took some design decisions in Liana, for example not having Absolute Timelocks available in the community software, because we don't have a good UX for it (and again, we believe users will fuck up). Or we only accept descriptors with one non-timelocked path. Again, just for UI/UX perspective.
Now that Liana has a really good UX (check out v16rc1), the main complaint of not-yet-users is the shitty signing device UX. I now understand why Bitkey went the route they did.
I still wish they had support for other software coordinators, including with Miniscript, and I hope they will. But I get that having control over the hardware UX is a huge selling point for end users.
TLDR: I think it's time for Wizardsardine to really start exploring hardware, either through custom firmware of existing devices, and/or making our own devices.
Obviously with a MVMS (multivendor-multisig) approach first, so we would still support all the Miniscript devices out there.
If you guys have any thoughts on this, shout.
LesLie retweeted
Users have often asked for a way to skip deactivated letters in the @SeedSigner bip39 mnemonic word entry UI to minimize nav movements.
It's a harder problem than it initially seems.
I brainstormed a bit with Claude and landed on this cool "Pack each row" approach.
LesLie retweeted
The documentation is finally flowing.
libbitcoin.info/configuratio…
👇
Replying to @stephanlivera @andrew_s_toth
A high performance full chain address index adds no time to sync and requires no more than 8GB. The one show here is maximally sized at 18 GB.
libbitcoin.info/node-perform…
44
#libbitcoin is coming.
Here's my proposal to add an address indexer to Bitcoin Core. It takes about 62 GB of disk space today, and can be run pruned. So a node with a full address index can be run with < 100 GB of disk space.
github.com/bitcoin/bitcoin/p…
53
LesLie retweeted
An update to Bitcoin Core's security policy
via @darosior on the Bitcoin-Dev mailing list


















