> Having a node set-up will allow you to more easily test and query the RPC/REST API, and begin monitoring new transactions added to the bitcoin blockchain/mempool.
> The default bcoin HTTP server listens on the standard RPC port (8332 for main, 18332 for testnet, 48332 for regtest, and 18556 default for simnet). It exposes a REST json api, as well as a JSON-RPC api.
Seems bcoin doesn't connect you directly, but rather to a node they're running elsewhere.
I can’t answer that question, it does implement server and client and the demo does try to download the whole blockchain on your browser (I’m not sure who has the bandwith to play with that demo)
It’s tho in production use and many people like the project cause it’s a full node implementation.
I assume there is some kind of bridge server, or supernode, to allow the browser node to connect (via websocket?) to the actual Bitcoin network?