testnet: reconcile indexed event counts against the RPC source

[Depo-dev]

Nothing currently proves that what Trident indexed matches what the chain actually emitted. Without that check, silent under-indexing is invisible — the API returns a confident, incomplete answer.

Scope

• A reconciliation job comparing indexed event counts per ledger range against RPC.
• Report discrepancies with the specific ledger ranges involved.
• Run it over a meaningful testnet window, not just a handful of ledgers.
• Decide whether it runs continuously or on demand, and document the choice.

Done when

• A reconciliation run over a real window reports zero unexplained discrepancies.

[yustech-alt]

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

I would like to work on this...asign this to me maintener

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

[Miracle656]

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

I’d like to claim this issue. Building an authoritative reconciliation job to verify indexed event counts against raw Soroban RPC ledger responses is critical to detect and eliminate silent under-indexing.

My implementation plan:

Reconciliation Ingestion & Range Chunking: Build a reconciliation service (trident reconcile --from= --to=) that segments a verified ledger window into deterministic chunks (e.g., 500-ledger blocks).

Dual-Source Delta Comparison:

Query the authoritative Soroban RPC getEvents endpoint across each chunk to extract raw emitted event counts per contract and ledger.

Query Trident’s indexed Postgres database for the corresponding count in that exact ledger sequence range.

Calculate exact counts and identify missing/under-indexed ledger sequences.

Operational Cadence & Audit Logging: Structure the worker with dual-mode execution: an on-demand CLI command for ad-hoc range verification and a periodic background cron (e.g., trailing 6-hour checkpoint sweep) to maintain continuous verification without saturating public RPC limits.

Telemetry & Discrepancy Reporting: Log detailed ledger ranges, contract IDs, and missing event counts to a dedicated audit store while exposing a Prometheus gauge trident_indexer_event_count_divergence.

Testnet Verification: Run a verification sweep over a multi-thousand testnet ledger window to assert zero unexplained discrepancies and write unit tests simulating mismatched event counts.

Please assign this to me!

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

[drips-wave]

Congratulations, @Miracle656! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Miracle656: 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 🌊