Bitcoin Consultant | P210N Owner | Vibes | sp1qqwkt0aetchmm5gzucxych7l7kxaevetpx7npe54e236zqv73jevr5qucy5pgnut9fm7syjmlqv9ykm3qzzpfc0v3j737plzvvuy8k08a4scn62wl

Genesis Block
Joined April 2011
Include

Only show posts containing:

Exclude

Hide posts containing:

Time range
-
Minimum likes
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
Please update your BitcoinJS and related dependencies. We have backported some fixes all the way to BitcoinJS v5. Big thanks to everyone mentioned in this post, especially to @landabaso who helped coordinate with the reporters and publish fixes.
We've just published 15 security advisories across BitcoinJS libraries (14 High and one Medium), with patched releases available on npm. This follows work with @junderwood4649 and the reporters to investigate the issues, prepare fixes and provide backports for the maintained release lines. The findings cover areas including transaction and block parsing, PSBT fee calculations, proof verification, mnemonic handling and elliptic-curve operations. Their impact depends on the affected version and how an application uses the library. Each advisory explains those conditions and the required remediation. If you maintain an application using BitcoinJS packages, please check your direct and transitive dependencies and upgrade affected versions. For bitcoinjs-lib, the patched releases are 7.0.5, 6.1.10 and 5.2.3, depending on your release line. Both tiny-secp256k1 and bitcoin-js/tiny-secp256k1-asmjs have fixes in 2.2.5. The other patched releases are bip39 3.1.2 and 2.6.1, bip38 3.1.2 and 2.0.4, bolt11 1.4.2, merkle-lib 2.0.11 and bip32-utils 0.11.2. Some fixes require changes in the application as well as a dependency update. You can find the affected ranges, technical details and upgrade guidance here: github.com/bitcoinjs/bitcoin… github.com/bitcoinjs/tiny-se… github.com/bitcoinjs/bip39/s… github.com/bitcoinjs/bip38/s… github.com/bitcoinjs/bolt11/… github.com/bitcoinjs/merkle-… github.com/bitcoinjs/bip32-u… Thanks to the researchers and reporters: the Bitcoin Red Team (@Rob1Ham, @callebtc and @danielabrozzoni), @0xaudron, @real_a_kalout and ARSB (github.com/ARSB1).
2
11
1
28
2,845
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
An airplane just landed at a heliport. In lower Manhattan. That is the @ElectraAero EL-2, the ultra-short takeoff and landing prototype aircraft. CEO Marc Allen said Monday it was the first time the manufacturer has shown the EL2’s capabilities publicly in such an environment. Story ➡️ vist.ly/5q45c #eVTOL #airplane #newyorkcity #heliport #aviation
1
15
3
92
7,117
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
nixos is great because you can be like "my machine is perfect. i wish i had another one exactly like it" and then just do it
1
1
1
219
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
Everyday is zero-day these days
2,687
2,729
535
32,848
2,775,396
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
Jameson Lopp: "We are orders of magnitudes away from a real usable quantum computer that can crack the algorithm that is used to secure your Bitcoin."
6
9
95
6,286
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
Replying to @reardencode
Definitely a point here too. K-shaped change in the amount of thoughts thunk.
2
1
7
408
Replying to @jamesob
I don't think that's right. For those of us who have "always wanted to X but it took too much investment", it instead leads to us thinking harder than ever before. That doesn't apply to everyone, but I certainly find myself thinking hard far more hours each day now than I used to. I do my thinking in how I prompt my agent to extract the meaningful questions from the code and how to direct it to make the correct changes based on those extractions. I used to _waste_ my thinking on just navigating the code itself, but I no longer have to waste my own cycles on that. I spend inference tokens on that instead.
2
14
273
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
There's no such thing as too much RAM.
10
9
132
4,461
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
If Bitcoin failed what would be the reason?
11%LLMs solving DLP
19%Quantum computer
49%World looses Interest
21%other (write comment)
1,143 votes • 11 hours
94
2
1
29
12,902
Replying to @renepickhardt
Ossification leads to falling decentralization over time
2
3
167
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
grok in control
So IMO we should all just use the rbitcoin API since it already exists and is trivial for clients to adapt to. We *really* don't want another API that everyone has to support, I think this time around we'll just say no.
1
4
582
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
INVESTIGATION UPDATE Many of you have asked how personal information ended up in the phishing emails, particularly those who ordered from us years ago. Here is what we have found so far. Phishing emails: We have identified more than 23,000 phishing email attempts across our email systems, including 19,057 messages delivered through Mailgun and 1,503 messages sent through Google Workspace. Some addresses received multiple messages, and some attempts failed or were stopped before delivery. These numbers do not tell us how many people had personal information exposed. We are still determining that number and will share it once we can confirm it. Older orders and abandoned carts (WooCommerce): Before moving to Shopify in May of this year, our store ran on WooCommerce. We had configured automatic redaction of customer details 60 days after shipping. When we viewed those orders in our store admin, the customer details were no longer visible and the orders showed as redacted. During past database migrations, orders were copied into a new set of tables, but copies remained in the old tables. The redaction process updated the newer tables, which were also what our store admin displayed. Orders therefore appeared redacted even though older copies still contained personal information. We also found personal information in other order and refund records, as well as abandoned carts. This included shipping details entered by someone who never completed a purchase. We are still checking the historical settings and redaction process to understand why these records retained data. Those older records were held in systems the attackers were able to reach. We relied on the redaction shown in our admin dashboard, and we now know that was insufficient to verify that the underlying data had been removed. Whatever the shortcomings in the tools we used, protecting your information was still our full responsibility. We plan to share our findings with WooCommerce and the relevant plugin developers. When an order is marked as redacted, its personal information should not remain in another table in the same database. For other WooCommerce store owners: do not rely solely on what your admin dashboard shows when personal data is redacted. Have your developer or agent check the entire database for information left behind, including legacy tables, refund records, and abandoned carts. This is especially important if you have used WooCommerce for years or have been through database migrations. Recent orders (Shopify): Customer details from orders placed on our Shopify store since May may also have been exposed. We are still investigating the extent of any unauthorized access. These orders had not yet been manually redacted. We updated our privacy policy when we moved to Shopify and were building a tool to automate redaction, but automatic deletion was not yet active. Other possible sources: We have received reports of phishing emails containing personal details that customers say they never shared with us. We are investigating whether the attackers combined information from our systems with data obtained elsewhere, but we have not confirmed a connection to breaches at other companies. Historical support records are also part of our investigation. What we have done: We have revoked affected email credentials, cleared queued phishing messages, and taken affected legacy services offline while preserving evidence. Our investigation into the full extent of the compromise is continuing. We have found no evidence that this incident compromised Passport devices or the private keys they hold. The phishing emails are designed to trick you into revealing your recovery phrase, and including your correct personal information makes them more convincing. Never enter your recovery phrase into a website or share it with anyone, including someone claiming to be Foundation. We will continue sharing confirmed findings and publish our full report when the investigation is complete.
33
33
17
147
30,990
Yeah, a good idea. Will consider and PRs welcome ;)
1
45
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
If someone is using an untrusted pruned rbitcoin node to serve their wallets, I just don't even know what to do about that. Pruned mode is for people running their own node, so they can _trust_ it to have validated the signatures already.
1
1
1
273
If someone is using an untrusted pruned rbitcoin node to serve their wallets, I just don't even know what to do about that. Pruned mode is for people running their own node, so they can _trust_ it to have validated the signatures already.
1
1
1
273
Open source. The way.
Replying to @andrew_s_toth
Update: Due to improvements inspired by @rbitcoin_org 's address index, my proposed index now takes only ~52 GB of disk space. A synced Bitcoin Core node with a full address index can be run in as little as 65 GB. This is a level of compression not possible without a UTXO set.
2
17
520
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
Update: Due to improvements inspired by @rbitcoin_org 's address index, my proposed index now takes only ~52 GB of disk space. A synced Bitcoin Core node with a full address index can be run in as little as 65 GB. This is a level of compression not possible without a UTXO set.
8
11
4
79
3,534
No code yet written to recover pruned data. Would be interested in PRs along that line, to rebuild a full store by fetching all blocks and just hash checking the parts we don't have to make sure they fit into the store. Since the pruned data is only needed for running scripts and serving IBD (or serving as an ordinals explorer), I imagine not many folks will go from pruned to unpruned. Still seems a nice capability.
1
41