Develop, Audit, and Deploy Secure Smart Contracts

Acts as an autonomous Blockchain Developer that carries a project through six stages: requirements analysis (parsing specs, choosing a network such as Ethereum, Polygon, or BSC, selecting standards like ERC-20, ERC-721, or ERC-1155, mapping contract architecture), smart contract development (gas-optimized Solidity following OpenZeppelin and proxy patterns, with NatSpec documentation), security implementation (reentrancy guards, overflow/underflow protection, validated external calls, emergency pause mechanisms, time locks, checks-effects-interactions ordering), testing and validation (unit tests in Hardhat/Foundry, multi-contract integration tests, gas optimization analysis, static analysis via Slither/MythX, fuzz testing for edge cases), frontend integration (ethers.js or web3.js, MetaMask/WalletConnect wallet connection, real-time blockchain data UI, transaction status monitoring, event listening), and deployment and documentation (deployment scripts with verification, ABI generation, function documentation, user guides, monitoring and alerting setup). Output follows a fixed structure: Smart Contract Code, a Test Suite, Frontend Integration code, and a Deployment Report covering network, contract address, gas used, verification status, and a security-audit summary.

Use it when a task needs Solidity smart-contract work end to end - from choosing the chain and token standard through writing gas-optimized, audit-ready code, testing it, wiring a Web3 frontend, and producing a deployment report - especially when security controls like reentrancy guards, the checks-effects-interactions pattern, time locks, and emergency pause need to be built in from the start rather than added after the fact.

Input is a project specification describing the desired blockchain functionality. Output is Solidity contract code (OpenZeppelin-based, with NatSpec documentation), a Hardhat/Foundry test suite, ethers.js/web3.js frontend integration code, and a deployment report with the contract address formatted as [0x...] and verification status recorded as Verified or Pending.

Built around Solidity ^0.8.19, OpenZeppelin contracts (ReentrancyGuard, Ownable, and other security primitives), Hardhat and Foundry for testing, Slither and MythX for static analysis, ethers.js and web3.js for frontend Web3 integration, and MetaMask/WalletConnect for wallet connection.

For teams building smart contracts and Web3 applications who want security controls applied by default rather than left to a later audit pass: a checklist covering reentrancy, overflow/underflow, access control, validated external calls, emergency mechanisms, input validation, checks-effects-interactions ordering, time-based vulnerabilities, front-running, and gas-limit attacks, plus code-quality standards - consistent naming conventions, cyclomatic complexity below 10 per function, single-responsibility contract design, OpenZeppelin over custom implementations, and semantic versioning. It targets a minimum 95% test coverage with edge-case validation.

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.19;

import "@openzeppelin/contracts/security/ReentrancyGuard.sol";
import "@openzeppelin/contracts/access/Ownable.sol";

/**
 * @title ContractName
 * @dev Brief description of contract functionality
 */
contract ContractName is ReentrancyGuard, Ownable {
    // Contract implementation
}