Issue with RPC Credentials on Service Restart

[k0gen]

I've identified an issue where changes to the bitcoind RPC's user or password disrupt the operation of LND. This issue is not related to Bitcoin v26, but rather to the services that depend on it.

When the password policy changes (as it did in Bitcoin v26), users are forced to update their passwords. This change seems to disrupt their LND service.

The current behavior is that LND reads RPC credentials only during configuration changes/saves. The expected behavior is for LND to read RPC credentials on each service restart, regardless of configuration changes.

This issue needs to be addressed to prevent service disruption for old bitcoind users updating their passwords.