Lelantos SDK

Appearance

@lelantos-org/sdk / advanced / ScanStats

Interface: ScanStats ​

Defined in: @lelantos-org/sdk/dist/sync/scan.d.ts:35

Per-scan tallies, which distinguish a systematic decode failure from an empty result.

Properties ​

clueMismatch ​

ts
clueMismatch: number;

Defined in: @lelantos-org/sdk/dist/sync/scan.d.ts:70

Opens cm under the right epk, but the published clue (R or the bits prefix) is not the clue the plaintext's seed yields for the address its d names. Should be 0 for honest senders.

cmMismatch ​

ts
cmMismatch: number;

Defined in: @lelantos-org/sdk/dist/sync/scan.d.ts:59

Decrypted cleanly but the payload does not open the feed's cm. Should be 0: otherwise the feed serves commitments that do not match their ciphertexts, or a sender built an unspendable output or deposit. See the check in scanNotes.

decodeFailed ​

ts
decodeFailed: number;

Defined in: @lelantos-org/sdk/dist/sync/scan.d.ts:44

The input's epk or clueR is not 32 bytes; or the tag verified and checking the plaintext threw: it is not a NotePayload, its rho is not a canonical field element, or a later check threw. Should be 0.

ephemeralMismatch ​

ts
ephemeralMismatch: number;

Defined in: @lelantos-org/sdk/dist/sync/scan.d.ts:64

Opens cm, but epk is not esk · g_d for the esk the plaintext's seed expands to and the address its d names. Should be 0 for honest senders.

hits ​

ts
hits: number;

Defined in: @lelantos-org/sdk/dist/sync/scan.d.ts:71

notOurs ​

ts
notOurs: number;

Defined in: @lelantos-org/sdk/dist/sync/scan.d.ts:38

ECDH/ChaCha tag mismatch; expected for notes addressed to other keys.

scanned ​

ts
scanned: number;

Defined in: @lelantos-org/sdk/dist/sync/scan.d.ts:36

zeroValue ​

ts
zeroValue: number;

Defined in: @lelantos-org/sdk/dist/sync/scan.d.ts:53

Value-0 notes that decrypt under this key: unspendable, and dropped before the commitment, ephemeral-key and clue checks. The wallet seals none to a held address: a spend's pads and the fee leaf of a deposit that charged no fee go to one-time recipients no one holds, and count as notOurs. A non-zero tally means a sender addressed a value-0 output to this account through the bundle builders or another client.