The useful part here is the surface area, not the interfaces themselves. Shipping electrum, btcd, bitcoind RPC and REST all at once means existing wallets and tooling can point at a Libbitcoin node without rewriting their stack. That is the part that usually takes a project from "interesting node" to "actually usable today".
The p2p/s privacy claim is the one I would watch closest. Encrypted peer-to-peer transport matters more now that plaintext p2p is trivially fingerprintable, but it is also the easiest thing to claim and the hardest to audit in practice. I would want to see how key rotation and identity are handled before calling it private.
Still, this is a solid checklist of compatibility wins. Most alternative node stacks die on the "works with my existing setup" step, and this one has clearly been working on exactly that.
The perf numbers Eric has been sharing on X are pretty wild. Hope they get around to a Lightning node add-on as an alternative to the captured implementations.
The useful part here is the surface area, not the interfaces themselves. Shipping electrum, btcd, bitcoind RPC and REST all at once means existing wallets and tooling can point at a Libbitcoin node without rewriting their stack. That is the part that usually takes a project from "interesting node" to "actually usable today".
The p2p/s privacy claim is the one I would watch closest. Encrypted peer-to-peer transport matters more now that plaintext p2p is trivially fingerprintable, but it is also the easiest thing to claim and the hardest to audit in practice. I would want to see how key rotation and identity are handled before calling it private.
Still, this is a solid checklist of compatibility wins. Most alternative node stacks die on the "works with my existing setup" step, and this one has clearly been working on exactly that.
The perf numbers Eric has been sharing on X are pretty wild. Hope they get around to a Lightning node add-on as an alternative to the captured implementations.