smart-contract-vulnerabilities

To audit a Solidity contract for reentrancy and access control vulnerabilities, review callback-induced stale-state issues, cross-function reentrancy, and unprotected initializers. This process identifies exploit risks and generates a prioritized list of findings with concrete mitigation fixes.

Read-only reentrancy in smart contracts is a stale-state issue where callbacks manipulate external contracts during view function calls. Detect it by tracing callback execution paths and verifying state consistency across contract interactions to ensure accurate data reads.

Check proxy contracts for storage slot collisions and CREATE2 exploitation by analyzing storage layout inheritance and deterministic address deployment patterns. This verifies function selector integrity and prevents unauthorized code execution through collision attacks.

Yes, this skill assesses MEV and flash-loan manipulation risks in DeFi contracts. It evaluates front-running exposure, oracle dependency vulnerabilities, and price manipulation vectors to provide mitigation strategies like TWAP integration and commit-reveal safeguards.

Prevent signature replay attacks in EVM smart contracts by enforcing nonce and chainId validation during signature verification. This ensures cryptographic signatures are bound to specific transactions and cannot be reused across different chains or contract states.

Yes, this security audit covers arithmetic overflow and unchecked block risks across Solidity versions. It evaluates unsafe casting, assembly corner cases, and timelock wrapping within unchecked blocks to identify potential overflow and underflow vulnerabilities.