64. [QA] Implement dead code detection for Go codebase

[dotandev]

Description
Add a linter to detect and remove unused functions, variables, and constants in the Go project.

Requirements and Context

• Background: Keeps the codebase lean and maintainable.
• Success Criteria (Done):
  • unused linter enabled in golangci-lint.

Suggested Execution

• Fork/Branch: qa/go-dead-code
• Implementation:
  • Update .golangci.yml.
  • Remove any code flagged as unused by the linter.

Test and Commit

• Testing:
  • Run golangci-lint run and verify zero unused code warnings.
• PR Inclusions:
  • Updated config and removal of dead code.

Example Commit Message
chore: enable unused linter and remove dead code

Guidelines

• Must-haves: Ensure non-exported fields intended for future use aren't prematurely deleted.

---

[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

[Manuel1234477]

@Manuel1234477 has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi Can I work on this issue

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

[Georgechisom]

@Georgechisom has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi, I love to work on this issue and deliver an excellent result, pls help assign this issue to me

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

[Obiajulu-gif]

@Obiajulu-gif has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

GM maintainer, I would love to take this because dead code is “silent debt” — it slows reviews, misleads new contributors, and hides the real API surface. I’ll enable the unused linter in golangci-lint via .golangci.yml, run it across the repo, and remove only what’s truly unreachable (unused funcs/vars/consts/types). For anything that looks unused but is intentionally reserved (reflection, build tags, generated wiring, future hooks), I’ll validate the call path and, if needed, preserve it with a minimal, well-justified directive instead of deleting. Then I’ll run golangci-lint run + the full test suite to ensure zero warnings and no behavior regressions.

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

[Mosas2000]

@Mosas2000 has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I'd love to take up this issue of [QA] Implement dead code detection for Go codebase and will be happy to enable the unused linter in .golangci.yml, run it, carefully review & remove genuinely dead code (while preserving any intentionally unused non-exported fields marked for future use), and make sure golangci-lint run ends with zero unused warnings.

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

[Pvsaint]

@Pvsaint has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi, I'm Victor, a software developer, proficient in rust, nextjs, react, typescript, etc.
I'd love to contribute to this project by taking this issue if it's available, ETA 24hrs.

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

[victorisiguzoruzoma874]

@victorisiguzoruzoma874 has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I am a Full Stack Engineer with deep expertise in Next.js, Python, TypeScript, Node.js, Rust, PostgreSQL, JavaScript, and DevOps practices. I have made some meaningful contributions to projects within the Web3 space, with a strong focus on the Stellar ecosystem. Through this experience, I have consistently delivered robust, high-quality solutions and effectively addressed complex technical challenges under strict timelines. My background covers frontend and backend development, smart contract implementation, as well as the optimization and long-term maintenance of scalable systems.

I am fully capable of handling this assignment. Please proceed with the allocation.

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

[EbukaMoses]

@EbukaMoses has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hello Maintainer,

I’d like to apply to work on this issue.

I’m Ebuka Moses, a full-stack and blockchain developer with experience building, testing, and maintaining smart contracts, particularly using Rust and blockchain-based architectures. I’m comfortable working with contract logic, validation, access control, persistent storage, and event handling, and I always pay close attention to correctness, security, and edge cases.

I take time to fully understand the issue requirements before implementing a solution, and I ensure my work follows the project’s coding standards. I also write clear, well-tested code and submit clean pull requests with meaningful commits.

I’m confident I can deliver a solid solution that meets the acceptance criteria and adds value to the project.

Thank you for your consideration, and I look forward to contributing.

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

[drips-wave]

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

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