Solidity security review: trace attack paths and asset impact

Use code, compiler, and deployment context to check common contract risks with reproducible evidence.

Skills

Confirm compiler/pragmas, dependency versions, proxy/upgrade model, role initialization, and protected assets. Trace each external input to state changes or transfers. Check reentrancy, integer/precision issues, signature replay, authorization boundaries, low-level call results, and oracle assumptions. Run project tests and static analysis, adding a local reproducer for each defect. Review storage layout and one-time initialization constraints. State what runtime/economic risks were not covered. Passing static tools is not an audit or safety claim; do not deploy or transact.

Permissions

Prerequisites

For reviewing Solidity access control, reentrancy, arithmetic, external calls, and upgrade risks.
Needs compiler version, locked dependencies, deployment assumptions, and threat/asset model.

Permissions

May inspect/edit contracts and tests and run static analysis/local tests.
Finding no issue is not an audit; do not deploy, upgrade, or transact.

Limitations

Trace reachable attack paths and asset impact; inspect role initialization, external calls, reentrancy guards, and upgrade storage layout; require independent audit.