Category |
Details |
Position |
Smart Contract Engineer |
Recommended Duration |
4 Hours |
Format |
Remote/Virtual |
Candidates must select and complete ONE out of four available technical issues. The submission should include a complete solution with proper documentation explaining your approach and implementation decisions. After evaluation, you will receive compensation for both your time and the submitted solution.
Issue Title |
Problem |
Technical Focus |
Repository |
Issue Link |
Fix JWT Prover for Special Characters |
JWT proof generation fails for Google accounts with special characters |
Modify ZK circuit constraints to handle special character encoding |
zkemail/jwt-tx-builder |
#8 |
Modular JWT Verification Architecture |
JWT verifier needs separation from transaction builder |
Refactor smart contract architecture to isolate core JWT verification logic |
zkemail/jwt-tx-builder |
#5 |
Assert state changes for script tests |
Deployment scripts do not adequately assert on state changes |
Refactoring tests |
zkemail/email-recovery |
#65 |
Prototype a new ERC7579 recovery module |
We need to implement a prototype for a simpler and more generic recovery module |
Implement new recovery module prototype |
zkemail/email-recovery |
#66 |
Stage |
Duration |
Focus |
Initial Review |
1-2 Days |
Code quality and completeness |
Technical Evaluation |
2-3 Days |
Detailed assessment of all components |
Final Decision |
1 Day |
Overall evaluation and decision |
- Fork the repository of the issue on Github
- Create a new branch with your name
- Commit your solution and push changes
- Create a pull request against the main branch
- Email: Send an email to [email protected] with:
- Subject line: "Technical Challenge Submission - [Your Name]"
- GitHub PR link
- Brief summary of your chosen issue and approach
- Attach a resume and/or portfolio