Nice write up by @bitcoinbrink grantee @theStack, comparing the performance of ECDSA signature validation in libsecp256k1 and OpenSSL. Nearly 10 years on, libsecp256k1 is ~8x faster than OpenSSL, and performance improvements continue to be made. The devs have been doing

Bitcoin Core now has an interface for its consensus code - it only took a decade. https://t.co/w9r8AKmnLl

Good time to backup (and maybe even mirror) your GitHub repository issues and PRs if they contain discussion worth keeping. Tooling is available here:

Kudos to @Bitcoin_Devs running the evening "Lightning Crashes" Warnet workshop at @tabconf. Learning how to jam channels and OOM kill nodes LND v18 and v19.

The Bitcoin Core development process and distribution model actually makes it somewhat harder to fix security issues, compared to other serious software distributors. Take Google Chrome as an example. The CVE fixing happy path is to develop and review a fix in private, push that

Don’t read some third-hand misinformed commentary drivel on this site, if you want to know about Bitcoin Core v30 and about some overhyped drama your read about, read the actual source from people who are thinking deeply about these issues and making decision ⬇️

A non-pruned full node takes a good chunk of disk space, but big SSDs are expensive. The blockchain data contributes most of the footprint, but it is not read often. Keep the data directory (e.g., UTXO set) on your SSD, but store the blockchain on an HDD: `-blocksdir`

@coinjoined @davidmarcus @spark @XverseApp @josibake Yeah, this is a problem. The Silent Payments BIP is final and being used in the wild. Changing it now could lead to loss of funds. Spark also benefits from open source by being derived from my statechains protocol - any chance a good faith effort can be made to limit the damage?

@GrassFedBitcoin @OrangeSurfBTC You know why, you're just engaging in bad faith. But i'll repeat the reason for anyone lurking who's not aware. The point of making it bigger was that some applications want to have a proof of publication for a modicum amount of data (like Lightning does) in case a specific

@start9labs @callebtc The Knots 28.1 tag differs from Bitcoin Core 28.1 by 1,370 commits and 28,511 LOC (+25,871, -2640) across 550 files. If you were aware of that and think that "infinitesimal" is a good description of that patch set, we’ll have to agree to disagree. Sauce: https://t.co/r6dVLi3oxG

Bitcoin Core is looking for a volunteer Greek translation coordinator! Help keep the UI accurate and up to date for Greek-speaking users. Interested? DM me on Twitter, Transifex, or GitHub to get involved. https://t.co/pY05Z73ktI

I've written a bit about a project I've been working on for a while: peer-observer: A tool and infrastructure for monitoring the Bitcoin P2P network for attacks and anomalies https://t.co/doLMGV98Bx

I have too many other projects currently, but I think this could be a fun side-project for someone: Can we spot public spy-Electrum servers run by Chainanalysis? https://t.co/knoB0vlGJW

@dhh @mitchellh @Shopify you would end up where everyone else ends up with nix: you will absolutely hate it, except that you cannot stop using it anymore, because its mere existence makes everything else seem wrong

I've persistent my notes on the May 2023 Bitcoin Core node DoS problems. These are background information for the disclosure from last year. When non-ideal sorting, mass BRC-20 mints, and spy nodes caused a CPU Denial-of-Service on the Bitcoin network: https://t.co/KZvpPo2Ivh

🎉Localhost Research has been formally recognized as a 501(c)(3) non-profit! All donations are now tax deductible. Learn more: https://t.co/BJ8OQFGPyz

Have you, too, had enough of Core devs abusing their power to release highly reviewed software with sane defaults? Come to my bitcoinkernel workshop at @BTCPrague's dev/hack/day and take the first step towards becoming your own tyrannical full node dev.

We’ve got one shot at fixing the law or Americans simply won't have access to the best wallets available and US devs will be locked out of providing the best UX! It’s time for Bitcoiners and crypto bros to come together and fight for our right to access our wallets, before its

Currently, more than ~500000000000000000000000 (500 zeta or 5×10²³) hash attempts are required on average to mine a block. https://t.co/izyC9WFhGv