[RULE] Rule G003: Flag Public Variables in Internal/Abstract Contracts

[mijinummi]

Labels: good-first-issue, gasguard-rules, solidity, gasguard
Difficulty: Easy
Module: rules/g003_abstract_visibility.rs

---

🧠 Concept

Add static rule G003 to flag state variables defined as public within abstract or internal base contracts.

⚠️ Problem

public state variables in abstract contracts auto-generate public getters in every inheriting child contract, swelling deployment bytecode size unnecessarily.

📁 Implementation Scope

• rules/g003_abstract_visibility.rs
• test/fixtures/g003_samples.sol

🛠️ Requirements

1. Detect variable declarations with public visibility inside abstract contract blocks.
2. Suggest changing visibility to internal or private.

🎯 Acceptance Criteria

• Flags public state variables in abstract classes.
• Passes without warnings on internal or private declarations.

[francisprecious061]

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

hello, can i WORK on this issue?, i can fix it.

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

[Thoni76]

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

Hi, please i would love to work on this issues

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

[Leothosine]

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

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

I'm a software engineer with strong experience in JavaScript and building scalable web applications. I'm comfortable working across the stack, writing clean, maintainable code, and collaborating in open source environments.

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

Happy to get started right away if assigned — looking forward to contributing.

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

[drips-wave]

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

🧑‍💻 @Leothosine: 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 @Leothosine as part of the Stellar Wave Program's 7th Wave 🥳

😎 @Leothosine: 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.