rbitcoin 0.9 should be released this week, depending how testing goes. this release will feature docker builds plus major improvements in performance, stability, and reliability along with new features like blindbit serving and trusted peer mode and more.
If you've valued my work on rbitcoin to date, please donate to support ongoing development!
For funding transparency, donations have so far covered inference costs and my travel for TABconf and rust-bitcoin summit, but no living expenses over 3.5 months of full time development.
sp1qqwkt0aetchmm5gzucxych7l7kxaevetpx7npe54e236zqv73jevr5qucy5pgnut9fm7syjmlqv9ykm3qzzpfc0v3j737plzvvuy8k08a4scn62wl
yes. I know. donations would be easier if I supported legacy addresses, but I don't yet.
[email protected]
[email protected]
Or X money!
Rearden π©οΈ BIP448 π₯ fork/acc retweeted
If Bitcoin failed what would be the reason?
11%LLMs solving DLP
17%Quantum computer
52%World looses Interest
20%other (write comment)
531 votes β’ 20 hours 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.
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.
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.
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.
Rearden π©οΈ BIP448 π₯ fork/acc retweeted
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.
Rearden π©οΈ BIP448 π₯ fork/acc retweeted
ANNOUNCEMENT: SPAM EMAILS HAVE BEEN SENT THAT APPEAR TO HAVE COME FROM OFFICIAL FOUNDATION DOMAINS.
We have traced this back to one or more compromised API keys on Cloudflare, and have already revoked all API keys.
The malicious domain in the spam email has been taken down.
Funds stored on Passport are safe and Passport hardware is not compromised.
We are working nonstop to discover exactly what happened and will put out a report ASAP.
Rearden π©οΈ BIP448 π₯ fork/acc retweeted
Opus 5.5 rewrote all of Noah in native (Swift + Kotlin) in 5 days.
Results:
Pixel 6:
Cold start: 4.3s -> 1.4s (-65%)
Memory: 262 mb -> 128 mb (-51%)
Apk size: 105mb -> 61mb (-42%)
Scroll jank β οΈ: 0.13% -> 1.2% (Fixing this)
iPhone 17:
Cold start: 1.42s -> 0.85s (β40%)
Memory: 105mb -> 30mb (β71%)
Download size: 35.6mb -> 31.0 MB (β13%)
Rearden π©οΈ BIP448 π₯ fork/acc retweeted
rbitcoin-beignet lightning node is up on mainnet. I'm playing with fire here.
037d8e59b42c5da87e97cb6efd5f2bda2192dc725e261b91ed0b29c158a0928d29@ekbugzu4kswcwmbtc5avwsiqysdfcol5z4wjai25bprnisrmq6srurid.onion:9101
Replying to @chamath
Pretty much.
As of the past few weeks, debt markets have almost entirely shut off access to money for any company that doesnβt have substantial revenue independent of AI data centers.
SpaceX closed $40B of debt for GPUs, but weβre investment grade and have Starlink & launch revenue.
That means the 200+ neoclouds are going to see guppy-level death and consolidation. Some will make it through, but not many.
Rearden π©οΈ BIP448 π₯ fork/acc retweeted
Task Manager TMOG is doing very well! But it might not meet your definition of "vibe-coded".
AI largely wrote the code. The distinction is that the ARCHITECTURE was mine; it was defined by me as part of a 107-page spec. That's where AI struggles.
It's like how a skyscraper still needs a skilled architect, but the construction trades themselves are now largely automated. But if you have a bunch of steel workers and drywallers show up and just start working, you get slop.
Slop doesn't work, and it doesn't sell. But carefully designed, created, and curated high-quality software does, regardless of provenance!
In the end, quality matters. Still unsure? Try it yourself: tmog.org
Rearden π©οΈ BIP448 π₯ fork/acc retweeted
No human will ever write code better than LLMs. Accept this fact, stop pretending, and move on.
Rearden π©οΈ BIP448 π₯ fork/acc retweeted
What matters is the resulting behavior, not the code itself.
That said, both humans and agents do better working on clean, modular code, so I do push code quality per hard on rbitcoin... Without looking at it most of the time.
I can tell when code quality isn't good in an area by how many tokens and review cycles it takes for the agents to be satisfied. For example.
rbitcoin performs very well in most node+wallet+explorer use cases, so the results speak for themselves largely.
Rearden π©οΈ BIP448 π₯ fork/acc retweeted
Yes, multiple robust projects with good BDFLs and meaningful adoption would seem to be a better form of decentralization than a dominant, ostensibly leaderless or rule-by-commitee one.
Rearden π©οΈ BIP448 π₯ fork/acc retweeted
Replying to @vnprc_
BDFL is a fundamentally superior governance model to committee.
Committee was maybe necessary in bitcoin because of the difficulty in guaranteeing consensus compatibility. We are fixing that.
Cc @eric_lombrozo @HornetNode @Rob1Ham
the biggest innovation of rbitcoin over bitcoind is removing the decision making committee
As you can imagine, the @rbitcoin_org project fully embraces this mentality.
It started as ~60% a joke and me wondering what was possible, and the answer appears to be that A LOT is possible.
In the modern world, someone with sufficient intelligence, domain knowledge, and technical background (or willingness to learn fast) can accomplish previously impossible things in a short time.
At first I thought it was AI psychosis, but I'm starting to think that rbitcoin is actually really good and useful software.





















