Immutable HTTP Password or Stronger Authentication for Truly Non-Custodial

[sepiropht]

I host phoenixd instances for clients’ non-custodial wallets, removing the seed phrase from phoenix/seed.dat after clients save it to ensure they control funds.

However, admins can change the --http-password to access API endpoints and steal funds, undermining non-custodial guarantees.

Can phoenixd support an immutable HTTP password, hashed and stored in /data after initial setup, to prevent updates?

If not, are there alternative authentication methods (e.g., client-signed requests) to restrict admin access completely? Running acinq/phoenixd:latest on testnet.