Luciana

@EFDevcon @ethereum Audits, formal verification, and preventive assurance for smart contracts and protocols. Our team brings deep expertise in cryptography, zero-knowledge systems, and privacy, ensuring rigorous security from design to deployment.

x.com/i/article/1979…

Most auditors stop at contracts. @NethermindSec goes deeper, into ZK circuits, privacy layers, and formal proofs where trust itself is coded. The invisible layer is where they operate. And that’s why they belong here. club.rekt.news/audit-broker

Women, wine, and crypto? 💅 We're excited to announce a co-hosted event with @myBraavos in Tel-Aviv! This event is all about networking and exciting panels! So, you know the drill, if you are around, come and join us 👇

The countdown is on: 1 day to go! Join us and our guests for the next Ethereum milestone 🐡 Livestream🔗youtube.com/live/E_i4e-oU_… We're hosting builders from the entire ecosystem! Ethereum client teams @ethnimbus team, @potuz_eth, @terencechain from @prylabs, @vdWijden from @go_ethereum Nethermind client’s @_D4nie1 @urozmeJ @M25Marek @marcin_d_s @ben_a_adams @__flcl @asdacap L2 builders @starknet, @OPLabsPBC, @m_ratsim from @taikoxyz, @DeclanFox14 from @LineaBuild, @toghrulmaharram from @Scroll_ZKP, @FmrSmrt from @the_matter_labs, @0xb17z from @CoinbaseCloud And many other great builders from the Ethereum community!

Nethermind Research is here to research & build on Starknet. We are looking for 🧠 - Protocol Researchers - Mechanism Designers - Cryptography Researcher - Research Engineers - Consensus Research Engineers 🔖Bookmark nethermind.io/open-roles to keep an eye out for new listings! Let us show you some of the research directions we will investigate in cryptographic research. Ready? Let’s go! 🧵 🔹Starknet aligned DA layer Ethereum’s DAS-s, although efficient, are not really “Starknet aligned”. This is because they rely on the discrete logarithm problem to ensure data availability. Hence, arguably, the security guarantees of DAS are weaker than what STARKs used to secure Starknet transactions offer. To fix that gap, we will investigate FRIDA — the transparent FRI-based DAS — to build a Starknet-aligned DA layer. 🔸SNARK CairoVM prover We love STARKs. But we love SNARKs as well. We will build a CairoVM SNARK prover to bring Cairo to SNARK lovers. We will utilize all recent zk-tech, like folding, to make proving efficient and effortless. 🔹zkFHE FHE unlocks another layer of on-chain transaction privacy. However, FHE operations are expensive. To make FHE more blockchain-friendly, we will implement a zk-proof system that will allow users to perform FHE operations off-chain and cheaply verify them on-chain. 🔸zk coprocessors zk coprocessors augment the native capabilities of the blockchain, allowing features such as trustless historical data retrieval and verifiable off-chain computing. We see a great rise in zk coprocessors. But how should the prover market look like, how will the provers be synchronized, how will fees be paid, and how can we minimize the proof verification cost? We’re looking forward to working on these problems. 🔹Reputation and ID system The advent of zk coprocessors unlocks access to on-chain (and potentially cross-chain) historical data. We can think of using this functionality to build a reputation system powered by the aggregation and interpretation of this data into a reputation score. The next step will be to build a decentralized ID system on top of the reputation system. 🔸Privacy on Starknet We will leverage Starknet’s scalability for the design and implementation of privacy-preserving protocols. For example: - cost-efficient private voting protocols, which can be used to improve current governance systems - applications for the private transfer of assets - privacy-preserving decentralized exchange 🔹More cryptographic primitives in Cairo We want to bring more cryptographic primitives to Starknet to encourage even more cryptography-based products. This includes implementations of various elliptic curves and zero-knowledge proof systems. 🔸Hybrid arithmetics There are so many pain points arising from writing arithmetic from field Foo to field Bar. We will look at ways to mitigate these. 🔹Soundness proofs There are several open problems related to the soundness of STARKs and of FRI. Solving them would allow us to configure STARKs reliably in more efficient ways. We will continue our research around these questions. 🔸Soundness in the presence of hash collisions A particular soundness problem is the following: suppose an attacker can find collisions for the Merkle tree hash function. How is the soundness of the STARK or FRI protocol affected? Following common practice, STARKs are configured so that it would be too expensive for an attacker to find collisions. But is that really necessary? We will look into it. 🔹Alternative commitment scheme By now, many of us are folding scheme enthusiasts. However, Merkle trees are not folding-friendly. Towards circumventing this, we will research alternative homomorphic vector commitment schemes so that they can be used for folding and possibly lattice-based to preserve post-quantum resistance.

Join us & work on Starknet 🚀 And in the words of @tkstanczak "reignite your love for computer science, maths, and finance!" Dedicated to pushing the boundaries of blockchain, we’re gearing up for a future where computational integrity meets decentralized technology. 🧠 Build with us, and let's expand Ethereum with our Layer 2 roadmap and develop the most complex distributed systems. We are a global, remote-first, and impact-driven team that comes together at events around the world. 🌐 Start as an intern, or join as an expert or leader, and work with the sharpest minds across ecosystems! Get up to speed with Starknet 🚀 - Cairo book: book.cairo-lang.org - Starknet by Example: book.starknet.io - Tutorials for devs by devs: starknet.io/en/tutorials - Learn syntax: github.com/shramee/starkl… - Deploy your Starknet contracts github.com/NethermindEth/… - Submit your project: github.com/keep-starknet-…