Implement Cross-Venue Timing Correlation to Detect Coordinated Pump-and-Dump Across DEXes

[Inkman007]

Description

Pump-and-dump schemes on the Stellar DEX often involve coordinated buying across multiple venues (SDEX, AMM pools, and sometimes Ethereum DEX) to create the appearance of organic demand before the dump. The existing detection/cross_venue_features.py computes SDEX ↔ AMM coordination features but does not measure timing synchrony across more than two venues. This issue asks you to implement a multi-venue timing correlation detector that identifies wallets executing coordinated trades across 3+ venues within tight time windows.

What needs to be built

• Extend detection/cross_venue_features.py with compute_multi_venue_timing_correlation(wallet_id, venues, window_seconds) that computes a cross-venue synchrony score using the Pearson correlation coefficient of per-venue trade volume time series (binned into 1-second buckets).
• Venues: SDEX order book, AMM pools (each pool is its own venue), and Ethereum DEX (if identity graph has a linked address).
• Add the synchrony score as multi_venue_sync_score feature.
• Emit a structured alert when multi_venue_sync_score > 0.85 via the existing monitoring/alert_dispatcher.py.

Requirements

Functional

• Time series binning must align across venues using UTC epoch seconds.
• Must handle venues with no activity in the window (all-zero time series): treat as uncorrelated, not as division-by-zero error.

Testing

• Unit test: two perfectly synchronised venues (same trade at the same second) must produce correlation = 1.0.
• Unit test: one active venue and one silent venue must produce correlation = 0.0.
• Test: alert fires when sync score exceeds threshold.

Security

• The alert payload must not include raw trade amounts; include only the sync score, time window, and wallet ID hash.

Documentation

• Update docs/cross_venue_detection.md with the multi-venue timing correlation algorithm, the alert threshold rationale, and known limitations (correlation ≠ causation).

Contributor guidance

Area of specialty: Financial data analysis, cross-chain analytics, Python, statistics.

How to contribute:

1. Comment describing your experience with cross-venue or cross-asset correlation analysis.
2. Propose how to handle the case where the Ethereum DEX data has higher latency than Stellar (introducing timing misalignment).
3. PR must include both unit tests and the alert integration.

[paulpeter32-coder]

@paulpeter32-coder has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer I'm a fullstack developer and I would love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @paulpeter32-coder to this issue.

[chiemezie1]

@chiemezie1 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello, I have reviewed the issue and understand what needs to be done.

I would appreciate being assigned to it.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @chiemezie1 to this issue.

[Mitch5000]

@Mitch5000 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Please maintainer... Assign me this issue... I'll resolve it without errors 🙏

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Mitch5000 to this issue.

[Isihaq123]

@Isihaq123 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I wiill like to work on the issue, Assign me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Isihaq123 to this issue.

[adesinavictor272-alt]

@adesinavictor272-alt has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to work on this issue because I have the technical skills and tools to sort out the issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @adesinavictor272-alt to this issue.

[soyaya]

@soyaya has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Can i be assigned to this task ? i will be done at record time.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @soyaya to this issue.

[CAESARIAN-ATHENS]

@Chidubemkingsley has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

PR in seconds. I deliver fast and quality works.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Chidubemkingsley to this issue.

[grantfox-oss]

🦊 GrantFox — @soyaya has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #211)
2. Your PR will be reviewed by the Ledger-Lenz maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

Congratulations, @soyaya! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @soyaya: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