Refactor duplicated attestation repository implementations into one typed repository on the shared base

[Baskarayelu]

📋 Description

There are two parallel attestation repository files: src/repositories/attestationRepository.ts and src/repositories/attestations.repository.ts, while the project standardizes data access on a shared typed base in src/db/repository.ts (BaseRepository) re-exported via src/repositories/index.ts. Two implementations of the same concept drift apart and double the surface for bugs.

This issue consolidates them into a single repository extending BaseRepository, updates all callers, and removes the redundant file.

Why this matters: duplicate repositories are a maintenance trap — a fix applied to one silently misses the other. One typed repository on the shared base is the canonical pattern the rest of the codebase already follows.

🎯 Requirements & Context

Functional requirements

• Pick the canonical attestation repository (extending BaseRepository) and migrate any unique methods from the other into it.
• Update every import site to the consolidated repository (search the whole src tree).
• Delete the redundant file and remove its export from src/repositories/index.ts.
• Preserve all existing query behavior and signatures used by callers (e.g. attestations route/service).
• Ensure existing attestation tests still pass; add a test for any method that lacked coverage after the merge.

Context & constraints

• This is a behavior-preserving refactor; do not change query semantics.
• If the two files actually have divergent behavior, document the difference in the PR and choose the correct one explicitly.

🛠️ Suggested Execution

1. Fork & branch

git checkout -b refactor/consolidate-attestation-repository

2. Implement changes

• Diff the two files; merge into the BaseRepository-derived one; rewire imports; delete the other.
• Add TSDoc on the consolidated repository methods.

3. Test & commit

npm run test -- attestation
npm run lint
npm run build

• Edge cases: callers importing the deleted path, divergent method names, pagination/filter parity.

Example commit message

refactor(db): consolidate duplicate attestation repositories onto BaseRepository

Merges attestations.repository.ts into the canonical attestationRepository
and removes the redundant file.

✅ Acceptance Criteria & Guidelines

Requirement	Target
Single repository on BaseRepository, redundant file removed	Required
All callers updated, behavior preserved	Required
Coverage of merged methods	≥ 95% where testable
npm run lint + npm run build clean	Required
Timeframe	96 hours from assignment

💬 Community & Support

Questions and design discussion — join the GrantFox contributor community on Discord: https://discord.gg/nmnPBkBge

Please comment on this issue to ask to be assigned before you start. 🚀

[brite-side0]

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

Hello maintainer,

I’m a Full Stack Blockchain, Mobile, and Software Engineer with experience building scalable and production ready applications.

I’ve reviewed this particular issue and understand its requirements. If assigned, I’ll begin work immediately, provide regular updates, and deliver a clean, well-tested, and maintainable solution that meets the project’s standards.

Looking forward to contributing.

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

[nice-bills]

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

Hi , I'd like to work on this issue.
I'm a full-stack developer experienced in TypeScript, Rust, and smart contract development across EVM and Soroban/Stellar ecosystems. I've built and shipped production systems covering backend APIs, frontend interfaces (Next.js, React), CI/CD pipelines, and onchain protocols so I'm comfortable working across whatever layer this issue touches.
My approach
I'll start by reproducing the issue locally and reading the surrounding code to understand context and constraints. I'll scope the fix tightly to avoid unnecessary churn, write or update tests to cover the change, and make sure linting, formatting, and existing CI checks all pass before opening a PR. If anything in the issue is ambiguous, I'll flag it early rather than guess.
What you can expect is a single clean PR with a clear description linking back to this issue. Minimal, well-tested changes that follow the project's existing conventions. Fast turnaround, I'm available to start immediately and responsive to review feedback.

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

[Heazzy500]

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

my applications

Hello@ Maintainer, I’ve reviewed the issue description and I’m confident I can work on it effectively. Please assign it to me.

Hi! I’d love to contribute to this issue. It looks interesting and I’d be happy to take it on if it’s still available.

Hello, I’ve gone through the requirements and I’m confident I can implement a proper solution that matches the acceptance criteria. Kindly assign this issue to me.

Hi Maintainer, I’d like to work on this issue. I have experience handling similar tasks and can start immediately.

Hello, I’m interested in working on this issue and would appreciate being assigned to it. Thank you.

Hi there, I carefully reviewed the issue details and I’m confident I can deliver a clean and efficient solution.

Hello Maintainer, I’d love to take ownership of this issue and submit a high-quality pull request once completed.

Hi, I’m a full-stack Web2 & Web3 developer with open-source contribution experience, and I’d be glad to work on this issue.

Hello, this issue aligns well with my skill set and I’m confident I can resolve it properly. Please assign it to me.

Hi Maintainer! I’m interested in contributing to this task and can ensure timely delivery with clean implementation.

Hello, I’ve thoroughly read the issue description and understand the expected outcome. I’d love to work on it.

Want me to clean these up into one stronger template you can reuse?

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

[Caneryy]

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

Hello, I'd like to work on this issue.

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

[drips-wave]

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

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