verify-addresses

You can verify new blockchain addresses in a pull request by scanning the codebase changes to detect addresses across TypeScript and JSON files, classify them as EOAs or contracts, and surface role mismatches with actionable recommendations.

You can check if an on-chain address is an EOA or a smart contract by running a validation process that analyzes the address format, infers its type, and optionally uses cast to verify contract interfaces and expected behaviors.

Yes, you can validate blockchain address roles in uncommitted code changes by running a scan command that detects newly added addresses and verifies their correct on-chain roles before committing.

The best way to automate blockchain address validation for PR reviews is to use a context-aware validation tool that detects new addresses across TypeScript and JSON files, distinguishes deployers, governors, and token contracts, and provides actionable mismatch recommendations.

You need to verify contract addresses with cast during code review to optionally check contract interfaces on-chain, ensuring that the deployed contracts expose the expected methods and behaviors for their intended roles.