Jan b retweeted
hmmmmmmmmm i wonder why they chose such a weak private key for a CA hmmmmmmmmmmmmmm
Replying to @astuyve
Oh god: The p384 private keys are randomly selected integers between 1 and 256, the private keys are effectively all-zeroes apart from the last byte
11
11
218
20,931
Fun fact: when building Bitcoin Core’s bitcoind on modern systems, the x86_64 build compiles 10 more source files than the arm64 build.
1
5
282
Jan b retweeted
bitcoin 0.1
i rebuilt satoshi's 2009 bitcoin.exe byte for byte! afaik nobody has been able to perfectly recreate the executable published in 2009 from source, because we didn't know the exact build environment that was used. using opus 5.5, i reverse-engineered satoshi's build machine from the binary. it now outputs an exe with the exact same sha256 as the 2009 release!
2
4
88
10,954
Jan b retweeted
Surround yourself with people who see a flying car and say, "Awesome!" Not people who see a flying car and say, "It's not actually flying" or "I don't see the point." This post is not about cars :)
1,102
5,238
46,179
494,864
Jan b retweeted
This is amazeballs.
Wait what? @COLDCARDwallet
6
3
28
2,370
A new release candidate of Bitcoin Core, v32.0rc4, is available for testing. This is a new major release, and follows v31.1. Work-in-progress release notes are here: github.com/bitcoin-core/bitc… Binaries are available here: bitcoincore.org/bin/bitcoin-…
12
22
83
7,324
A new release candidate of Bitcoin Core, v32.0rc3, is available for testing. This is a new major release, and follows v31.1. Work-in-progress release notes are here: github.com/bitcoin-core/bitc… Binaries are available here: bitcoincore.org/bin/bitcoin-…
12
26
116
12,305
Ahmet Kurt (@startimeahmet) and Jan B (@_jan__b) joined Optech to discuss Newsletter #424: News ● Proposal for a post-quantum Lightning Network (1:10) Selected Q&A from Bitcoin Stack Exchange ● What would be a drawback if sum instead of SHA256 of amounts was used in the taproot signature message? (36:18) ● Post-BIP110 fork is it necessary to resync from block 0? (39:32) ● Can a Bitcoin node build a partial UTXO set from only the most recent blocks and use it to validate new transactions? (42:16) Releases and release candidates ● Bitcoin Core 32.0rc2 (21:13) ● Core Lightning 26.06.8 (45:36) ● LDK v0.3-rc2 (47:15) Notable code and documentation changes ● Bitcoin Core #34566 (51:31) ● BIPs #1951 (54:14) ● BIPs #2224 (57:45) ● Core Lightning #9507 (1:02:00) ● Core Lightning #9508 (1:07:35) ● Core Lightning #9509 (1:12:02) ● Core Lightning #9510 (1:16:03) ● Core Lightning #9513 (1:20:01) ● LND #11198 (1:21:47) ● LND #11146 (1:24:15) ● LND #11132 (1:27:20)
1
9
11
2,561
Jan b retweeted
‼️ just got a pretty smart github OAuth phishing/ATO attempt on my personal account. attacker created a repo named after my github username, opened an issue mentioning me with a fake account-access alert, which triggered a real email from notifications@github.com. “This wasn’t me” → attacker-controlled GitHub Pages → real github.com OAuth consent page for an app called “profile security settings”, asking for public/private repo access + permission to update GitHub Actions workflow files. no fake github login page. the email is github, the auth page is github. the malicious part is the OAuth app + redirect flow. the page is just an obfuscated redirector, while the OAuth callback forwards the returned code/state to the same backend: github.com/api6268/code-839c… also caught two other username-specific phishing issues from the same github account before they disappeared. some indicators: issue account: 6119f4f OAuth app: profile security settings consent: Authorize request-6286 landing: api6268[.]github[.]io/code-839c74ee/ related landing: api25cd[.]github[.]io/account-13e95c92/ callback: request-6286[.]github[.]io backend: gitmain[.]serveblog[.]net route ID: 9e52a992
18
44
277
22,928
The edge cases always occur
"this edge case would never happen in production"
6
1
112
4,821
A new release candidate of Bitcoin Core, v32.0rc2, is available for testing. This is a new major release, and follows v31.1. Work-in-progress release notes are here: github.com/bitcoin-core/bitc… Binaries are available here: bitcoincore.org/bin/bitcoin-…
36
40
138
16,927
32.0rc2 testing binaries are now available bitcoincore.org/bin/bitcoin-… Includes the new getopenrpcinfo RPC (shoutout @willcl_ark). It returns a machine-readable OpenRPC spec of the entire RPC API, useful for generating client code and docs or diffing between releases.
2
12
31
1,119
Jan b retweeted
x402 lets agents pay for API calls using almost every form of digital money under the sun—except for the first digital money. Then @benthecarman got Lightning merged into the spec and now, BLAM, every agent is a bitcoiner.
The spec for lightning in x402 was merged last night! github.com/x402-foundation/x…
13
38
184
69,486
Jan b retweeted
New zine drop 🐱 OP_CAT! 🐱
8
23
101
6,541
Jan b retweeted
I wrote a blog post on the recent exploits in the Bitcoin ecosystem, how Bitcoin Core is holding up, and how I think the community can get ahead of the models: dergoegge.de/blog/somethings…
4
45
153
61,020
New release: Electrum 4.8.2. This is another security update, so please upgrade. Thanks to all contributors and researchers who reported issues to us. electrum.org/#download
15
64
353
33,001
Jan b retweeted
Our third-party e-mail provider has been breached. Please be aware that the email named ‘Critical Security Alert: STM32 Entropy Vulnerability’ is not coming from us, and it’s a phishing attempt. Do not click on any link. We have taken down the domain, and we are investigating the situation, including how the hackers got access to our legit domain.
976
1,371
5,576
3,441,191
Jan b retweeted
1/6 libsecp256k1 formal verification update: In June, I finished proofs for all 38 scalar functions and 22 int128 functions in the extracted libsecp256k1 backend, including internal helpers.
4
8
25
1,994