Source Collection Receipts

This page describes the next source-proof layer for LN Advisor.

Purpose

The current recommendation flow already has:

1. local collection through LNC
2. normalization
3. privacy transform
4. pinned execution metadata
5. signed recommendation binding

The missing piece is authenticated source collection for verified mode.

Current state

Today, some recommendation routes still use a fallback provenance path that hashes the already reduced payload and binds that hash into provenance.

That is useful for local binding.

It is not a source proof.

Planned receipt

The next artifact is source-collection-receipt-v1.

It binds:

1. node pubkey
2. collection time
3. verifier nonce
4. exact RPC set
5. raw snapshot hash
6. normalized snapshot hash
7. privacy-transformed snapshot hash
8. collector version

Trust levels

Local

Browser collected. Privacy preserving. Internal provenance only.

Verified Runtime

Reduced payload plus verified runtime for scoring.

This is the current verified recommendation path.

Verified Source

Collector-signed or enclave-attested source receipt, then reduced payload scoring.

Only this mode should claim authenticated source collection.

Rollout

Step 1

Add a signed collector sidecar next to LND or litd.

The collector should:

1. receive a nonce
2. fetch the RPC set
3. build the raw snapshot
4. normalize it
5. apply feature_only
6. sign the receipt

Step 2

Verify that receipt in the API and bind the receipt hash into provenance.

Step 3

Move the collector into the verified runtime and add attestation metadata.

Step 4

Bind the receipt hash, raw hash, normalized hash, and privacy hash into ARB.

Current repo status

The current codebase has the receipt schema, deterministic builder, structural verifier, and provenance binding helper.

The live recommendation flow is unchanged.