Web source
Radar App Store
apps.apple.com · Supports Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourceOriginal material
170 distinct source links are cited by the analyses on this site. Multiple line-specific citations may point to the same underlying document.
Web source
apps.apple.com · Supports Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourceBlog or announcement
blink.sv · Supports Blink’s Weekly Brief described seed-only recovery and an unswept amount as received
Open original sourceWeb source
blog.cakewallet.com · Supports Cake describes a one-transaction exit, but its reviewed shipped integration did not expose an exit flow
Open original sourceBlog or announcement
bringin.app · Supports No complete in-app operatorless exit was found in eight reviewed consumer-wallet products, Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourceOfficial documentation
docs.lightspark.com · Supports Grid’s common account model permits a Spark-backed wallet to carry a frozen status that blocks payments
Open original sourceOfficial documentation
docs.spark.money · Supports Spark’s FAQ reduces exit to a pre-signed broadcast; its beta manual documents a multi-stage expert procedure, The documented independent exit cannot start from a Spark balance alone; it needs external on-chain fee funding
Open original sourceOfficial documentation
docs.spark.money · Supports Sparkscan exposes the hidden Spark identity behind Lightning payments
Open original sourceOfficial documentation
docs.spark.money · Supports Despite an announced Breez SSP, both reviewed SDKs still default only to Lightspark, Flashnet—one of three named Spark Operators—reserves compliance-based rejection and fund freezing in its service terms, Spark’s FAQ reduces exit to a pre-signed broadcast; its beta manual documents a multi-stage expert procedure
Open original sourceOfficial documentation
docs.spark.money · Supports Sparkscan exposes the hidden Spark identity behind Lightning payments, Spark privacy does not cover a globally enumerable token ledger
Open original sourceOfficial documentation
docs.spark.money · Supports Spark’s FAQ reduces exit to a pre-signed broadcast; its beta manual documents a multi-stage expert procedure
Open original sourceOfficial documentation
docs.spark.money · Supports Spark's forward security rests on an act of key deletion users cannot verify, Retained Lightspark and Flashnet keys could sign a conflicting spend of a Lightspark-funded Lightning leaf
Open original sourceOfficial documentation
docs.sparkscan.io · Supports Sparkscan exposes the hidden Spark identity behind Lightning payments
Open original sourceBlog or announcement
flashnet.xyz · Supports Retained Lightspark and Flashnet keys could sign a conflicting spend of a Lightspark-funded Lightning leaf
Open original sourceWeb source
flashnet.xyz · Supports Flashnet—one of three named Spark Operators—reserves compliance-based rejection and fund freezing in its service terms
Open original sourceRepository record
github.com · Supports Club Orange bundled lower-level exit code without exposing an app-facing exit operation
Open original sourcePinned source code
github.com · Supports Every Spark Operator receives transfer participants and records—not merely a signing share
Open original sourcePinned source code
github.com · Supports A normal Spark wallet identifies itself separately to every Operator
Open original sourcePinned source code
github.com · Supports Every Spark Operator receives the full Lightning invoice—not merely one secret share
Open original sourcePinned source code
github.com · Supports Every Spark Operator receives the full Lightning invoice—not merely one secret share
Open original sourcePinned source code
github.com · Supports Every Spark Operator receives transfer participants and records—not merely a signing share
Open original sourceRepository record
github.com · Supports Blitz’s ‘no third parties’ recovery tool uses Spark’s cooperative-withdrawal path
Open original sourcePinned source code
github.com · Supports Rotating a Spark deposit address leaves the Operator-side wallet cluster intact
Open original sourcePinned source code
github.com · Supports Spark makes a targeted wallet freeze externally indistinguishable from an ordinary identity error
Open original sourcePinned source code
github.com · Supports Spark’s FAQ reduces exit to a pre-signed broadcast; its beta manual documents a multi-stage expert procedure, One 100,000-sat wallet required 253 ordered packages; 252 failed when submitted together, At 1 sat/vB, 18 of 22 leaves cost more to exit than they held, Blink’s first documented mainnet recovery bundle silently omitted required ancestry, Cake describes a one-transaction exit, but its reviewed shipped integration did not expose an exit flow
Open original sourcePinned source code
github.com · Supports A Spark unilateral exit is a staged recovery procedure, not a single emergency broadcast
Open original sourcePinned source code
github.com · Supports Wallet usage history—not just balance—determines Spark’s exit workload
Open original sourcePinned source code
github.com · Supports Higher fee rates push more Spark leaves below the economic exit threshold
Open original sourcePinned source code
github.com · Supports A Spark destination amount does not disclose the exit’s net economic recovery, Blink’s Weekly Brief described seed-only recovery and an unswept amount as received
Open original sourcePinned source code
github.com · Supports A Spark destination amount does not disclose the exit’s net economic recovery
Open original sourcePinned source code
github.com · Supports Higher fee rates push more Spark leaves below the economic exit threshold
Open original sourcePinned source code
github.com · Supports A Spark destination amount does not disclose the exit’s net economic recovery, Higher fee rates push more Spark leaves below the economic exit threshold
Open original sourceRepository record
github.com · Supports No complete in-app operatorless exit was found in eight reviewed consumer-wallet products
Open original sourcePinned source code
github.com · Supports Spark exit backups must track wallet mutations; a one-time seed backup cannot stay current, The documented independent exit cannot start from a Spark balance alone; it needs external on-chain fee funding
Open original sourcePinned source code
github.com · Supports A Spark unilateral exit is a staged recovery procedure, not a single emergency broadcast
Open original sourcePinned source code
github.com · Supports A seed alone is not an operator-outage recovery backup for Spark, Blink’s Weekly Brief described seed-only recovery and an unswept amount as received
Open original sourcePinned source code
github.com · Supports A seed alone is not an operator-outage recovery backup for Spark
Open original sourcePinned source code
github.com · Supports A Spark unilateral exit is a staged recovery procedure, not a single emergency broadcast, Blink’s Weekly Brief described seed-only recovery and an unswept amount as received
Open original sourcePinned source code
github.com · Supports Wallet usage history—not just balance—determines Spark’s exit workload
Open original sourcePinned source code
github.com · Supports Wallet usage history—not just balance—determines Spark’s exit workload
Open original sourceRepository record
github.com · Supports No complete in-app operatorless exit was found in eight reviewed consumer-wallet products
Open original sourceRepository record
github.com · Supports Blitz’s ‘no third parties’ recovery tool uses Spark’s cooperative-withdrawal path
Open original sourceRepository record
github.com · Supports Blitz’s ‘no third parties’ recovery tool uses Spark’s cooperative-withdrawal path
Open original sourcePinned source code
github.com · Supports Every Spark Operator receives the full Lightning invoice—not merely one secret share
Open original sourcePinned source code
github.com · Supports The referenced server logic for Spark’s default Lightspark SSP is not publicly accessible
Open original sourcePinned source code
github.com · Supports Both reviewed SDKs fix Lightspark SO0 as default coordinator without automatic failover
Open original sourceRepository record
github.com · Supports Blink’s first documented mainnet recovery bundle silently omitted required ancestry
Open original sourcePinned source code
github.com · Supports The referenced server logic for Spark’s default Lightspark SSP is not publicly accessible
Open original sourceRepository record
github.com · Supports Breez 0.19.0 ships no public mobile exit API; its draft API still contacts an operator
Open original sourcePinned source code
github.com · Supports The referenced server logic for Spark’s default Lightspark SSP is not publicly accessible, Despite an announced Breez SSP, both reviewed SDKs still default only to Lightspark
Open original sourcePinned source code
github.com · Supports Breez 0.19.0 can silently omit a required parent and produce an unbroadcastable exit package
Open original sourceRepository record
github.com · Supports Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourceRepository record
github.com · Supports No complete in-app operatorless exit was found in eight reviewed consumer-wallet products, Cake describes a one-transaction exit, but its reviewed shipped integration did not expose an exit flow
Open original sourcePinned source code
github.com · Supports Cake describes a one-transaction exit, but its reviewed shipped integration did not expose an exit flow
Open original sourcePinned source code
github.com · Supports Retained Lightspark and Flashnet keys could sign a conflicting spend of a Lightspark-funded Lightning leaf
Open original sourcePinned source code
github.com · Supports A normal Spark wallet identifies itself separately to every Operator
Open original sourceRepository record
github.com · Supports No complete in-app operatorless exit was found in eight reviewed consumer-wallet products, Club Orange bundled lower-level exit code without exposing an app-facing exit operation
Open original sourcePinned source code
github.com · Supports Lightspark Connect exposes Chainalysis-backed sanctions screening of Lightning nodes
Open original sourcePinned source code
github.com · Supports When enabled, Spark’s targeted wallet gate can be updated live, applied selectively, and reversed
Open original sourcePinned source code
github.com · Supports A normal Spark wallet identifies itself separately to every Operator
Open original sourcePinned source code
github.com · Supports Spark applies its wallet gate across exits, deposits, claims, and privileged-service paths
Open original sourcePinned source code
github.com · Supports One public participant is enough to expose the full Spark transfer
Open original sourcePinned source code
github.com · Supports Breez 0.19.0 ships no public mobile exit API; its draft API still contacts an operator
Open original sourcePinned source code
github.com · Supports The referenced server logic for Spark’s default Lightspark SSP is not publicly accessible
Open original sourcePinned source code
github.com · Supports The referenced server logic for Spark’s default Lightspark SSP is not publicly accessible
Open original sourcePinned source code
github.com · Supports Lightspark's default SSP binds invoices and Bitcoin destinations to the Operator-layer wallet identity, Spark's published 2-of-3 setting means one honest Operator cannot veto two retained shares, Retained Lightspark and Flashnet keys could sign a conflicting spend of a Lightspark-funded Lightning leaf
Open original sourcePinned source code
github.com · Supports Both reviewed SDKs fix Lightspark SO0 as default coordinator without automatic failover
Open original sourcePinned source code
github.com · Supports Spark applies its wallet gate across exits, deposits, claims, and privileged-service paths
Open original sourcePinned source code
github.com · Supports Spark's published 2-of-3 setting means one honest Operator cannot veto two retained shares
Open original sourcePinned source code
github.com · Supports The referenced server logic for Spark’s default Lightspark SSP is not publicly accessible
Open original sourcePinned source code
github.com · Supports Spark privacy does not cover a globally enumerable token ledger
Open original sourcePinned source code
github.com · Supports Spark's forward security rests on an act of key deletion users cannot verify
Open original sourceRepository record
github.com · Supports Breez 0.19.0 can silently omit a required parent and produce an unbroadcastable exit package
Open original sourcePinned source code
github.com · Supports One public participant is enough to expose the full Spark transfer, Lightspark's default SSP binds invoices and Bitcoin destinations to the Operator-layer wallet identity, Retained Lightspark and Flashnet keys could sign a conflicting spend of a Lightspark-funded Lightning leaf
Open original sourcePinned source code
github.com · Supports Spark privacy does not cover a globally enumerable token ledger
Open original sourcePinned source code
github.com · Supports Lightspark’s Grid contract expressly permits sanctions-based refusal, reversal, and freezing
Open original sourcePinned source code
github.com · Supports Grid’s contract puts compliance judgment, transaction execution, and suspension in Lightspark’s hands
Open original sourcePinned source code
github.com · Supports Lightspark says Grid integrates sanctions checks into transactions and blocks illicit transfers by default
Open original sourcePinned source code
github.com · Supports A normal Spark wallet identifies itself separately to every Operator
Open original sourcePinned source code
github.com · Supports Rotating a Spark deposit address leaves the Operator-side wallet cluster intact
Open original sourcePinned source code
github.com · Supports Rotating a Spark deposit address leaves the Operator-side wallet cluster intact
Open original sourcePinned source code
github.com · Supports Spark makes a targeted wallet freeze externally indistinguishable from an ordinary identity error
Open original sourcePinned source code
github.com · Supports Grid’s common account model permits a Spark-backed wallet to carry a frozen status that blocks payments
Open original sourcePinned source code
github.com · Supports Grid’s common account model permits a Spark-backed wallet to carry a frozen status that blocks payments
Open original sourcePinned source code
github.com · Supports Grid’s common account model permits a Spark-backed wallet to carry a frozen status that blocks payments
Open original sourceRepository record
github.com · Supports Breez 0.19.0 ships no public mobile exit API; its draft API still contacts an operator, Cake describes a one-transaction exit, but its reviewed shipped integration did not expose an exit flow
Open original sourcePinned source code
github.com · Supports Both reviewed SDKs fix Lightspark SO0 as default coordinator without automatic failover
Open original sourcePinned source code
github.com · Supports Spark makes a targeted wallet freeze externally indistinguishable from an ordinary identity error
Open original sourcePinned source code
github.com · Supports Spark Operator code includes a wallet-identity kill switch for state-changing actions
Open original sourcePinned source code
github.com · Supports Spark applies its wallet gate across exits, deposits, claims, and privileged-service paths
Open original sourcePinned source code
github.com · Supports Every Spark Operator receives transfer participants and records—not merely a signing share
Open original sourcePinned source code
github.com · Supports One public participant is enough to expose the full Spark transfer
Open original sourcePinned source code
github.com · Supports Spark gives Lightspark's SSP explicit cross-wallet privacy-bypass paths
Open original sourcePinned source code
github.com · Supports When enabled, Spark’s targeted wallet gate can be updated live, applied selectively, and reversed
Open original sourcePinned source code
github.com · Supports One public participant is enough to expose the full Spark transfer
Open original sourcePinned source code
github.com · Supports Breez’s default mobile persistence does not retain the tree needed for an outage exit
Open original sourcePinned source code
github.com · Supports Spark's forward security rests on an act of key deletion users cannot verify
Open original sourcePinned source code
github.com · Supports Spark's published 2-of-3 setting means one honest Operator cannot veto two retained shares, Retained Lightspark and Flashnet keys could sign a conflicting spend of a Lightspark-funded Lightning leaf
Open original sourcePinned source code
github.com · Supports Lightspark's default SSP binds invoices and Bitcoin destinations to the Operator-layer wallet identity
Open original sourcePinned source code
github.com · Supports Spark's forward security rests on an act of key deletion users cannot verify
Open original sourcePinned source code
github.com · Supports Spark applies its wallet gate across exits, deposits, claims, and privileged-service paths
Open original sourceCode commit
github.com · Supports Spark Operator code includes a wallet-identity kill switch for state-changing actions
Open original sourcePinned source code
github.com · Supports Every Spark Operator receives the full Lightning invoice—not merely one secret share
Open original sourcePinned source code
github.com · Supports Every Spark Operator receives transfer participants and records—not merely a signing share
Open original sourcePinned source code
github.com · Supports A normal Spark wallet identifies itself separately to every Operator
Open original sourcePinned source code
github.com · Supports Spark’s preimage-share consensus path enforces the wallet gate for SSP and LNURL callers
Open original sourceRepository record
github.com · Supports No complete in-app operatorless exit was found in eight reviewed consumer-wallet products, Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourcePinned source code
github.com · Supports Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourcePinned source code
github.com · Supports Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourceRepository record
github.com · Supports No complete in-app operatorless exit was found in eight reviewed consumer-wallet products, Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourcePinned source code
github.com · Supports Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourcePinned source code
github.com · Supports Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourcePinned source code
github.com · Supports Spark applies its wallet gate across exits, deposits, claims, and privileged-service paths
Open original sourcePinned source code
github.com · Supports A normal Spark wallet identifies itself separately to every Operator
Open original sourcePinned source code
github.com · Supports A public-mode Spark identity exposes exact holdings and raw Bitcoin transaction material
Open original sourcePinned source code
github.com · Supports The referenced server logic for Spark’s default Lightspark SSP is not publicly accessible
Open original sourcePinned source code
github.com · Supports One public participant is enough to expose the full Spark transfer
Open original sourceRepository record
github.com · Supports Breez 0.19.0 ships no public mobile exit API; its draft API still contacts an operator
Open original sourceRepository record
github.com · Supports No complete in-app operatorless exit was found in eight reviewed consumer-wallet products, Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourcePinned source code
github.com · Supports Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourcePinned source code
github.com · Supports Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourceRepository record
github.com · Supports No complete in-app operatorless exit was found in eight reviewed consumer-wallet products, Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourcePinned source code
github.com · Supports Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourcePinned source code
github.com · Supports Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourcePinned source code
github.com · Supports Spark Operator code can stop a pending SSP-funded incoming transfer before wallet credit
Open original sourcePinned source code
github.com · Supports Retained Lightspark and Flashnet keys could sign a conflicting spend of a Lightspark-funded Lightning leaf
Open original sourceReferenced non-public implementation
github.com · Supports The referenced server logic for Spark’s default Lightspark SSP is not publicly accessible
Open original sourcePinned source code
github.com · Supports A normal Spark wallet identifies itself separately to every Operator
Open original sourcePinned source code
github.com · Supports A public-mode Spark identity exposes exact holdings and raw Bitcoin transaction material
Open original sourcePinned source code
github.com · Supports Lightspark Connect exposes Chainalysis-backed sanctions screening of Lightning nodes
Open original sourcePinned source code
github.com · Supports Lightspark’s Grid contract expressly permits sanctions-based refusal, reversal, and freezing
Open original sourcePinned source code
github.com · Supports Retained Lightspark and Flashnet keys could sign a conflicting spend of a Lightspark-funded Lightning leaf
Open original sourcePinned source code
github.com · Supports Spark’s mainnet CLI generates packages but leaves signing, ordered broadcast, timelocks, and sweeping to the user
Open original sourcePinned source code
github.com · Supports The documented independent exit cannot start from a Spark balance alone; it needs external on-chain fee funding
Open original sourcePinned source code
github.com · Supports Breez 0.19.0 can silently omit a required parent and produce an unbroadcastable exit package
Open original sourcePinned source code
github.com · Supports Despite an announced Breez SSP, both reviewed SDKs still default only to Lightspark
Open original sourcePinned source code
github.com · Supports The referenced server logic for Spark’s default Lightspark SSP is not publicly accessible
Open original sourcePinned source code
github.com · Supports Breez’s default mobile persistence does not retain the tree needed for an outage exit
Open original sourcePinned source code
github.com · Supports Lightspark's default SSP binds invoices and Bitcoin destinations to the Operator-layer wallet identity
Open original sourcePinned source code
github.com · Supports Lightspark's default SSP binds invoices and Bitcoin destinations to the Operator-layer wallet identity
Open original sourcePinned source code
github.com · Supports Lightspark's default SSP binds invoices and Bitcoin destinations to the Operator-layer wallet identity
Open original sourcePinned source code
github.com · Supports Lightspark's default SSP binds invoices and Bitcoin destinations to the Operator-layer wallet identity
Open original sourcePinned source code
github.com · Supports Spark gives Lightspark's SSP explicit cross-wallet privacy-bypass paths, A public-mode Spark identity exposes exact holdings and raw Bitcoin transaction material
Open original sourcePinned source code
github.com · Supports Spark gives Lightspark's SSP explicit cross-wallet privacy-bypass paths
Open original sourcePinned source code
github.com · Supports Lightspark's default SSP binds invoices and Bitcoin destinations to the Operator-layer wallet identity
Open original sourcePinned source code
github.com · Supports Spark applies its wallet gate across exits, deposits, claims, and privileged-service paths
Open original sourceCode commit
github.com · Supports Spark gives Lightspark's SSP explicit cross-wallet privacy-bypass paths
Open original sourcePinned source code
github.com · Supports Rotating a Spark deposit address leaves the Operator-side wallet cluster intact
Open original sourcePinned source code
github.com · Supports Spark applies its wallet gate across exits, deposits, claims, and privileged-service paths
Open original sourcePinned source code
github.com · Supports Every Spark Operator receives the full Lightning invoice—not merely one secret share
Open original sourcePinned source code
github.com · Supports When enabled, Spark’s targeted wallet gate can be updated live, applied selectively, and reversed
Open original sourcePinned source code
github.com · Supports Spark privacy does not cover a globally enumerable token ledger
Open original sourcePinned source code
github.com · Supports Spark applies its wallet gate across exits, deposits, claims, and privileged-service paths
Open original sourcePinned source code
github.com · Supports A public-mode Spark identity exposes exact holdings and raw Bitcoin transaction material
Open original sourcePinned source code
github.com · Supports Spark privacy does not cover a globally enumerable token ledger
Open original sourcePinned source code
github.com · Supports Lightspark's default SSP binds invoices and Bitcoin destinations to the Operator-layer wallet identity
Open original sourcePinned source code
github.com · Supports A normal Spark wallet identifies itself separately to every Operator
Open original sourcePinned source code
github.com · Supports Every Spark Operator receives the full Lightning invoice—not merely one secret share
Open original sourcePinned source code
github.com · Supports Breez’s default mobile persistence does not retain the tree needed for an outage exit
Open original sourceBlog or announcement
lightspark.com · Supports Despite an announced Breez SSP, both reviewed SDKs still default only to Lightspark
Open original sourceWeb source
lightspark.com · Supports Lightspark says it handles sanctions screening for account products built on Spark wallets
Open original sourceWeb source
lightspark.com · Supports Lightspark says Grid integrates sanctions checks into transactions and blocks illicit transfers by default
Open original sourceBlog or announcement
lightspark.com · Supports The referenced server logic for Spark’s default Lightspark SSP is not publicly accessible
Open original sourceOn-chain transaction
mempool.space · Supports The documented independent exit cannot start from a Spark balance alone; it needs external on-chain fee funding
Open original sourceWeb source
play.google.com · Supports Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourceReproducible audit manifest
Review of Spark's trust model · Supports No complete in-app operatorless exit was found in eight reviewed consumer-wallet products, Club Orange bundled lower-level exit code without exposing an app-facing exit operation, Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourceReproducible audit manifest
Review of Spark's trust model · Supports Sparkscan exposes the hidden Spark identity behind Lightning payments, One public participant is enough to expose the full Spark transfer, Spark privacy does not cover a globally enumerable token ledger
Open original sourceWeb source
spark.money · Supports Spark's forward security rests on an act of key deletion users cannot verify, Spark's published 2-of-3 setting means one honest Operator cannot veto two retained shares
Open original sourceWeb source
static1.squarespace.com · Supports Retained Lightspark and Flashnet keys could sign a conflicting spend of a Lightspark-funded Lightning leaf
Open original sourceWeb source
walletofsatoshi.com · Supports No complete in-app operatorless exit was found in eight reviewed consumer-wallet products, Across Primal, Radar, Wallet of Satoshi, and Bringin, control claims were not matched by a demonstrated unilateral-exit path
Open original sourceArchived web source
web.archive.org · Supports Lightspark Connect exposes Chainalysis-backed sanctions screening of Lightning nodes
Open original source