Pinned Tweet
the big question that lies ahead for rbitcoin is: how can we be sure that there won't be a consensus divergence with bitcoin core (or some other dominant implementation)?
the current answer is that rbitcoin has a comprehensive (probably the most comprehensive) suite of consensus tests which fully validate its consensus implementation on every build. that combined with running differential fuzz and 70+ of core's functional test scripts every night is what gives me the confidence to (recklessly?) run it as my sole source of truth for my wallets going forward. development of rbitcoin has led to one additional consensus test case being proposed for bitcoin core, 3 consensus differences being raised with rust-bitcoin (one already rejected because it is historical only and no historical block hit it), and 4-5 additional consensus rules being proposed for hornet.
what would it take for you to trust rbitcoin to stay in consensus with bitcoin core?
the crash outs will continue until @rbitcoin_org becomes the reference client
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
An update to Bitcoin Core's security policy
via @darosior on the Bitcoin-Dev mailing list
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
Feature: ask what a wallet looked like at an older block.
Add ?asof=<blockhash> to rbitcoin's Esplora address, UTXO, tx status or outspend calls. Later confirmations vanish, mempool is ignored, headers name the block.
Time travel, best chain only.
rbitcoin.org/esplora/
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
Great to see this open-sourced finally.
Argo is what enabled the 1,000x reduction in Babylon's "BABE", as well as the paper we released last week, Talos.
Talos adds ~5x on-top of the 1,000x from Argo.
TL;DR Garbled Circuits (BitVM3 / Glock) has become very elegant and small.
Excited to open-source Argo!
The most practical trust-minimized Bitcoin bridging:
• Setup time: ~100ms
• Offchain cost: ~10MB
• Onchain cost: ~$8
🤖 Throw your clankers at it and help us harden it
github.com/idealgroup/argo?_
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
Replying to @Rob1Ham
The indexes in Core are sadly all async and disconnected from the chain state. That might be okay if Core added an rbitcoin-style asof parameter to REST queries.
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
The eMudhra incident is a striking illustration of the fundamental flaw in how SSL certificates work: every Certificate Authority is effectively empowered to vouch for every website on the planet.
That’s insane.
Hopefully the world eventually adopts a Bitcoin name system.
Let's just remove AssumeUTXO github.com/bitcoin/bitcoin/p…
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
Why do we need to install a Bitcoin consensus client and Electrs in 2026 to manage wallets easily? It's brittle and insane.
Bitcoin ... lets download 1TB
Esplora ... lets download 2TB then compact to 1TB
The consensus client should index addresses through a config option.
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
NEW: Jeremy Rubin, inventor of CTV, implements @roasbeef ‘s LayerTree proposal in Sapio, his covenant focused scripting engine for Bitcoin
inspired by this, I have produced an implementation of the LayerTree prototype (level at beautiful Mid) in Sapio github.com/sapio-lang/sapio/…
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
New on rbitcoin.org: an Esplora API reference, generated from the repo's OpenAPI spec.
Every route, the ?asof=<blockhash> dialect for point-in-time wallet queries, chain-tip headers, and error codes. The OpenAPI file is downloadable too.
rbitcoin.org/esplora/
A lot of bank card info may have been stolen/hacked with the recent vulnerabilities. I found unauthorized transactions for the first time on my virtual btc-fiat card. Might be a good time to check your card use and temporarily freeze it.
at the rust-bitcoin summit, it has become clear that before rbitcoin takes over as the reference consensus implementation for bitcoin it will take over as the reference esplora implementation.
Rearden 🛩️ BIP448 🥖 fork/acc retweeted
inspired by this, I have produced an implementation of the LayerTree prototype (level at beautiful Mid) in Sapio github.com/sapio-lang/sapio/…
Announcing LayerTree: a new tree-based scaling solution for Bitcoin that permits O(1), independent of the number of users in the system: xitter.cf/lightning/status/21108…
A single UTXO can hold the balance of millions of users as an off-chain Merkle-sum tree.
Transaction introspection techniques permit batched exit from the system in a single transaction w/o any pre-signing: layertree.tech
























