Verification History Endpoint

[mftee]

Description:

Implement a GET /verify/:hash/history endpoint that retrieves the full on-chain history for a document hash — all Stellar transactions that reference the hash in their memo field.

Requirements:

• Extend StellarClient with get_hash_history(document_hash: &str) -> Result<Vec<TransactionRecord>> where TransactionRecord contains:

  pub struct TransactionRecord {
      pub transaction_id: String,
      pub timestamp: i64,
      pub memo: String,
      pub ledger: u64,
  }

• The Horizon query must paginate through results (limit=200, follow next cursor links if present)
• Sort results chronologically (oldest first)
• Cache the full history with a TTL of 300 seconds
• Return 404 if no transactions are found for the hash

Acceptance Criteria:

• Returns an ordered list of all transactions referencing the hash
• Pagination is followed (not just the first page)
• Cache is used on subsequent requests within TTL
• Unit tests for the sorting and pagination logic

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[KuchiMercy]

@KuchiMercy has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi, I’d like to work on this issue
Kindly assign

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

[drips-wave]

Congratulations, @KuchiMercy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @KuchiMercy: 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 issued 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 @KuchiMercy as part of the Stellar Wave Program's 2nd Wave 🥳

😎 @KuchiMercy: You earned 150 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.