You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Electrum is a protocol, I think typically for light clients or users to connect over the internet to their home node. That is more the typical client-server relationship. Exposing a Capnp interface here would be for over applications to be compiled along with kernel-node, so the process can interact with the node but the two run separately. I am imagining this is mostly useful for GUIs that will embed their own wallet. In fact, the node can run 24/7 as a daemon on the machine and the GUI just needs to open a unix socket and catch up on whatever blocks it missed. So the purpose here would be to allow building bundled applications.
I'm not sure I see the distinction between what your proposing and existing electrum protocol. In fact, I think this project could implement electrum and that way maintain compatibility with wallets that already implement the electrum protocol. For example, here is a CLI I wrote some years ago: https://crates.io/crates/esplora-cli. The point is, if this project implemented electrum, and then, this cli could just be pointed at the kernel-node and call for example "broadcast" to broadcast a transaction..
Actually, the cli I posted above is esplora which is over HTTPs. Electrum uses JSON-RPC over TCP, SSL/TLS, or socks proxy (for Onion services). Although, i'm still wonder if what you are proposing could instead be done with electrum since that supports all the same functionality like broadcast tx, wait for next block etc.
Activity
yancyribbens commentedon Oct 19, 2026
This sounds similar in functionality then to the electrum protocol? Is there reason to prefer using this vs using electrum then? For example, electrs.
rustaceanrob commentedon Oct 24, 2026
Electrum is a protocol, I think typically for light clients or users to connect over the internet to their home node. That is more the typical client-server relationship. Exposing a Capnp interface here would be for over applications to be compiled along with
kernel-node, so the process can interact with the node but the two run separately. I am imagining this is mostly useful for GUIs that will embed their own wallet. In fact, the node can run 24/7 as a daemon on the machine and the GUI just needs to open a unix socket and catch up on whatever blocks it missed. So the purpose here would be to allow building bundled applications.yancyribbens commentedon Oct 25, 2026
I'm not sure I see the distinction between what your proposing and existing electrum protocol. In fact, I think this project could implement electrum and that way maintain compatibility with wallets that already implement the electrum protocol. For example, here is a CLI I wrote some years ago: https://crates.io/crates/esplora-cli. The point is, if this project implemented electrum, and then, this cli could just be pointed at the kernel-node and call for example "broadcast" to broadcast a transaction..
yancyribbens commentedon Oct 25, 2026
Actually, the cli I posted above is esplora which is over HTTPs. Electrum uses JSON-RPC over TCP, SSL/TLS, or socks proxy (for Onion services). Although, i'm still wonder if what you are proposing could instead be done with electrum since that supports all the same functionality like broadcast tx, wait for next block etc.