Blog or announcement
Blink Weekly Brief
blink.sv · Supports Blink’s Weekly Brief described seed-only recovery and an unswept amount as received
Open original sourceOriginal material
187 distinct source links are cited by the analyses on this site. Multiple line-specific citations may point to the same underlying document.
Blog or announcement
blink.sv · Supports Blink’s Weekly Brief described seed-only recovery and an unswept amount as received
Open original sourceWeb source
blockstream.info · Supports The reviewed CPFP exit requires Bitcoin fee funding outside Spark
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 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 reviewed CPFP exit requires Bitcoin fee funding outside Spark
Open original sourceOfficial documentation
docs.spark.money · Supports A dated Sparkscan sample linked Lightning entries to Spark identities
Open original sourceOfficial documentation
docs.spark.money · Supports Despite an announced Breez SSP, both reviewed SDKs still default only to Lightspark, Flashnet reserves service refusal based on transaction activity, 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 A dated Sparkscan sample linked Lightning entries to Spark identities, 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 A dated Sparkscan sample linked Lightning entries to Spark identities
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 reserves service refusal based on transaction activity
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 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 Spark Operator code includes a wallet-identity kill switch for state-changing actions
Open original sourcePinned source code
github.com · Supports One public participant is enough to expose the full Spark transfer, A public-mode Spark identity exposes exact holdings and raw Bitcoin transaction material
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 The wallet-gate response matches an ordinary identity error
Open original sourcePinned source code
github.com · Supports Breez 0.23 fixes durable exit state, but older wallet integrations do not inherit the fix, Blink advertises non-custody while its source says the app never starts an exit flow
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 Wallet diagnostics can retain or forward complete Spark payment records
Open original sourcePinned source code
github.com · Supports Blink advertises non-custody while its source says the app never starts an exit flow, The reviewed wallets market seed recovery without delivering outage 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, 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 sourcePinned source code
github.com · Supports Spark exit backups must track wallet mutations; a one-time seed backup cannot stay current, The reviewed CPFP exit requires Bitcoin fee funding outside Spark
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 Breez 0.23 fixes durable exit state, but older wallet integrations do not inherit the fix, Blink advertises non-custody while its source says the app never starts an exit flow
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 Blitz preserves exit state but exports the actual recovery outside the wallet
Open original sourcePinned source code
github.com · Supports Blitz gives Flashnet the same Spark identity used with the Operator network
Open original sourcePinned source code
github.com · Supports Blitz preserves exit state but exports the actual recovery outside the wallet
Open original sourcePinned source code
github.com · Supports Blitz gives Flashnet the same Spark identity used with the Operator network
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 The reviewed wallets market seed recovery without delivering outage recovery
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 0.23 fixes the renewed-leaf ancestry omission present in 0.19.0
Open original sourcePinned source code
github.com · Supports Breez cloud sync exposes deterministic record identifiers and omits exit state, Breez 0.23 fixes durable exit state, but older wallet integrations do not inherit the fix
Open original sourcePinned source code
github.com · Supports Breez 0.23 fixes the renewed-leaf ancestry omission present in 0.19.0
Open original sourcePinned source code
github.com · Supports Breez 0.23 fixes durable exit state, but older wallet integrations do not inherit the fix
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 sourcePinned source code
github.com · Supports Breez cloud sync exposes deterministic record identifiers and omits exit state
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 default leaf policy favors payment convenience over unilateral-exit value
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 Wallet diagnostics can retain or forward complete Spark payment records
Open original sourcePinned source code
github.com · Supports One public participant is enough to expose the full Spark transfer, A public-mode Spark identity exposes exact holdings and raw Bitcoin transaction material
Open original sourcePinned source code
github.com · Supports Breez cloud sync exposes deterministic record identifiers and omits exit state
Open original sourcePinned source code
github.com · Supports Restoring the same seed preserves the Spark identity across compatible wallets
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 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 The reviewed wallets market seed recovery without delivering outage recovery
Open original sourcePinned source code
github.com · Supports Wallet diagnostics can retain or forward complete Spark payment records
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 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 cooperative exits, deposits and claims
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 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 Breez builds the exit and checks progress; wallet integration is still required
Open original sourcePinned source code
github.com · Supports Breez builds the exit and checks progress; wallet integration is still required
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, One honest operator cannot invalidate two retained shares and a former-owner key, 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 cooperative exits, deposits and claims
Open original sourcePinned source code
github.com · Supports One honest operator cannot invalidate two retained shares and a former-owner key
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 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 Blitz gives Flashnet the same Spark identity used with the Operator network
Open original sourcePinned source code
github.com · Supports Blitz gives Flashnet the same Spark identity used with the Operator network
Open original sourcePinned source code
github.com · Supports Blitz gives Flashnet the same Spark identity used with the Operator network
Open original sourcePinned source code
github.com · Supports Blitz gives Flashnet the same Spark identity used with the Operator network
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 sourceRepository record
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 wallet-gate response matches 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 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 The wallet-gate response matches 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 cooperative exits, deposits and claims
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 The reviewed Lightning-send path locks selected leaves before requesting payment from the configured SSP
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 The reviewed Lightning-send path locks selected leaves before requesting payment from the configured SSP
Open original sourcePinned source code
github.com · Supports Historical SSP policy bypasses ordinary wallet-privacy checks
Open original sourcePinned source code
github.com · Supports Historical SSP policy relies on an internal network-access boundary
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 Spark's forward security rests on an act of key deletion users cannot verify
Open original sourcePinned source code
github.com · Supports One honest operator cannot invalidate two retained shares and a former-owner key, 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 cooperative exits, deposits and claims
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 sourcePinned source code
github.com · Supports The reviewed wallets market seed recovery without delivering outage recovery
Open original sourcePinned source code
github.com · Supports Spark applies its wallet gate across cooperative exits, deposits and claims
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 sourcePinned source code
github.com · Supports Operators validate an inbound Spark transfer before releasing Lightning-receive preimage shares
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 Blitz’s ‘no third parties’ recovery tool uses Spark’s cooperative-withdrawal path
Open original sourcePinned source code
github.com · Supports Blitz’s ‘no third parties’ recovery tool uses Spark’s cooperative-withdrawal path
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 Operators validate an inbound Spark transfer before releasing Lightning-receive preimage shares
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 Blink advertises non-custody while its source says the app never starts an exit flow
Open original sourcePinned source code
github.com · Supports Blitz preserves exit state but exports the actual recovery outside the wallet
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 sourceRepository record
github.com · Supports Historical SSP policy bypasses ordinary wallet-privacy checks, Historical SSP policy relies on an internal network-access boundary
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 Breez cloud sync exposes deterministic record identifiers and omits exit state
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 reviewed CPFP exit requires Bitcoin fee funding outside Spark
Open original sourcePinned source code
github.com · Supports Breez 0.23 fixes the renewed-leaf ancestry omission present in 0.19.0
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 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 Historical SSP policy bypasses ordinary wallet-privacy checks, A public-mode Spark identity exposes exact holdings and raw Bitcoin transaction material
Open original sourcePinned source code
github.com · Supports Historical SSP policy bypasses ordinary wallet-privacy checks
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 cooperative exits, deposits and claims
Open original sourceCode commit
github.com · Supports Historical SSP policy bypasses ordinary wallet-privacy checks
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 cooperative exits, deposits and claims
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 cooperative exits, deposits and claims
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 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 sourceReproducible audit manifest
Review of Spark's trust model · Supports No complete in-app operatorless exit was found in twelve reviewed products, Breez builds the exit and checks progress; wallet integration is still required, Breez 0.23 fixes durable exit state, but older wallet integrations do not inherit the fix, Cake describes a one-transaction exit, but its reviewed shipped integration did not expose an exit flow, 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, Blink advertises non-custody while its source says the app never starts an exit flow, The reviewed wallets market seed recovery without delivering outage recovery, Blitz preserves exit state but exports the actual recovery outside the wallet
Open original sourceReproducible audit manifest
Review of Spark's trust model · Supports A dated Sparkscan sample linked Lightning entries to Spark identities, One public participant is enough to expose the full Spark transfer, Spark privacy does not cover a globally enumerable token ledger
Open original sourceReproducible audit manifest
Review of Spark's trust model · Supports The default leaf policy favors payment convenience over unilateral-exit value
Open original sourceWeb source
spark.money · Supports Spark's forward security rests on an act of key deletion users cannot verify, One honest operator cannot invalidate two retained shares and a former-owner key
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
support.walletofsatoshi.com · Supports 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