account-validation

Solana account validation enforces owner, discriminator, and account type checks across all instruction handlers to prevent misconfigurations. It is required for consistent security audits of cross-account references and sysvar usage.

Audit Solana instruction handlers by enumerating accounts, documenting ownership, and verifying discriminator checks for each instruction. This identifies and documents all account validation points to ensure consistent security patterns.

Yes, this account validation pattern applies to all instruction handlers, cross-account references, and sysvar usage within Solana audits. It ensures consistent data-matching validation across all program components.

The best way to document account types for a Solana program audit is to enumerate accounts, ownership, and discriminators for every instruction. This creates a repeatable audit pattern satisfying consistent account type inventory requirements.

Yes, you can integrate Solana account validation checks with breadth and depth agent workflows. The validation pattern is designed to be injected into these agents, providing a repeatable audit workflow for Solana programs.

You should not use automated account validation patterns when your Solana program uses non-standard discriminator layouts or custom ownership models that fall outside standard instruction handler, sysvar, and cross-account reference configurations.