Tactful Cipher

Web 3.0 | Aerospace Engineering Student | Smart contract developer | Security researcher | ZK Engineer | Building @DeCipherLabs_HQ

[Genghis not Kahn @totdking]

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 :)

[Aztec @aztecnetwork]

@web3privacy 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! https://t.co/PWs7nJdvwE

[Zac @Zac_Aztec]

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.

[Aztec @aztecnetwork]

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?

[Tactful Cipher @TactfulCipher]

@Zac_Aztec There are honestly a lot of use cases for Aztec.
What do you think about this? @Zac_Aztec

[Tactful Cipher @TactfulCipher]

@aztecnetwork I am working on a private, auction platform on @aztecnetwork where all bids and buyer identities stay completely hidden from competitors, the public, and even the auctioneer. It forces everyone to bid what they honestly think the item is worth without being influenced by others.

[Tactful Cipher @TactfulCipher]

@aztecnetwork I am working on a private, auction platform on @aztecnetwork where all bids and buyer identities stay completely hidden from competitors, the public, and even the auctioneer. It forces everyone to bid what they honestly think the item is worth without being influenced by others.

[Aztec @aztecnetwork]

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.

[Tactful Cipher @TactfulCipher]

@zkphub @aztecnetwork @EFDevcon @Zac_Aztec Ethereum adding programmable privacy doesn’t make @aztecnetwork obsolete
It could actually make Aztec more relevant. I said earlier that Ethereum can provide privacy at the base layer, while Aztec can build an execution environ where private state and private apps are the default

[Aztec @aztecnetwork]

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.

[Tactful Cipher @TactfulCipher]

@zkphub I think Ethereum baking privacy into the protocol would be huge, but I actually see it as bullish for @aztecnetwork and even stronger for Aztec’s thesis, not really a threat.

Ethereum can make privacy native, but Aztec makes it programmable. That’s how I see it anyway.

[Tactful Cipher @TactfulCipher]

I’m wrapping up the confidential payroll project I’ve been building on @aztecnetwork .
@Zac_Aztec here is the latest update.
https://t.co/8IVl5mLrRT

[Tactful Cipher @TactfulCipher]

🧵

A small update on the confidential payroll project @DecipherLabs_HQ .

In my last post, I was at the testing and validation stage.

Since then, I’ve spent a lot more time debugging the Aztec execution environment than writing new payroll logic 😅

[Tactful Cipher @TactfulCipher]

I’ve cleaned up the repository and documentation and I’m leaving the project here for now.

https://t.co/8IVl5mLrRT

This project taught me a lot about private notes, ownership, execution scopes and state transitions.

For now, I’m calling it complete.

[Tactful Cipher @TactfulCipher]

The main goal was to build and validate a confidential payroll system around private state.

That part is done.