Build Layer-2 Cross-Chain Smart Contracts
Budget: $5,000 – $10,000 USD
I’m expanding our protocol to run seamlessly across multiple chains while taking full advantage of Layer-2 speed and cost efficiency. What I need now is pure development fire-power: someone who can architect and code production-ready smart contracts, design the cross-chain message flow, and stitch everything together on the L2 of choice (Optimistic or ZK rollups are both on the table).
The work centres on three pillars—smart contract logic, cross-chain interoperability, and Layer-2 scaling solutions. Solidity (or Vyper), Hardhat/Foundry, EVM-compatible bridges, proof relayers, and gas-optimised patterns will be part of the daily toolbox. Familiarity with rollup frameworks like Optimism, Arbitrum, zkSync or Starknet is a major plus, as is experience with Cosmos SDK / IBC or Polkadot XCM for non-EVM routing.
Current architecture diagrams, tokenomics specs, and a partial test suite are ready to share once we sign an NDA. From there I’ll look for:
• Production-grade smart contracts with full test coverage
• A working cross-chain bridge or messaging layer proving state finality end-to-end
• Deployment scripts and CI pipelines for mainnet and at least one L2 testnet
• Concise technical documentation and hand-off notes
Code quality, gas efficiency, and security best practices (OpenZeppelin, formal verification where practical, and audit-ready comments) will be the acceptance criteria. If this sounds like your domain, let’s talk timing and milestones so we can push this live.
The work centres on three pillars—smart contract logic, cross-chain interoperability, and Layer-2 scaling solutions. Solidity (or Vyper), Hardhat/Foundry, EVM-compatible bridges, proof relayers, and gas-optimised patterns will be part of the daily toolbox. Familiarity with rollup frameworks like Optimism, Arbitrum, zkSync or Starknet is a major plus, as is experience with Cosmos SDK / IBC or Polkadot XCM for non-EVM routing.
Current architecture diagrams, tokenomics specs, and a partial test suite are ready to share once we sign an NDA. From there I’ll look for:
• Production-grade smart contracts with full test coverage
• A working cross-chain bridge or messaging layer proving state finality end-to-end
• Deployment scripts and CI pipelines for mainnet and at least one L2 testnet
• Concise technical documentation and hand-off notes
Code quality, gas efficiency, and security best practices (OpenZeppelin, formal verification where practical, and audit-ready comments) will be the acceptance criteria. If this sounds like your domain, let’s talk timing and milestones so we can push this live.