| Job Position | Company | Posted | Location | Salary | Tags |
|---|---|---|---|---|---|
NIL (CYPRUS) LTD | Lima, Peru | $87k - $110k | |||
Nexus | San Francisco, CA, United States | $105k - $120k | |||
Matter Labs | Remote | $154k - $213k | |||
O1labs | Remote | $113k - $165k | |||
| Learn job-ready web3 skills on your schedule with 1-on-1 support & get a job, or your money back. | | by Metana Bootcamp Info | |||
O1labs | Remote | $54k - $100k | |||
Avo Intelligence | Remote | $12k - $36k | |||
Logos | Rio De Janeiro, Brazil | $81k - $95k | |||
Codex | Lisbon, Portugal | $81k - $95k | |||
RISC Zero | Remote | $174k - $226k | |||
Provable | San Francisco, CA, United States | $143k - $156k | |||
ZkCloud | Remote |
| |||
P2P. org | European Union |
| |||
Matter Labs | United States | $86k - $120k | |||
Matter Labs | Remote | $72k - $87k | |||
Matter Labs | Remote | $87k - $87k |
=nil; Foundation has been at the forefront of Ethereum scalability solutions since 2018. With a mission to overcome the Ethereum scalability challenge, our team is dedicated to launching our own L2 solution — =nil; zkSharding, a zkRollup that securely scales Ethereum empowering web3 developers to build scalable, secure, and composable applications.
Our architecture supports parallel transaction processing across multiple execution shards, each validated by zero-knowledge proofs (ZKPs) and EVM opcode compatibility. Interoperability among these shards is seamlessly maintained through a native cross-shard communication protocol, enabling efficient and secure interactions within the network.
We are looking for someone to join our Integration Team. The team key responsibilities are:
- Integration: Build and integrate tools like explorers, wallets, plugins, and extensions, ensuring a seamless user experience with =nil;
- Decentralized Application Development: Architect and develop the first dApps on top of =nil;, utilizing sharded architecture and multi-currency features. This involves exploring innovative project ideas or adapting existing dApps like Uniswap V2 to the =nil; ecosystem, pushing the boundaries of decentralized technology
Responsibilities
- Work on internal integrations to support =nil;, such as developing tools like the hardhat-plugin, block explorer, in-browser IDE, Block Indexer, and more. =nil; protocol is written in Go, and most integrations utilize TypeScript. Examples of existing integrations include:
- CLI: Command-line interface for interacting with =nil; (written in Go)
- Hardhat-plugin: Adapts requests and responses to match =nil; RPC and unique features (TypeScript)
- Block Explorer: A tool for viewing block and message data (TypeScript)
- Develop and Design the first cross-shard dApps on top of =nil;, leveraging the sharding and multi-currency features. Examples include:
- Adapting Uniswap V2 to =nil; by adding multi-currency support and modifying the architecture to distribute load across multiple shards.
- Designing the architecture for an orderbook DEXto operate efficiently on a sharded blockchain.
Qualifications
- Strong engineering background with the ability to adapt to various programming languages and tech stacks as required by different projects (experience with Go, TypeScript, or Solidity is a plus)
- Willingness to learn and work with Web3 protocols and blockchain technologies, even if prior experience is limited
- Ability to design and implement scalable and secure systems in a decentralized environment
- Independence and productivity, with the ability to take ownership of projects from inception to completion
- Proficiency in English (B2+), both written and spoken, to effectively collaborate with international teams
Benefits
What is Zero-knowledge?
Zero-knowledge is a concept in cryptography that allows two parties to exchange information without revealing any additional information beyond what is necessary to prove a particular fact
In other words, zero-knowledge is a way of proving something without actually revealing any details about the proof
Here are some examples of zero-knowledge:
- Password authentication: When you enter your password to log into an online account, the server doesn't actually know your password. Instead, it checks to see if the hash of your password matches the stored hash in its database. This is a form of zero-knowledge because the server doesn't know your actual password, just the hash that proves you know the correct password.
- Sudoku puzzles: Suppose you want to prove to someone that you've solved a particularly difficult Sudoku puzzle. You could do this by providing them with the completed puzzle, but that would reveal how you solved it. Instead, you could use a zero-knowledge proof where you demonstrate that you know the solution without actually revealing the solution itself.
- Bitcoin transactions: In a Bitcoin transaction, you prove that you have ownership of a certain amount of Bitcoin without revealing your private key. This is done using a zero-knowledge proof called a Schnorr signature, which allows you to prove ownership of a specific transaction output without revealing the private key associated with that output.
- Secure messaging: In a secure messaging app, you can prove to your contacts that you have access to a shared secret without revealing the secret itself. This is done using a zero-knowledge proof, which allows you to prove that you have access to the secret without actually revealing what the secret is.