Recruitment notice for Ooo: Tokamak zk-EVM

Our technical milestone

Position	Work Description	Milestone
Cryptographer	Designing zk-SNARK, multi-party computation, consensus algorithms, and zk-rollup	A1, A3, B2, C2
L2 network developer	Establishment and management of infrastructure for operating a layer 2 network	D1, D2
~~ZKP front-end developer~~	~~Developing ZKP front-end compilers~~	B1
Circuit developer	Developing efficient circuits of EVM and our zk-rollup	B1, C1
~~Smart contract developer~~	~~Implementing smart contracts that includes layer 2 network entities and cryptography verifiers~~	~~A2, B3, C3, D1, D2, E1~~
~~Economist~~	~~Designing an incentive mechanism to motivate honest participants and deter dishonest ones from collusion~~	E2
~~ZKP back-end developer~~	~~Implementing and accelerating ZKP back-end algorithms~~	~~A2, B3, C3, E1~~
~~General front-end developer~~	~~User interface development, user/developer experience improvement, and git management for the project codes.~~	~~All~~
General engineering writing specialist	Improve readability of all project technical documents, including papers, reports, and design specifications.	All
~~Graphic designer~~	~~Improve the creativity and quality of illustrations and figures used in project documents and UI of project products.~~	~~All~~

(Optional) Review our public documents such as blog articles, progress reports, and papers to catch up on the project’s motivation, goal, and progress
(Mandatory) Submit a short proposal about how you can contribute to our project.
- It MUST INCLUDE problem formulation, goals, and a compelling argument for why you can achieve your goals.
  - See this example, where the sections “Problem Statement and objectives”, “Expected deliverables”, “Relevant Experiences” (or convince us that why you can fulfill the objectives), and the table “Expected deliverable timeline” are the must-have components.
- You will be informed of either Accept or Reject within two weeks after submission.

We value fundamental knowledge and insight rather than coding skills.
We don't plan to lecture you, so please review our public documents and codes yourself first. After that, we always welcome your questions or in-depth discussions.
The length of your proposal does not matter as long as the content is clear (even one page is acceptable).