| Job Position | Company | Posted | Location | Salary | Tags |
|---|---|---|---|---|---|
Vac | Remote | $84k - $150k | |||
Binance | Dubai, United Arab Emirates |
| |||
Logos | Remote | $84k - $150k | |||
Dcentralab | Remote | $72k - $150k | |||
| Learn job-ready web3 skills on your schedule with 1-on-1 support & get a job, or your money back. | | by Metana Bootcamp Info | |||
Binance | South East Asia |
| |||
Uniswaplabs | Remote | $86k - $90k | |||
Aztec | Remote | $98k - $108k | |||
Axiom | New York, NY, United States | $125k - $175k | |||
Weekday AI | Delhi, India | $36k - $54k | |||
Pluto | New York, NY, United States | $81k - $105k | |||
Matter Labs | Remote | $87k - $87k | |||
QuickNode | United States | $203k - $227k | |||
Salt Technologies | Pune, India | $113k - $165k | |||
Spearbit | Remote | $200k - $250k | |||
Matter Labs | Remote | $175k - $240k |
About Vac Vac builds public good protocols for the decentralized web.We do applied research based on which we build protocols, libraries and publications. This role is within the the Vac Incubator Project “Nescience”, which is developing a state separation architecture with selective privacy. The role In this role, you will be responsible for maintaining our Rust code base, transforming research prototypes into production and collaborating with researchers, prototyping ideas, measuring performance, and conducting code reviews, and shaping engineering culture. Your responsibilities will include planning, implementing, and shipping end-to-end functionality in monthly release sprints. As well as profiling bottlenecks, hardening cryptographic components, and writing property-based tests. The ideal candidate should be comfortable with modern cryptography, familiar with zero-knowledge virtual machines (zkVMs) and experienced with blockchain or other peer-to-peer systems, and motivated by decentralisation and privacy. Key responsibilities
Write and maintain Rust code base. Develop new solutions based on research output. If necessary, participate in research.
You ideally will have
4-5 Years of Rust experience. Experience writing asynchronous code in Rust using Tokio. Solid understanding of cryptography. Understanding, how zkVM’s work. Experience in, and passion for, blockchain technology. A strong alignment to our principles.
Bonus points if
Experience writing code using libp2p. Worked with RISC0. Participated in building blockchain projects.
[Don’t worry if you don’t meet all of these criteria, we’d still love to hear from you anyway if you think you’d be a great fit for this role. Just explain to us why in your cover letter]. Hiring process The hiring process for this role will be:
Interview with our POps team Interview with Nescience team lead Pair programming task with the Nescience team Interview with Vac team lead
The steps may change along the way if we see it makes sense to adapt the interview stages, so please consider the above as a guideline. Compensation The expected compensation range for this role is negotiable, dependent on how we assess your skills and experience throughout our interview process. We are happy to pay in any mix of fiat/crypto.
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.