Some Esplora backends require OAuth 2.0 authentication using the client credentials flow. The application exchanges a client ID and client secret for a short-lived access token, then sends that token with each Esplora request as an Authorization: Bearer header.
LDK Node supports fixed Esplora headers through set_chain_source_esplora_with_headers, so an application can provide an initial access token. However, OAuth access tokens expire, and the headers cannot be updated while the node is running. A long-running node must therefore be rebuilt or restarted when its token expires.
It would be useful to support an OAuth-aware or dynamic header provider for Esplora requests. The application could remain responsible for obtaining and renewing the token, while LDK Node requests the current authorization header when it makes an Esplora request. The updated header should apply to all Esplora operations without requiring the node to restart.
Some Esplora backends require OAuth 2.0 authentication using the client credentials flow. The application exchanges a client ID and client secret for a short-lived access token, then sends that token with each Esplora request as an Authorization: Bearer header.
LDK Node supports fixed Esplora headers through
set_chain_source_esplora_with_headers, so an application can provide an initial access token. However, OAuth access tokens expire, and the headers cannot be updated while the node is running. A long-running node must therefore be rebuilt or restarted when its token expires.It would be useful to support an OAuth-aware or dynamic header provider for Esplora requests. The application could remain responsible for obtaining and renewing the token, while LDK Node requests the current authorization header when it makes an Esplora request. The updated header should apply to all Esplora operations without requiring the node to restart.