Is your feature request related to a problem? Please describe.
I would like to see a clear separation between the machine which runs LND and the location of the keys/macaroons. Currently the user has to pass the stateless_init field into the API calls in order to prevent the macaroon being saved on the machine. To avoid this, having a config in LND itself would make sure the macaroons are never written to disk.
Describe the solution you'd like
An option in the config, like: lnd.stateless_init=true which always uses the stateless init flow for the RPCs.
Perhaps the user should have a way to know if this feature is enabled or not. Not sure how that would look like.
Describe alternatives you've considered
Additional context
Is your feature request related to a problem? Please describe.
I would like to see a clear separation between the machine which runs LND and the location of the keys/macaroons. Currently the user has to pass the
stateless_initfield into the API calls in order to prevent the macaroon being saved on the machine. To avoid this, having a config in LND itself would make sure the macaroons are never written to disk.Describe the solution you'd like
An option in the config, like:
lnd.stateless_init=truewhich always uses the stateless init flow for the RPCs.Perhaps the user should have a way to know if this feature is enabled or not. Not sure how that would look like.
Describe alternatives you've considered
Additional context