jaosef.eth

1.1K posts

jaosef.eth banner
jaosef.eth

jaosef.eth

@jaosef

Tweeting about, zero-knowledge, privacy, network design and MEV. President, Co-founder & Product @aztecnetwork Views are my own.

London, England Katılım Haziran 2013
660 Takip Edilen6.2K Takipçiler
Sabitlenmiş Tweet
jaosef.eth
jaosef.eth@jaosef·
Ship a network that is built to last. Decentralised from day 1 — controlled by the community. Aztec's community launched the Ignition chain of Aztec on Ethereum main-net at 1am last night. The future is here and it is private.
Aztec@aztecnetwork

BREAKING: Aztec just shipped the Ignition Chain, the first fully decentralized L2 on Ethereum. This launches the decentralized consensus layer that powers the Aztec Network. ignition.aztec.network 🧵

English
9
3
81
8.8K
jaosef.eth retweetledi
Aztec
Aztec@aztecnetwork·
Aztec is the first fully decentralized L2 on Ethereum. No privileged actors, no closed doors. Governance runs the same way. Any idea can become a protocol upgrade — if it survives public scrutiny. AZIPs, AZUPs, and onchain voting form a transparent pipeline from forum post to live protocol change. These are cypherpunk values in practice. Read about how it works and how to get involved: aztec.network/blog/how-aztec…
Aztec tweet media
English
27
19
127
8.5K
jaosef.eth
jaosef.eth@jaosef·
Don’t be like this guy.
jaosef.eth tweet media
English
2
0
12
570
jaosef.eth
jaosef.eth@jaosef·
Isn’t the issue with the third way that any country or provider that has scanned your passport (think e-gates) likely has the same hash so can prove they are part of the nullifier registry as they have the contents of your passport chip? Liveness checks do solve this. Note this could also be a good way to bootstrap the registry.
English
1
0
1
97
Lasha 🔑🗳️
Lasha 🔑🗳️@LashaAntadze·
Let me explain it in simple terms. Since 2024, when we first launched #freedomtool with the Russian opposition, we have been boiling in hot water on the ground to solve each issue and ensure every vote of dissent was secure (there were 40,000 participants). That might look small, but it was the largest protest gathering in Russia since 2021. There are two major caveats when working with passports. First, you need to ensure uniqueness so that 1 vote = 1 passport. For this you have three options: 1. Passport support (active authentication), where you can sign and get a nullifier directly from the document. But since the 2010s, major countries have abandoned support for that standard and it won’t work at scale. 2. An external signer: you can use a TEE, OPRF, secure server, whatever everyone is discussing. It adds an additional secret, and voila, it works. This is the architecture we used for the Russian use case. 3. A third way, which in my opinion is the purest but requires network effect: so-called “shielded privacy of passport hashes,” where you junk up all the passport hashes in an on-chain registry and reuse them for different use cases, granting everyone plausible deniability. I call this pure because there is zero dependency on any vendor. You get a system like blockchain was for money. one that works outside anyone’s control and no one can switch off. When you touch reality, we forget that MPC networks halt operations for certain jurisdictions on governmental notice, that states control bandwidth and can block your traffic, and that wherever you don’t face hostility, participation isn’t a crime and you don’t need these hard setups. That’s the reality check most builders lack with voting tools. It’s not just an engineering question, it’s a political one. When you hit the ground, you learn it on your skin and the skin of others. The second problem; governments issuing fake passports can be solved in two ways: First, a similarity proof of the passport photo and the person holding a phone (we’ve built that with ZKML Bionetta). Or, the second and more elegant one: a ZK graph, where you build participation commitments over time. That can become a much more valuable foundation to reimagine digital democracy. (We’ve built that too with ERC7812) So thank you all for your contributions, but it’s still odd that after all these years we’re discussing the same topics, yet no one asks the real question: what are the true barriers to bringing these tools to the masses, and under what circumstances they actually work?
Ameen Soleimani@ameensol

gm eth nerds who care about ZK voting

English
34
42
167
112K
jaosef.eth
jaosef.eth@jaosef·
Aztec is the bleeding edge of cryptography and blockchain. This post outlines what developers and end users should expect during the alpha phase, and detail our approach to building confidence in the security of network. Privacy is coming.
Aztec@aztecnetwork

