ZK-Atomic Swap Engine Development

SOVEREIGN ZK-ATOMIC SWAP IMMUTABLE GROTH16 PRIVACY-SWAP ENGINE FOR TRUSTLESS OTC EXCHANGE Project Details Research Focus: Improving Proof of Work (PoW) efficiency and cross-chain confidentiality via zk-SNARKs. The Groundfloor Opportunity: This project represents a unique opportunity to lead the research and implementation of ZK-SNARKs on a nascent PoW chain. We are aiming to achieve what Zcash did for privacy and what Bitcoin Cash sought for utility, but at a "Groundfloor" level on a Sovereign EVM. As a lead architect, you will not just be coding; you will be officially improving the Bitnet Money blockchain's privacy infrastructure, establishing a reference standard for trustless OTC exchange before the ecosystem scales. Introduction: Polygon proved that you could take the standard Ethereum Virtual Machine and wrap it in a zero-knowledge proof layer to achieve instruction-level compatibility with cryptographic finality. By referencing their success, we ground this project in proven computer science while applying it to a unique Proof of Work environment. Launched in 2023, this Sovereign PoW ecosystem requires a high-security, non-custodial environment for the peer-to-peer exchange of Proof-of-Work Bitnet Money (BTN). Our goal is to implement the ZK-EVM principles pioneered by Polygon, optimized for the decentralized sovereignty of Bitnet. Role: Lead Blockchain Architect (ZK-HTLC Specialist) Budget: $500 Fixed (Grant-Based Milestones) Network: Bitnet Money (Chain ID 210 | Sovereign PoW EVM) RPC: https://rpc.bitnetmoney.com Explorer: https://explorer.bitnetmoney.com Genesis: 0xa3cc7f928cebbc82a199e3c506104df317244e5de86018b375ef3096f674f1a 1. PROJECT OBJECTIVE Build an immutable, decentralized ZK-Atomic Swap platform. The system utilizes Hashed Time-Locked Contracts (HTLC) and Groth16 Zero-Knowledge Proofs (zk-SNARKs) to enable confidential, trustless swaps between native BTN and stablecoins (MockUSDT, MockUSDC, MockUSD1).1. PROJECT OBJECTIVE Build an immutable, decentralized ZK-Atomic Swap platform. The system utilizes Hashed Time-Locked Contracts (HTLC) and Groth16 Zero-Knowledge Proofs (zk-SNARKs) to enable confidential, trustless swaps between native BTN and stablecoins (MockUSDT, MockUSDC, MockUSD1). 2. TECHNICAL STACK & GUARDRAILS (NON-NEGOTIABLE) EVM Equivalence: Maintaining the 100% Solidity compatibility established by the Polygon zkEVM model. Privacy: zk-SNARK (Groth16) via Circom/SnarkJS. (No STARKs). Verifier: Solidity contract using BN254 (alt_bn128) curve + EVM pairing precompile. Gas Target: On-chain verification MUST be < 300,000 gas. Sovereignty: Zero-Admin. 0 matches for owner, onlyOwner, proxies, or upgradeability. Security: Nullifiers required to prevent replay attacks and Proof Malleability checks. Proving: Witness generation MUST be client-side (in-browser). Zero backend calls. 3. MILESTONES & THE "48-HOUR MOMENTUM" OFFER PHASE 1: Foundation & Down Payment ($150) Goal: Establish the fundamental "Lock-Claim-Refund" PoW state machine. The Challenge: Deliver functional Mock Tokens and a verified HTLC within 48 hours. Audit: Provide a Refund Transaction Hash (Lock -> Timeout -> Refund) proven on-chain. Verification: All contracts verified (Green Checkmark) on explorer.bitnetmoney.com. PHASE 2: ZK-Circuit & Verifier Integration ($150) Goal: Integrate the zero-knowledge privacy layer (inspired by Polygon's recursion/verification logic). Deliverables: .circom circuit + BN254 Solidity Verifier. Logic: Prove knowledge of secret without revealing preimage. Implement Nullifiers. Setup: Conduct Phase 2 Trusted Setup contribution for .zkey parameters. PHASE 3: Sovereign React DApp & Publication ($200) Goal: Validate proof generation in a zero-trust, client-side environment. The Frontend: React + Ethers.js. Client-side WASM for proof generation. Visual States: PENDING (Yellow), READY (Green), COMPLETED (Blue), EXPIRED (Red). Publication: Full source on GitHub, Arweave, and IPFS under your name. 4. TECHNICAL UI/UX SPECIFICATION Feature Technical Requirement UI Element Secret Generator Generate secure bytes32 random string + sha256 hash. "Generate Secret" Button + 2 Text Boxes. New Swap Form Fields: Target Address, Amount, Lock Code (Hash), Timelock. Input Form + "Create Swap" Button. Status Dashboard Scan contract state via Lock Code. Search Input + Visual Status Logic. Claim Logic Function call: claim(bytes32 _secret). "Claim" Button (Active if secret revealed). Refund Logic Function call: refund(). "Refund" Button (Active if block.timestamp > timelock). 5. CRITICAL COMPLIANCE CHECKLIST No Owner Functions: 0 matches for owner or onlyOwner. Contracts must be ownerless. Refund Logic: Personally tested lock -> timeout -> refund sequence on-chain. BN254 Compatibility: Verifier must use the EVM-native pairing precompile. 3-Venue Publication: GitHub + Arweave + IPFS access is mandatory for final payment. 6. REQUIRED SKILLS & SCREENING TEST Applicants must answer these 3 questions: How do you plan to keep the Groth16 verifyProof call under 300k gas on an EVM, following the efficiency standards seen in Polygon's architecture? In your Circom circuit, how will you ensure a single ZK-proof cannot be "replayed" to claim multiple swaps? Why is it a critical security failure to generate the "Witness" on a backend server for this specific project? DEVELOPER CONFIRMATION (REPLY WITH THIS): "I agree to the 3-phase, based on my bid for the project i.e ZK-Atomic Swap suite. I confirm: BN254 Solidity verifier, no owner functions, client-side witness generation, <300k gas verification, and as the developer of this project, I will do on my own the necessary for publication on GitHub/Arweave/IPFS." Skills Required Cryptography Blockchain Frontend Development Solidity Smart Contracts Web3.js