I just completed Offensive Security Intro room on TryHackMe! Hack your first website (legally in a safe environment) and experience an ethical hacker's job. tryhackme.com/room/offensive… #tryhackme via @tryhackme

Got to design a network configuration on packet tracer properly without the auto tool and making use of the right cables for the right distances as well as the right ports for the needed cables. I learnt about the 10/100 as well as 1G/10G rj cabling. taking the @Cisco course :)

Our co-founder @Zac_Aztec will be there giving a talk on what programmable privacy entails at the system level! Hope to see you there!

Ethereum is developing very useful privacy primitives that lets devs define proofs and efficiently verify and aggregate zkVM programs. What it lacks is a private state model and model for private execution that enables private composability (private smart contracts talking to other private smart contracts). Aztec’s execution model validates that calls executed correct contract code (not generic zk proofs), updates private state reads/writes and contains its own private call stack to ensure it’s possible to make multiple nested calls to different contracts, all modifying their own state. We do all this without revealing the call graph or the state contents. In short - it’s private composability, a private state model and a language that makes building private smart contracts easy and idiomatic. Ethereum are not planning on adding this level of private transaction abstraction into their roadmap, nor is it their intention. If they were to do so they would end up looking like Aztec - which requires a radical divergence in both protocol design and their state model which We built a lot of Aztec’s cryptography and protocol technology because we had to, nothing else existed. I see Ethereum’s privacy initiatives as being very positive and if realised, we would embrace and adopt a lot of what they are deploying, it’s additive to Aztec’s goals.

Programmable privacy allows for unprecedented levels of customization to ensure your data is seen exclusively by the people you choose. What apps would you like to see built with programmable privacy on Aztec?

A viewing key hands over an address's entire history to whoever holds it. Programmable disclosure proves one fact to one party, once, as part of the contract logic. One is a compliance feature bolted on after the fact. The other is Aztec, with compliance designed into the protocol.

If you're building anything that touches user data onchain, this is the @EFDevcon talk to sit in. @Zac_Aztec will present what programmable privacy entails at the system level, from the perspective of the network that already shipped it.