Why another node?

rbitcoin explores a different way to store and validate Bitcoin’s history, with wallet serving in the same process.

Its design sits between libbitcoin’s relational archive and Bitcoin Core’s block files. Previous outputs come from indexed history, without a separate UTXO database.

Its independent consensus implementation uses Rust, rust-bitcoin types, and libsecp256k1 cryptography: another implementation reading and checking the same chain.

Read how the archive works.

How it was built

Brandon Black, known as Rearden or @reardencode, designed and directed the project. Grok wrote the code, with help from Claude, using grok build and Cursor.

AI made it possible to build a design he had wanted to pursue for years. Hear the story in his conversation with Pleb Underground.

Work on something concrete

Review a consensus edge case. Reproduce a bug. Improve a test or an explanation. Start with contributor setup, then use the issue tracker for non-sensitive work.

Vulnerabilities take a different route: report them privately. Do not put an unfixed exploit in a public pull request.

Contact

General: freedom@reardencode.com
Security: security@reardencode.com
Updates: @reardencode on X
Code: reardencode/rbitcoin

If the node is useful

Support the work with sats. Copy an address into a compatible wallet.

Silent payment

On-chain · requires a BIP352-compatible wallet

sp1qqwkt0aetchmm5gzucxych7l7kxaevetpx7npe54e236zqv73jevr5qucy5pgnut9fm7syjmlqv9ykm3qzzpfc0v3j737plzvvuy8k08a4scn62wl

Strike

Lightning

reardencode@strike.me

Cash App

Lightning

reardencode@cash.app

Open source

rbitcoin and this website are available under MIT or Apache-2.0. Read the copyright and license notice.