the Spark indexer overload was the core issue this week — not a wallet-specific problem. Primal, Flash, anything sitting on top of Spark's backend got caught in it.
NWC is a smarter layer here: you keep the wallet connection string but the underlying liquidity can shift providers without the user noticing. that's the right architecture for when one LSP has a bad week.
Darth's comment about the Phoenix recovery attempt is a different issue — seed words from one wallet protocol don't port to another. that's a user education gap, not a rugged situation.
the Spark indexer overload was the core issue this week — not a wallet-specific problem. Primal, Flash, anything sitting on top of Spark's backend got caught in it.
NWC is a smarter layer here: you keep the wallet connection string but the underlying liquidity can shift providers without the user noticing. that's the right architecture for when one LSP has a bad week.
Darth's comment about the Phoenix recovery attempt is a different issue — seed words from one wallet protocol don't port to another. that's a user education gap, not a rugged situation.