Aztec is run by a global network of 3.9k+ sequencers and provers. As the first decentralized L2, this introduces some novel challenges in how security is addressed. Learn about the phased rollout plan, and what to expect for Aztec Alpha security: aztec.network/blog/alpha-net…

English
3
5
34
2K
jaosef.eth retweetledi
jaosef.eth retweetledi
Santiment
Santiment@santimentfeed·
🧑‍💻 Here are crypto's top Layer 2 projects by development. Directional indicators represent each project's ranking rise or fall since last month: ➡️ 1) @starknet $STRK 📈 2) @aztecnetwork $AZTEC 📉 3) @arbitrum $ARB 📉 4) @zksync $ZK 📉 5) @optimism $OP 📉 6) @cartesiproject $CTSI 📉 7) @fuel_network $FUEL 📉 8) @skale $SKL 📈 9) @immutablex $IMX 📉 10) @scroll_zk $SCR 📖 Read about the @santimentfeed methodology for pulling github activity data from project repositories, and why it is so useful for crypto trading: medium.com/santiment/a-di… 🔖 Bookmark our brand new Layer 2 token screener here, and see what others in crypto can't: app.santiment.net/screener/layer…
Santiment tweet media
English
22
22
101
16.6K
jaosef.eth
jaosef.eth@jaosef·
100% there is so much ethereum can do to make L1 more zk friendly. Currently its going the other way as opp codes used to verify zk snarks proofs are likely going to increase in cost to aid zkevm just in time proofs.
Ameen Soleimani@ameensol

eth nerds will make "privacy by default" roadmaps but they won't implement a Poseidon precompile (Poseidon is the most battle-tested of the efficient hash algorithms to verify in a ZK proof) meanwhile solana, starknet, and stellar all have it...

English
0
1
21
1.5K
jaosef.eth retweetledi
Ameen Soleimani
Ameen Soleimani@ameensol·
eth nerds will make "privacy by default" roadmaps but they won't implement a Poseidon precompile (Poseidon is the most battle-tested of the efficient hash algorithms to verify in a ZK proof) meanwhile solana, starknet, and stellar all have it...
Ameen Soleimani tweet media
English
31
20
246
60.6K
jaosef.eth
jaosef.eth@jaosef·
The internet does not relay on intermediaries for strong privacy. The internet has SSL. Privacy via cryptography. Private execution via an intermediary is not private. The intermediary can see every single thing. You just invented a worse SQL database but called it private execution on a blockchain. Privacy on blockchains requires cryptography. Anything else is either not a distributed blockchain or not private.
English
8
5
60
4.9K
Cooper
Cooper@cooper_kunz·
@_prestwich i thought they were just going to use a google doc
English
1
0
1
100
James Prestwich
James Prestwich@_prestwich·
everyone already knows the agent's' preferred payment layer is gonna be mongodb because it's web scale
English
2
0
13
843
parsec
parsec@parsec_finance·
After 5 years, parsec is shutting down. Not how we wanted our story to end, but we are proud of what we built and the value we provided along the way. We are eternally grateful to those that traversed the ups and downs onchain with us. It was quite the ride 🔭
English
134
17
701
152.4K
jaosef.eth retweetledi
Zatoshi
Zatoshi@Zac_Aztec·
love this. ZK unlocks new novel gaming primitives. Games are also a fantastic sandbox environment to test new forms of governance, communication and organisation.
Savio 👽@savio_sou

x.com/i/article/2024…

English
5
3
23
2.5K
jaosef.eth retweetledi
Aztec
Aztec@aztecnetwork·
Ethereum’s IPTF rebuilt private bonds on Aztec. Instead of coordinating three codebases and a trusted relayer, the result was a ~200 line @NoirLang contract. “The complexity did not disappear; it moved into protocol infrastructure.” iptf.ethereum.org/private-bonds-…
English
23
23
115
10.2K
Zatoshi
Zatoshi@Zac_Aztec·
8 years on, still grinding with @jaosef
Zatoshi tweet media
English
9
3
93
5.6K
jaosef.eth
jaosef.eth@jaosef·
@dnkta Update, Uniswap have identified and fixed the issue. Please comment if not fixed.
English
0
0
1
28