Problem
The repository contains Stellar, EVM bridge, and Solana ingestion components, but there is no unified event-time pipeline that can reliably correlate activity across finality models and detect wash cycles that traverse chains. Naive address or timestamp matching would create false links and fail under reorgs, delayed bridge settlement, or duplicated provider events.
Scope
- Define a canonical cross-chain event envelope with chain ID, block/ledger identity, event time, observed time, finality state, transaction/log identity, asset identity, and provenance.
- Implement idempotent ingestion and reorg compensation for EVM/Solana while preserving Stellar checkpoint semantics.
- Normalize wrapped/bridged assets through an explicitly versioned asset registry.
- Produce confidence-scored wallet/transfer links using verifiable bridge evidence; never treat heuristic identity as fact.
- Add event-time windows, watermarks, late-arrival handling, and bounded state for multi-hop cycle detection.
- Feed cross-chain features into shadow scoring before production weighting.
Acceptance criteria
- Duplicate delivery and provider failover do not duplicate features.
- Reorged events are retracted and affected correlations/scores are recomputed or invalidated.
- Every link exposes evidence, confidence, and provenance.
- Tests cover delayed finality, reorgs, clock skew, bridge retries, asset-decimal mismatch, and incomplete paths.
- Offline evaluation reports false-link rate and detection lift.
- Operational metrics expose lag, watermark, unresolved assets, retractions, and state size.
Problem
The repository contains Stellar, EVM bridge, and Solana ingestion components, but there is no unified event-time pipeline that can reliably correlate activity across finality models and detect wash cycles that traverse chains. Naive address or timestamp matching would create false links and fail under reorgs, delayed bridge settlement, or duplicated provider events.
Scope
Acceptance criteria