[PERF] Refactor Constructor Error Handling to Use Custom Errors

[mijinummi]

Labels: good-first-issue, solidity, gas-saving, gasguard
Difficulty: Easy
Module: contracts/core/

---

🧠 Concept

Replace string revert messages in contract constructors (require(initValue != 0, "Zero init")) with custom error declarations (error ZeroInit()).

⚠️ Problem

Revert strings in constructors permanently inflate deployment bytecode size, increasing contract deployment gas costs on every deployment.

📁 Implementation Scope

• contracts/core/GasGuardFactory.sol
• test/core/GasGuardFactory.test.ts

🛠️ Requirements

1. Define custom error declarations for constructor setup checks.
2. Replace all require(condition, "string") calls in constructors with if (!condition) revert CustomError().

🎯 Acceptance Criteria

• Measurable reduction in contract deployment gas across core factory contracts.
• All deployment tests pass with expected custom error reverts.

[mikevill20]

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

Hello maintainer, please assign this issue to me. Thanks

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

[Ade-Pheebs]

@Ade-Pheebs has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

hi maintainer can you assign me to this issue please?

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

[abdulrcrtw]

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

Hi, I'd like to take this on.

I have hands-on experience with backend development, databases, and API design, as well as frontend work with React and modern CSS. I write tested, maintainable code and enjoy contributing to open source projects.

I understand what's being asked here and I'm confident I can implement this correctly and efficiently.

I'd love the opportunity to work on this — please consider assigning it to me.

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

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@abdulrcrtw's PR #716 was approved and merged by @mijinummi.

🏆 @abdulrcrtw: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (551 total points). Track your full progress on GrantFox.

👏 Great work, @abdulrcrtw! Keep contributing to MDTechLabs.

[drips-wave]

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

😎 @abdulrcrtw: You earned 200 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.