ExploreTrendingAnalytics
Nostr Archives
ExploreTrendingAnalytics
Super Testnet11d ago
A project in 2018 called Webcoin built a bitcoin browser wallet in SPV mode Details here: https://github.com/mappum/webcoin To talk to bitcoin nodes, it relied on a TCP->Websocket proxy called Webcoin Bridge Details here: https://github.com/mappum/webcoin-bridge Is anyone running that bridge anymore?
💬 4 replies

Replies (4)

Super Testnet11d ago
It's annoyingly hard to use bitcoin's p2p layer from browsers. BTC nodes don't understand the handshakes browsers do when they make GET/POST requests, unless you use RPC, which is permissioned. It's cool that Webcoin found a way, but it only works if folks run the bridge software
0000 sats
Super Testnet11d ago
A few services make data from bitcoin's p2p layer *available* to browsers, e.g. block explorers, some electrum servers (including esplora servers), and block-dn. But it'd be great if browsers could talk to *any* node instead of placing the load directly on those limited services.
0000 sats
Super Testnet11d ago
On that note, did you know the websocat tool can expose any TCP port (including bitcoin's) as if it was a websocket port? Yep! It's got a built-in converter that will do the websocket handshake and then directly pipe TCP data to the browser. Consider running it on your node!
0000 sats
Super Testnet11d ago
I'd love it if people started doing that and then a directory of websocket-compatible bitcoin nodes was created. Maybe they could signal on nostr. Or even signal on bitcoin's p2p layer, using service bits. It's possible to make bitcoin's p2p layer web-friendly - but it takes work
0000 sats