| Job Position | Company | Posted | Location | Salary | Tags |
|---|---|---|---|---|---|
Webb | United States | $70k - $150k | |||
O(1) Labs | San Francisco, CA, United States | $63k - $79k | |||
Consensys | Remote | $63k - $75k | |||
Panther Protocol | United States | $40k - $65k | |||
| Learn job-ready web3 skills on your schedule with 1-on-1 support & get a job, or your money back. | | by Metana Bootcamp Info | |||
MetaMask | United States | $54k - $72k | |||
NEAR | San Francisco, CA, United States | $29k - $50k | |||
Consensys | Remote | $54k - $72k | |||
Iron Fish | Remote | $40k - $70k | |||
Blockswap | Remote | $60k - $90k | |||
Brave | San Francisco, CA, United States | $11k - $60k | |||
Findora | Remote | $63k - $90k | |||
Status.im | Remote | $29k - $63k | |||
Parity Technologies | Berlin, Germany | $63k - $90k | |||
MobileCoin | San Francisco, CA, United States | $63k - $90k | |||
DFINITY | Palo Alto, CA, United States | $80k - $105k |
At Webb, we're building the largest private blockchain bridge protocol possible. We use modern cryptographic techniques like zero-knowledge proofs and multi-party computation to enhance privacy for users of multi-chain blockchain applications.
Our private bridge protocol is a critical piece of infrastructure that enables anyone to privately move cryptocurrency assets between blockchains. We are passionate about privacy and building products that give power and privacy back to users of blockchain protocols.
We are building multiple implementations of our protocols targetting the EVM, Substrate, and Cosmos ecosystems and plan to support more as we grow.
Role
We are looking for web3 / full-stack engineers to join our development team and help grow our web facing products. You will help design open source APIs and our main privacy product, the Webb UI, an interface for privately bridging webb wrapped cryptocurrency assets. The right person has at least 5+ years of experience building full-stack applications and at least 1+ years developing in the blockchain industry. Any additional blockchain experience writing smart contracts is a plus.
The main area of ownership for a web3 / full-stack engineer at Webb is to:
- Design and develop SDKs and WASM tools for interacting with the Webb Protocol.
- Research and implement speed and privacy optimisations for the user experience
- Write specs of product features and milestones for the product team.
- Mentor and provide support to junior developers.
- Read open-source libraries and APIs and contribute to open-source repos.
- Friendly engagement with our community 🙂!
Background
- Proficiency in Typescript.
- Experience building beautiful products.
- Experience leading development projects and teams.
- Profiency programming with open-source libraries and blockchain APIs such as web3.js / ethers.js / PolkadotJS
- An interest in distributed systems and blockchain technology.
A plus
- Experience programming with Solidity, Rust, WASM.
- Experience building blockchain systems and/or smart contract applications.
- Understanding of cryptographic data structures.
Organisation
We are a fully remote team and are incubated by Commonwealth Labs, a venture incubator. We work on slack and use Github to handle task allocation and use Notion to track technical specs and organise research. At Webb you'll have a tremendous amount of freedom to help shape the narrative and we don't have a ton of bureaucracy, you will be free and incentivised to do your best work on your own time.
For more info about our work, check out our Github.
Webb focuses on Security, Privacy, Blockchains, and Blockchain / Cryptocurrency. Their company has offices in United States. They have a small team that's between 1-10 employees.
You can view their website at https://github.com/webb-tools
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.