feat(electrum): add JWT authentication support via ConfigBuilder

Author: EddieHouston

crates/electrum/src/bdk_electrum_client.rs

@@ -603,6 +603,44 @@ impl<E: ElectrumApi> BdkElectrumClient<E> {
     }
 }
 
+impl BdkElectrumClient<electrum_client::Client> {
+    /// Creates a new BDK Electrum client from a URL with custom configuration.
+    ///
+    /// This is a convenience method for creating an Electrum client with custom settings
+    /// such as JWT authorization providers, timeouts, or proxy settings.
+    ///
+    /// # Example with JWT Authentication
+    ///
+    /// ```no_run
+    /// # use bdk_electrum::{BdkElectrumClient, electrum_client};
+    /// # use std::sync::Arc;
+    /// let config = electrum_client::ConfigBuilder::new()
+    ///     .authorization_provider(Some(Arc::new(|| {
+    ///         // Your token provider that fetches/refreshes JWT
+    ///         Some("Bearer your-jwt-token".to_string())
+    ///     })))
+    ///     .timeout(Some(30))
+    ///     .build();
+    ///
+    /// let client = BdkElectrumClient::from_config("tcp://server:50001", config)?;
+    /// # Ok::<(), electrum_client::Error>(())
+    /// ```
+    ///
+    /// # Arguments
+    ///
+    /// * `url` - Electrum server URL (e.g., "tcp://host:port" or "ssl://host:port")
+    /// * `config` - Configuration created via [`electrum_client::ConfigBuilder`]
+    ///
+    /// [`electrum_client::ConfigBuilder`]: crate::electrum_client::ConfigBuilder
+    pub fn from_config(
+        url: &str,
+        config: electrum_client::Config,
+    ) -> Result<Self, electrum_client::Error> {
+        let client = electrum_client::Client::from_config(url, config)?;
+        Ok(Self::new(client))
+    }
+}
+
 /// Return a [`CheckPoint`] of the latest tip, that connects with `prev_tip`. The latest blocks are
 /// fetched to construct checkpoint updates with the proper [`BlockHash`] in case of re-org.
 fn fetch_tip_and_latest_blocks(

crates/electrum/src/lib.rs

@@ -11,11 +11,31 @@
 //! where the range of possibly used scripts is not known. In this case it is necessary to scan all
 //! keychain scripts until a number (the "stop gap") of unused scripts is discovered.
 //!
+//! # JWT Authentication
+//!
+//! If your Electrum server requires JWT authentication (e.g., behind an API gateway),
+//! you can use the [`AuthProvider`] to dynamically inject tokens:
+//!
+//! ```no_run
+//! # use bdk_electrum::{BdkElectrumClient, electrum_client};
+//! # use std::sync::Arc;
+//! let config = electrum_client::ConfigBuilder::new()
+//!     .authorization_provider(Some(Arc::new(|| {
+//!         Some("Bearer your-jwt-token".to_string())
+//!     })))
+//!     .build();
+//!
+//! let client = electrum_client::Client::from_config("tcp://server:50001", config)?;
+//! let bdk_client = BdkElectrumClient::new(client);
+//! # Ok::<(), electrum_client::Error>(())
+//! ```
+//!
 //! Refer to [`example_electrum`] for a complete example.
 //!
 //! [`example_electrum`]: https://github.com/bitcoindevkit/bdk/tree/master/examples/example_electrum
 //! [`SyncResponse`]: bdk_core::spk_client::SyncResponse
 //! [`FullScanResponse`]: bdk_core::spk_client::FullScanResponse
+//! [`AuthProvider`]: electrum_client::config::AuthProvider
 #![cfg_attr(coverage_nightly, feature(coverage_attribute))]
 #![warn(missing_docs)]
 
@@ -24,3 +44,6 @@ pub use bdk_electrum_client::*;
 
 pub use bdk_core;
 pub use electrum_client;
+
+// Re-export commonly used electrum_client config types for convenience
+pub use electrum_client::{Config, ConfigBuilder};