Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Write, test, and deploy an ERC-20 (or ERC-721) token contract to a TESTNET (e.g. Sepolia) using Hardhat or Foundry. Build on the audited OpenZeppelin base rather than rolling your own, add one custom rule (e.g. a capped supply or a mint role), and write a thorough test suite covering transfers, approvals/allowances, and the failure cases (insufficient balance, unauthorized mint). Deploy to the testnet, verify the source on the block explorer, and document the gas costs. Never use mainnet or real funds.
Implements the chosen standard correctly on OpenZeppelin; the custom rule works; uses Solidity 0.8+ (no needless SafeMath); require/revert guards inputs.
Thorough tests including approve/transferFrom and failure cases (revert paths); tests pass; meaningful coverage.
Deployed to a testnet (not mainnet); source verified on the explorer; gas costs noted.
Testnet only; no secrets/keys committed; understands deployment is effectively permanent.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A token contract with a full test suite (testnet) ## Goal Write, test, and deploy an ERC-20 (or ERC-721) token contract to a TESTNET (e.g. Sepolia) using Hardhat or Foundry. Build on the audited OpenZeppelin base rather than rolling your own, add one custom rule (e.g. a capped supply or a mint role), and write a thorough test suite covering transfers, approvals/allowances, and the failure cases (insufficient balance, unauthorized mint). Deploy to the testnet, verify the source on the block explorer, and document the gas costs. Never use mainnet or real funds. ## Acceptance criteria - [ ] Correct contract: Implements the chosen standard correctly on OpenZeppelin; the custom rule works; uses Solidity 0.8+ (no needless SafeMath); require/revert guards inputs. - [ ] Testing: Thorough tests including approve/transferFrom and failure cases (revert paths); tests pass; meaningful coverage. - [ ] Deploy & verify: Deployed to a testnet (not mainnet); source verified on the explorer; gas costs noted. - [ ] Safety hygiene: Testnet only; no secrets/keys committed; understands deployment is effectively permanent. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.