Both reviewed default SDKs still expose one Lightspark SSP after an announced Breez SSP

What the evidence shows

Technical and product details

1. Documented behavior

   Spark's FAQ says anyone can become an SSP and its goal is to maximize SSP diversity and redundancy. Lightspark is identified as the first. 1

   Supporting material shown on this page

   Spark FAQOfficial documentation · docs.spark.money · checked 2026-07-14
2. Documented behavior

   Lightspark announced in May 2025 that Breez would operate an SSP alongside Lightspark. Current Spark and Breez configurations nevertheless expose the same single Lightspark URL and identity key; current published package artifacts preserve that configuration. 234

   Supporting material shown on this page

   Breez SSP announcementBlog or announcement · lightspark.com · checked 2026-07-14

   Spark SSP configurationPinned source code · github.com · checked 2026-07-14

   23    SSP: "http://127.0.0.1:5000",
   24    ELECTRS: "http://127.0.0.1:30000",
   25  },
   26  REGTEST: {
   27    PROD: {
   28      SSP: "https://api.lightspark.com",
   29      ELECTRS: "https://regtest-mempool.us-west-2.sparkinfra.net/api",

   Breez SSP configurationPinned source code · github.com · checked 2026-07-14

   54            Network::Mainnet => Self {
   55                network,
   56                operator_pool: Self::default_operator_pool_config(network),
   57                reconnect_interval_seconds: 1,
   58                service_provider_config: Self::create_service_provider_config(
   59                    "https://api.lightspark.com",
   60                    "023e33e2920326f64ea31058d44777442d97d7d5cbfcf54e3060bc1695e5261c93",

Scope control

What this does not establish

• This proves public/default concentration, not exclusivity. A private or custom SSP may exist, and integrators can override the configuration. An independent open-ssp implementation exists, with reported regtest CI and an operator fork. Existing-mainnet admission, compatibility, liquidity and automatic fallback were not demonstrated. The default provider is not the only theoretically possible provider. 1345

Sources and excerpts

Primary sources

The relevant details and available source-code excerpts appear alongside the claims above. This list preserves the complete original-source trail for independent verification.