spark.exposed

Centralization

Lightspark Connect exposes Chainalysis-backed sanctions screening for Lightning nodes

The pinned Connect SDK exposes a configurable Lightning-node sanctions-screening operation and identifies Chainalysis as a provider. This is a Connect capability; it does not establish production screening or a call from the Spark SSP. 123

3 sourcesEvidence reviewed through September 11, 2026

Content checked against the September 11 source audit. Historical measurements and product searches retain their stated dates; deployed configuration and later releases are not independently attested.

What the evidence shows

Technical and product details

  1. Documented behavior

    The official Connect SDK exposes screenNode for sanctions screening of a Lightning node and requires a valid API token for the selected compliance provider. The reviewed provider enum includes CHAINALYSIS. 12

    Supporting material shown on this page

    screenNodePinned source code · github.com · checked 2026-07-14
    Relevant lines from the pinned source · open raw file
    1398   * @param complianceProvider The provider that you want to use to perform the screening. You must have a valid
1399   *     API token for the provider set in your Lightspark account settings.
1400   * @param nodePubKey The public key of the node that needs to be screened.
1401   * @returns A RiskRating for the node.
1402   */
1403  public async screenNode(
1404    complianceProvider: ComplianceProvider,
    ComplianceProviderPinned source code · github.com · checked 2026-07-14
    Relevant lines from the pinned source · open raw file
    3/** This is an enum identifying a type of compliance provider. **/
4export enum ComplianceProvider {
5  /**
6   * This is an enum value that represents values that could be added in the future.
7   * Clients should support unknown values as more of them could be added without notice.
  2. Documented behavior

    The originally cited archived Connect guide was reported to describe recipient-node screening. The September fetch returned a documentation shell, so its detailed historical text was not independently recovered in this review. The pinned SDK remains the direct evidence for the configurable operation. 23

    Supporting material shown on this page

    ComplianceProviderPinned source code · github.com · checked 2026-07-14
    Relevant lines from the pinned source · open raw file
    3/** This is an enum identifying a type of compliance provider. **/
4export enum ComplianceProvider {
5  /**
6   * This is an enum value that represents values that could be added in the future.
7   * Clients should support unknown values as more of them could be added without notice.

Interpretation

Why this matters for Spark's trust model

The SDK provides a configurable counterparty-screening operation in an adjacent Lightspark product. Whether that operation is used by the Spark SSP requires a separate, evidenced call path. 123

This section states the trust-model consequence of the cited evidence. Conditional or inferred claims remain bounded by the next section.

Scope control

What this does not establish

  • This establishes a configurable Connect capability, not mandatory or default screening of every Connect payment and not a public call from the Spark SSP to Connect's screenNode mutation. 123

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.

1

screenNode

Pinned source code · github.com · Pinned or archival · checked 2026-07-14

Open original source
2

ComplianceProvider

Pinned source code · github.com · Pinned or archival · checked 2026-07-14

Open original source
3

archived official Lightspark Chainalysis guide

Archived web source · web.archive.org · Pinned or archival · checked 2026-07-14

Open original source

How sources, absence findings, and limitations were evaluated