IMD WORKPROOF — Autonomous AI Agent Work and Payment Protocol

Build a tokenless, non-custodial Solidity job escrow system integrated with real IdentityMD agent identities and verifiable work attestations.

Reference implementation: https://github.com/skinny1-code/stonk-intern-work

Create new contracts without modifying the reference repository.

Core requirements:

1. Allow customers to fund jobs using approved ERC-20 tokens.
2. Record immutable job requirements, agent identity, payment amount, deadlines and acceptance conditions.
3. Integrate actual IMD agent identity and oracle interfaces. Verify deployed addresses and signatures rather than assuming compatibility.
4. Allow authorized agents to submit cryptographically committed work results.
5. Require independent verification of completion before payment. Reject forged signatures, invalid identities and replayed attestations.
6. Distribute 95% to the authorized worker payout wallet and 5% to the protocol fee recipient on successful settlement.
7. Refund failed or expired jobs according to transparent, enforced rules. No protocol fee on fully refunded jobs.
8. Prevent unauthorized withdrawals, double payments, self-verification and reentrancy.
9. Include a 24-hour dispute window and restrict job deadlines to 1–30 days.
10. Build a mobile-friendly interface showing jobs, genuine IMD agents, escrow balances, verification records and settlement receipts.

Deliverables: Complete Solidity source, Foundry tests, adversarial tests, ABI files, deployment manifests, working frontend and an end-to-end demonstration.

Use a contracts-only launch without a token or liquidity pool. Verify compatibility with IMD's actual on-chain systems. Report unavailable integrations as blockers rather than fabricating functionality.

The application must never require customers to disclose wallet private keys.

Upgrades and pausing: Upgradeable and owner can pause

Outside services and values: IMD WorkProof external integrations and deployment requirements: Target network: Ethereum Sepolia testnet, chain ID 11155111, for initial development and security testing. Do not deploy to Ethereum mainnet until the complete system passes security review. IMD identity contracts (Sepolia): - ERC-8004 agent adapter: 0x7621630cb63a73a194f45a3e6801b8c6a7ec2f92 - IdentityRegistry: 0x8004a81dsbfb912233c491871b3d84c89a494bd9e - ReputationRegistry: 0x8004b663056a597dffe9eccc1965a193b7388713 Verify actual deployed bytecode and supported interfaces before relying on these contracts. Payment token for testnet: 0x44a1cd38474fb1748400e7deb5f8d786cce3f89a Use this freely mintable IMD test token for demonstration only. The escrow must accept approved ERC-20 tokens and measure the actual amount received. No new project token or liquidity pool. Oracle verification: Integrate IdentityMD Oracle v2 through https://api.imd.fun. Use EIP-712 domain name "IdentityMD Oracle", version "2", with the correct chain ID and consumer contract address. Verify the current authorized signer from IMD's live API and genuine signed attestations before deployment. Never invent or hardcode an unverified signer. Require a job-specific question hash, authenticated request ID, valid signature, adequate panel quorum and agreement, unexpired answer, correct result commitment and replay protection. If authentic IMD oracle attestations cannot be obtained and validated on Sepolia, stop settlement and report the integration blocker. Never substitute simulated verification for real verification. Economic parameters: - Worker payout: 95% of successful job payment. - Protocol fee: 5%. - Job duration: 1–30 days. - Dispute period: 24 hours. - Full refund on qualifying failed or expired uncompleted jobs, with no protocol fee. - No double settlement, unauthorized withdrawal or self-verification. Authorization: The deployment owner must be the connected user's authorized wallet. Worker payout addresses must be independently authenticated. The authorized owner controls protocol configuration but cannot arbitrarily withdraw client escrow funds. Deliverables: Functional Solidity contracts, Foundry tests, adversarial security tests, verified external interfaces, deployment manifest, ABI files, source repository, and reproducible testnet transaction receipts. No Chainlink VRF, third-party paid API subscription, new token, liquidity pool or unrelated external dependencies are required. Do not deploy to mainnet or claim real revenue from testnet transactions.