[Wave 9] Preserve timestamps for custom scanner adapters

[truthixify]

Problem

scanChainAdapterSource assigns timestamp: 0 to every custom adapter result. scanAll therefore loses ordering and time information for third-party chains.

Done when

• Define the timestamp contract for ChainScannerAdapter.
• Preserve adapter timestamps when supplied.
• Provide a documented fallback for chains without timestamps.
• Add a custom adapter test that verifies ordering and values.

[Morenike20]

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

I’m interested in contributing to this task. I can deliver a clean implementation within the expected timeframe while adhering to the project’s guidelines.

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

[samkiell]

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

hello, i would love to work on this, let me take this off your plate asap.

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

[yustech-alt]

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

Hi, I have gone through the description and I have a good grasp of the expectations. I would be happy to work on this issue if assigned.

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

[hardeyshorlar12]

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

I can solve this please assign it to me

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

[aabolari]

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

i have reviewed the issue and i can handle it i would like to work on this issue

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

[joshuasaleh200-spec]

@joshuasaleh200-spec has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello Maintener, assign me to work on this issue.

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

[aratass]

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

The work for this issue is already done: PR #215 (#215), open against develop.

It adds an optional timestampOf() to ChainScannerAdapter, falls back to a numeric timestamp field on the matched value, and otherwise reports a documented UNKNOWN_TIMESTAMP (0, which is today's behaviour, now named). Non-finite, negative and non-numeric values degrade to UNKNOWN_TIMESTAMP instead of putting NaN on an announcement, and a throwing timestampOf does not abort the scan. Adapters that implement nothing behave exactly as before.

11 new tests in test/scanner/adapter-timestamps.test.ts cover ordering, the fallback, precedence and malformed values. Run the way CI runs it (pnpm 10), the suite goes from 1221 to 1232 passing with zero failures, and format, build and api:check all pass. One CI job hit a flaky memory-ceiling test that I could not reproduce in 10 local runs; details are in the PR.

Apologies for opening the PR before applying here, I had not registered on Drips yet. Happy to change anything in review.

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

[drips-wave]

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

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

[drips-wave]

This issue has been completed by @aratass as part of the Stellar Wave Program's 9th Wave 🥳

😎 @aratass: You earned 400 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.