> ## Content Index > Fetch the complete content index at: https://www.psacramento.com/llms.txt > Use this file to discover other available public pages before exploring further. # SparkStalker: Making Spark-Enabled Wallet Privacy Problems Visible - URL: https://www.psacramento.com/sparkstalker-making-spark-wallet-privacy-problems-visible/ - Published: 2026-04-26T21:13:42.000Z - Updated: 2026-06-18T19:00:28.000Z - Author: pSacramento - Tags: #Import 2026-09-16 06:11 As I [explained in my previous post](https://www.psacramento.com/tether-wallet-lightning-privacy-issues/), I became very concerned after seeing Lightning payments being made publicly visible in [Tether Wallet](https://wallet.tether.io/). The core issue is simple: **people may be using these Lightning wallets for privacy-sensitive payments without realizing that their transactions can be made publicly accessible**. In some cases, this is not just a privacy issue. It can become a real safety risk, especially for people operating in hostile environments. To raise awareness, I built [**SparkStalker**](https://sparkstalker.vercel.app/), a simple tool that allows anyone to view the transactions linked to a [Tether Wallet](https://wallet.tether.io/) by entering its `tether.me` username. [SparkStalkerSee every transaction linked to a tether.me username.![](https://www.psacramento.com/content/images/icon/favicon.ico)](https://sparkstalker.vercel.app/) The goal of the tool is not to encourage surveillance. **The goal is to make the problem visible.** If a human-readable username can expose someone’s transaction history this easily, users need to know. And wallet providers need to fix it. ## A Similar Tool Already Existed Funny detail: only after talking to people on X about the issue did I find out that [René Aaron](https://github.com/reneaaron) had already built a similar tool. His tool, [Spark Address Doxxer](https://reneaaron.github.io/spark-lnaddress-doxxer/), exposes the issue not only for addresses created by [Tether Wallet](https://wallet.tether.io/), but also for [Wallet of Satoshi](https://www.walletofsatoshi.com/). ## Which Wallets Are Affected? I was not aware that [Wallet of Satoshi](https://www.walletofsatoshi.com/) had the same issue, so this was an important new detail that came to light through the discussion. During my own tests, I could also confirm something I had already seen mentioned on X: [Cake Wallet](https://cakewallet.com/), [Blitz Wallet](https://blitzwalletapp.com/), [Breez](https://breez.technology/) and [Primal](https://primal.net/) [all use Spark](https://www.spark.money/ecosystem), but **they are not affected by this problem**. That distinction matters because it suggests that the issue is probably not caused by [Spark](https://www.spark.money/) itself. ## What I Found About the Root Cause After [several exchanges with people on X](https://x.com/w%5Fs%5Fbitcoin/status/2045094018107802060), I came to the conclusion that the most likely cause is a misconfiguration related to existing privacy settings in the [wallet module of the WDK](https://github.com/tetherto/wdk-wallet-spark). [![](https://www.psacramento.com/content/images/2026/04/HGHH-aRWEAAyoBl.jpeg)](https://x.com/BlitzWalletApp/status/2045137528336842928) Source: [X post by Blitz Wallet](https://x.com/BlitzWalletApp/status/2045137528336842928) According to the [Blitz Wallet](https://blitzwalletapp.com/) team, [Spark has allowed users to hide their Bitcoin balance and transaction history from public explorers since November 2025](https://x.com/BlitzWalletApp/status/2045137528336842928). [Seth](https://x.com/sethforprivacy) from [Cake Wallet](https://cakewallet.com/) made a similar point, [saying that it is trivial not to expose users in this way and that Cake Wallet handles this properly](https://x.com/sethforprivacy/status/2045471801380114943?s=20). This is an important point. It suggests that a privacy mode already exists. The problem appears to be that some wallets are NOT changing the default setting, which is **disabled** for privacy mode. ## There Is Already a PR to Fix This [Walter also mentioned](https://x.com/bit%5Fwalt/status/2045204228679795058?s=20) that he had already opened [a pull request in the public WDK repository](https://github.com/tetherto/wdk-wallet-spark/pull/90), asking the Tether team to change the default setting from public to private. [feat: enable Spark privacy mode by default by bitwalt · Pull Request #90 · tetherto/wdk-wallet-sparkCloses #89 Summary Calls wallet.setPrivacyEnabled(true) inside WalletAccountSpark.at() after SparkWallet.initialize() so that newly created wallets hide Bitcoin transactions from block explorers a…![](https://www.psacramento.com/content/images/icon/pinned-octocat-093da3e6fa40.svg)GitHubtetherto![](https://opengraph.githubassets.com/6763084d795490d99731fae197f52afe4b7fda3de3c70dde650c91535cf288b2/tetherto/wdk-wallet-spark/pull/90)](https://github.com/tetherto/wdk-wallet-spark/pull/90) The pull request calls `wallet.setPrivacyEnabled(true)` inside `WalletAccountSpark.at()` after `SparkWallet.initialize()`, so that newly created wallets hide Bitcoin transactions from public explorers by default. From what I can read in the discussion, [there may still be compatibility issues](https://github.com/tetherto/wdk-wallet-spark/pull/90#pullrequestreview-4134752395) that need to be solved before this change can be merged safely. ## Privacy Should Not Be Optional > Yeah, I’ve always been clear that at best this is “VPN-style privacy”, where you trust the operators not to reveal logs. > > WoS did their implementation in a brutally bad way for privacy, we did not, and the default for anyone using Breez (most new Spark implementations it seems)… > > — Seth For Privacy (@sethforprivacy) [March 25, 2026](https://twitter.com/sethforprivacy/status/2036891622412095897?ref%5Fsrc=twsrc%5Etfw) People using Lightning wallets often assume that their payments are not being exposed in a public transaction history tied to a human-readable username. If a wallet makes that assumption false, users deserve to know. Even better, they should not need to know. Privacy should not depend on users discovering and enabling the right setting. **Privacy should be the default.**