Diego Bale

@dbale_arg

Solhint Tech lead - The Solidity Linter 20+ yrs as Software dev 7+ yrs Smart Contracts dev Protocols design, Architecture, Security, Audits and more

Buenos Aires, Argentina

npmjs.com/package/solhint

Joined March 2026

Following

Followers

Replies Media

Pinned
Diego Bale
@dbale_arg
Mar 23
Smart contract bugs can be prevented🤓 Solhint supports • External plugins • Scoped shareable configs Audit findings into rules. That’s @protofire magic Are you using Solhint ? Book an audit: calendly.com/vitaliy-cherno… @PatrickAlphaC @austingriffith @dabit3 @Santiag68392330
Diego Bale
@dbale_arg
Aug 13
Is your custom modifier before or after public? Erratic order slows reviewers down. Solhint's visibility-modifier-order rule keeps every signature uniform. #Solidity → github.com/protofire/solh… @OpenZeppelin @dabit3 @hardhat @austingriffith
solhint/docs/rules/order/visibility-modifier-order.md at master · protofire/solhint
From github.com
Diego Bale
@dbale_arg
Aug 9
Contracts with too many state variables turn into storage monoliths. Solhint's max-states-count rule prompts you to split before reviews get unmanageable. #Solidity → github.com/protofire/solh… @dabit3 @hardhat @austingriffith
solhint/docs/rules/best-practices/max-states-count.md at master · protofire/solhint
From github.com
Diego Bale
@dbale_arg
Aug 5
Foundry tests should use vm.getBlockTimestamp() and vm.getBlockNumber(), not block.timestamp / block.number. Solhint's foundry-no-block-time-number rule enforces it. #DevTools → github.com/protofire/solh… @OpenZeppelin @foundry_rs @SolidityLang
solhint/docs/rules/miscellaneous/foundry-no-block-time-number.md at master · protofire/solhint
From github.com
Diego Bale
@dbale_arg
Aug 4
Dead variables clutter diffs, mislead reviewers, and hide real bugs. Solhint's no-unused-vars rule removes every ghost declaration before review. #CodeQuality → github.com/protofire/solh… @hardhat @PaulRBerg
solhint/docs/rules/best-practices/no-unused-vars.md at master · protofire/solhint
From github.com