opendp VS namada

Example 2: dispatches to any member of the outer product of hashable and float types. This also shows how you can have type-erased arguments that are later dereferenced according to the type argument.

More information : https://namada.net/

Web https://namada.net

Both Namada and Zcash use zero-knowledge proofs (ZK-proofs), a type of cryptography, to verify transactions without revealing the sender, receiver or the transaction amount. ZK-proofs are a technique for proving the validity of information without revealing the information itself. ZEC users can either keep transaction details confidential (shielded) or public (transparent).

Let’s return to this concept of privacy being a public good and Namada’s unified privacy set. Namada actually incentivises the growth in users (and thus assets and overall privacy) of the set itself by subsidizing and rewarding those entering the privacy set. By subsidizing and rewarding users for their privacy usage, arguably privacy (due to its externality) should be considered a public good.

The Ethereum Bridge is not yet implemented as of 0.12.0. Keep an eye on the Changelog 📷 to see when it will be released.

A) Given the published resources (blog, website, talks/podcasts, docs, specs, codebase) summarise, write about the Namada protocol, its components, or content that helps more people understand / learn about the project.

Reference implementation in Rust: github.com/anoma/namada

Heliax | Multiple roles | REMOTE (+-2 hours from CEST ideal) | Full Time | https://heliax.dev/jobs#all-jobs

Heliax is a public goods lab which was built on years of pioneering experience across distributed systems, programming language theory, and zero-knowledge cryptography. All our work is open-source. Examples of some of our projects are Namada (https://github.com/anoma/namada), a sovereign proof-of-stake blockchain; Juvix (https://github.com/anoma/juvix), an experimental programming language; and Taiga (https://github.com/anoma/taiga), a framework for generalized shielded state transitions.

We are currently actively hiring for a number of positions, most notably Senior Rust Engineers, Senior Full Stack Engineers, and a Protocol Security Lead.

For the Senior Rust Engineer position, we are looking for experienced Rust developers that are interested in applying novel research to create high-quality open-source technology and solve outstanding problems in the blockchain space. You'll be working on distributed ledger technology implemented in Rust, all the way up and down the stack from the P2P layer to consensus algorithms, smart contract systems, proof-of-stake incentive mechanisms, privacy-enhancing cryptographic components, and on-chain governance procedures.

For the Senior Full Stack Engineer position, we are looking for either web developers with experience using TypeScript and other modern web frameworks or software developers who have experience with Rust. Some representative examples of features you’ll be working on in this role are: adding support for Ledger hardware wallet connectivity, support for generation and use of file-based keys, generation of shielded transactions using cryptographic libraries, display of any digital asset (including NFTs) and associated transaction history, and on-chain management of staking and governance. It's a plus if you've previously worked with WebAssembly.

For the Protocol Security Lead, you'll be responsible for breaking protocols both in theory and practice in and outside the company, and assembling a team to help them do so. You'll receive a high degree of latitude and autonomy to prioritize tasks and search for the weakest links in complex systems in order to break them. The rough structure could be compared to Google Project Zero, but with a focus on cryptographic protocols & implementations instead of web technology writ large.