blank credentials by default are needed when:
- when running offline/no reason/intention to sync
- when syncing using a future tool (to be developed), that tool would run on :8332
and serve blocks from the Bitcoin P2P network. That won't require the BTC RPC/server
option, and by extension our config file won't be needed.
in any case new_miner_start() must go, even with blank credentials
the blank credentials cannot be entered into bitcoin's config file. that's exactly
what we need! the user who is capable to edit config files won't be able to do the
wrong thing but will instead be forced to set identical strong credentials in both files.
Right now new_miner_start() runs without credentials, it's the make_bitcoin_call() that stalls out without them. I may be taking your statement too literally here though lol. As far as I am aware, there is no way to connect to BTC over RPC WITHOUT a username and password. There are currently 3 options;
1. Config username and password. What we've been using so far.
2. Cookie file. In the absence of a username and password in its config, BTC will generate a .cookie file that has a username and password to use in it. While we could pull the username and password automatically from said file, we'd still need the user to indicate the path to that file. The only option I see, other than having the user place combfullui in the same folder as .cookie, is to use a config file to communicate the path.
3. RPCAuth. This is just a more complicated version of user/pass that generates a config entry for you, which you then have to place in your bitcoin.conf file.
can't comment on merged main page non synced messages, I don't see the code.
It's just
if height < uint64(fakeheight) || (!check_btc_is_caught_up() && check_connected()) {
fmt.Fprintf(w, `<h1>Wallet appears to be out of sync. Displayed balances are incorrect until wallet is fully synced:</h1>`)
}
Although I tried a full sync and, until I restarted my comb, the message wouldn't disappear, so I'm missing something atm.