fara.eth

138 posts

fara.eth

fara.eth

@fbwoolf

Ethproofs @ Ethereum Foundation | @eth_proofs. Previously @LeatherBTC, @HiroSystems, and @Hudl.

Katılım Şubat 2012
393 Takip Edilen295 Takipçiler
Sabitlenmiş Tweet
fara.eth
fara.eth@fbwoolf·
The EF mandate reminds us that protocol design choices shape decentralization: “If Ethereum supports only a narrow set of account types… those use cases that require smart accounts can only be served through intermediaries.” Protocol limitations create centralization pressure. Expanding native account capabilities (eg. EIP-8141) helps ensure advanced UX inherits Ethereum’s CROPS guarantees instead of relying on trusted middleware. EIP-8141 (link below)👇
Ethereum Foundation@ethereumfndn

Today, the Foundation’s Board released the EF Mandate. This document, which was first intended for EF members, reaffirms the promise of Ethereum, and the role of EF within this ecosystem.

English
3
4
20
2.2K
fara.eth retweetledi
fara.eth retweetledi
Ethereum Foundation
Ethereum Foundation@ethereumfndn·
1/ Today, the Global Policy Strategy (GPS) team is publishing Ethereum Basics for Governments and Institutions, a non-technical primer to equip the leaders making policy and deployment decisions with an understanding of how Ethereum works, how it's governed, and how it compares with perceived alternatives.
Ethereum Foundation tweet media
English
52
279
906
202.3K
fara.eth retweetledi
binji
binji@binji_x·
If you want to learn more about the incredible people stepping up to lead the next chapter of the Ethereum foundation, please let me know below, and we will tell their story in its entirety. A few people on the protocol side: > @corcoranwill (was a renowned architect that made buildings throughout manhattan and public libraries before going from castles in the sand to castles in the sky with his work coordinating across lean ethereum and quantum etc) > @kevaundray (made noir and has been pioneering ZK at a GM level across the board, while also being an incredibly talented musician) > @fredrik0x (helped make and secure world of war craft, then created a trillion dollar security initiative for Ethereum..probably inadvertently led to the creation of Ethereum) Their stories are amazing, and their personalities are even better. Ethereum is more than the EF, but the EF is star-studded, more focused than ever, and ready to dance.
Will Corcoran@corcoranwill

A leaner EF Protocol begins today, and I won't pretend the cut was painless. We lost real talent and real friends, and I'm grateful for everything they brought over many years. What remains is a focused team carrying an enormous mandate: keep mainnet secure, ship the next upgrades, and protect the long-horizon: * PQ ethereum * zkEVM on L1 * Privacy on L1 I'm excited for the road ahead and clear-eyed about how much it asks of us.

English
8
6
102
10.6K
fara.eth retweetledi
Ethereum Foundation
Ethereum Foundation@ethereumfndn·
Today, the EF is changing shape, concluding a months-long process of reorganization as part of the implementation of the Mandate and the Treasury Management Policy. We come out of this process with the structure, activities, and people necessary for execution on the critical tasks ahead of us, but also with 54 fewer colleagues, roughly 20% of the EF, many of whom will be finding ways to contribute to Ethereum from outside the EF in the coming weeks. Find a brief introduction to the new structure, and learn more about how we are supporting the people who are leaving in the full post below:
English
232
272
1.7K
598.6K
fara.eth retweetledi
Ethlabs
Ethlabs@ethlabs_org·
Announcing Ethlabs: a non-profit R&D lab for Ethereum and ETH Our mission is to make Ethereum the settlement layer of the global economy. The internet became global because shared protocols created a common language between networks. Private systems remained useful, but bounded. Finance is approaching a similar moment. As value, assets, and markets become digital, the world needs shared settlement infrastructure. Ethereum is uniquely positioned to become that shared base layer, the neutral foundation on which users, institutions, and agents can transact without intermediation. What we believe: • We believe credible neutrality matters. Ten years of uptime and the lowest counterparty risk. Ground that cannot be pulled away by any one country, institution, company, or person. • We believe ETH matters. The most valuable, programmable store of value. A decade of broad distribution, deep liquidity in onchain markets, and maximally trustless asset on Ethereum. • We believe DeFi matters. Markets, liquidity, credit, exchange, and coordination, open to anyone. • We believe adoption matters. Principles do not change the world until people benefit from them. We sit between two worlds: real usage from the builders at the frontier, and the protocol that has to support it. We work with users, applications, wallets, L2s, infrastructure teams, institutions, ETH holders, core devs and researchers, then turn what they actually need into protocol work, shared standards, infrastructure, and shipped products. Ethlabs is independent but Ethereum is a shared project. We are one node in a much larger network of stewards. This is the multi-node future. We have spent the better part of the past decade contributing to Ethereum core research and development. We are opinionated and transparent. We move with urgency, learn in public, and course-correct when we’re wrong. We are building a lean, talent-dense team for people who want to do the most important work of their careers: join@ethlabs.org
English
536
1.1K
4.5K
1.8M
fara.eth retweetledi
Aerugo
Aerugo@aerugoettinea·
1. Intro Vitalik recently wrote about where the EF should go; Aya added a note to explain how we got here, and why. I’ll write about the execution. We now have enough clarity to stop treating “what is the EF for?” as an open-ended question. Our mandate is clear: The EF exists to ensure Ethereum is, becomes, and remains real permissionless infrastructure for self-sovereignty: censorship (and capture) resistant, free and open source, private, and secure; and capable of supporting sovereignty-preserving coordination at scales where trusted institutions hitherto have been unavoidable. The following are my thoughts on some of the points that follow from the mandate and how we are translating it to action. But first, a short reminder about 2. What the EF is not for We are not here to optimize for EF importance, corpo/pol appeal, or ecosystem popularity. We are also not here to please short-term speculators, prop up TBTF neo-SIFIs, market every app on Ethereum, help anyone look good to their crypto or investor friends, or provide on-demand entertainment for dinner parties and private retreats. 3. What the EF is for: Eliminating weaknesses We are here to defensively strengthen places where Ethereum is, or can still become, extractive, totalizing, or vulnerable to cartel or state capture, or authoritarian tools of surveillance or coercion. We will base our actions on a full examination of what Ethereum is and can be at the protocol layer (what is actually running as “Ethereum”), the access layer (what users use to interact with the protocol), the user layer (the end-users who need and will need Ethereum), and the institutional layer (the intermediated paths that scale self-sovereign usage). The EF exists to harden every surface of Ethereum, including those where Ethereum can remain formally permissionless while becoming practically captured. Some obvious surfaces are the transaction pipeline, staking and network security, access layer standards and interfaces, self-sovereignty norms, privacy expectations, institutional adoption patterns, and social layer governance processes. The primary concerns are similar across most of them: does the status quo and its future trajectory minimize trusted dependencies, minimize points of leverage and capture vectors, make user privacy the default, preserve exit, and make trust assumptions legible? The work starts with the EF itself. We are moving compensation and major financial relationships toward ETH and mandate-compliant Ethereum-native stables, with exceptions where positive law or unavoidable operational constraints require exceptions. Rather than a purity ritual or instruction for people to take unmanaged personal risk, it is robustness, alignment, and product pressure. If the EF’s work is to make Ethereum usable as infrastructure for self-sovereignty, everyone at the EF will increasingly live inside the constraints of the system the EF exists to improve: wallet UX, volatility, accounting, privacy gaps, payment friction, stablecoin trust assumptions, recovery, dependency risk, etc. If we can’t use these tools ourselves, it is unrealistic to expect others to. Ethereum is already mature; those who do not depend on the user-facing stack have no business trying to shape its future, at any layer. The transaction pipeline is next. Preventing toxic MEV capture is core EF work, not a peripheral market-structure concern. Transaction supply, ordering, inclusion, block construction, propagation, and settlement are part of Ethereum’s neutrality boundary. Some MEV may persist as an adversarial phenomenon the protocol contains, but it must be absolutely minimized and, for that to be possible, we must guard against the acquisition of unwarranted influence by its beneficiaries. If credibly neutral execution is subverted by privileged orderflow, cartelized builders, trusted relays, opaque routing, or validators outsourcing into a narrow supply chain, Ethereum will look permissionless while users experience it as intermediated at the moment value moves. EF protocol work will therefore prioritize lower barriers to block building and validation, stronger inclusion guarantees, reduced extraction opacity, competitive transaction pipelines, user-facing legibility of trust assumptions, and more aggressively exploring the open orderflow solution space. None of this is simple. A good solution in one place can aggravate problems elsewhere. FOCIL is good for censorship resistance, but it may introduce more cross-block MEV. While ePBS solves the relayer trust problem, we must make sure that its implementation does not inadvertently obstruct long-term solutions to even larger problems. It would be unacceptable, for example, if ePBS enshrining the builder economy ends up making it harder to reduce reliance on the private orderflow that has emptied out the public mempool. Encrypted mempools may not only reduce pre-execution transparency and pending orderflow visibility, but also shift competitive advantage to new privileged actors, including specialized hardware operators in some designs, while adding protocol complexity. In order to avoid wasting time playing whack-a-mole, we must commit to solving the extraction problem at a whole system scale. Doing so will require creativity, courage, and the understanding that failure to solve this problem is unacceptable. If we fail, we will have left in place an unnecessary barrier to institutional adoption, but, more importantly, we will also have surrendered a core part of the promise of Ethereum - the replacement of extractive middlemen with permissionless, credibly neutral infrastructure and competitive markets. That must not happen. MEV is likely to be the next major front in the cypherpunk war. We must set ourselves up to win here. Privacy is just as fundamental. A public ledger without serious privacy defaults is a surveillance substrate with settlement guarantees. That is not an acceptable end state for the world computer. Unconditional privacy will be readily available across Ethereum, with programmability on top for selective disclosure, proofs, auditability, compliance logic, reputation, governance, identity, and other constraints chosen by users and their communities. The temporal order matters: unconditional privacy must exist first, opt-in constraints come second. It is also important to avoid forcing users to assemble a fragile stack of special wallets, RPCs, bridges, apps, compliance providers, and operational habits to attain privacy. Deep privacy must be more secure than this. Privacy is a condition for Ethereum’s viability as freedom-respecting coordination infrastructure and as such must be robust. Staking must be treated as protocol infrastructure risk. Staking is not merely a yield product, and liquid staking is not merely an app-layer market. If stake, liquidity, validator access, DeFi collateral, and governance influence concentrate around a small set of issuers or operators, Ethereum’s security layer becomes vulnerable to capture through capture of the economic layer around it. EF will support research, specifications, and designs that keep staking permissionless, private where possible, plural in operation, and resistant to intermediaries becoming permanent control points. The access interfaces are where users access either the protocol directly or through intermediated defaults. The primary problem to solve here is not getting Ethereum into more rooms directly, but making its users, both end users and institutions, more self-sovereign and less susceptible to coercion, and avoiding normalization of soft coercion in exchange for reach. EF will not help Ethereum become more acceptable by sanding off the properties that make it uniquely valuable. Ethereum does not need to become another permissioned settlement backend with better branding. It needs to show, in production, that self-sovereign coordination at scale is possible. Across Ethereum, the EF’s defensive work seeks to ensure that Ethereum is infrastructure people can still use when counterparties fail, platforms censor, governments overreach, intermediaries extract, and coordination problems become infeasible for trusted systems to handle. A core part of that is to make that infrastructure secure and robust against capture at every layer wherever capture opportunities can hide. 4. What the EF is also for: Seizing opportunities Shoring up the fundamentals is not enough. Ethereum’s potential is still largely unrealized, but that does not mean that the path ahead is going to be straight. Opportunities must be seized when the time is right. At this moment in time, a number are visible, including: * Ethereum becoming the first quantum-resistant global infrastructure. Ethereum researchers will lead the post-quantum cryptographic migration before the threat becomes urgent, not after it becomes a governance emergency. That means hardening Ethereum’s cryptographic foundations while there is still time to design carefully. The same applies to other long-horizon risks, where waiting for market demand means waiting until the window for principled design has already closed. * Verifiably self-sovereign stack, from soup to nuts, whether local or remote, with no censorship or extraction openings: browsers, wallets, intents, broadcasts, orderflow, inclusion, block construction, proposal, proving, exit, and recovery. Minimal MEV, and zero toxic MEV entrenchment, either in or around the protocol. No execution layer that is formally permissionless but practically gatekept by privileged supply chains. If there’s a funnel towards an extractive private lane, there’s other options that keep the game live. The goal is not only to prevent extraction or capture, but to make credibly neutral execution competitive enough that serious users prefer it. * Making ETH normal digital cash: a private, dignity-respecting, debasement-resistant and surveillance-resistant medium of exchange and store of value, as well as the native asset of private computation and private coordination for both humans and their agents. If Ethereum can make private economic life and private institutional life possible without routing users back through the friction and potential abuse of custodians, surveillance vendors, or permissioned ledgers with softer branding, as well as provide a venue for secure and competitive machine economics, the value unlocks will be immense. * Personal wallets with personal AI agents that users can actually own and run on their own personal computers. Not your keys, not your coins; not your model, not your mind. As agents become interfaces for more economic and social action, the question of who owns the wallet, the model, the memory, the policy, and the signing authority becomes an existential question about sovereignty instead of UX details - we are all users above any other roles, and no one at EF will forget this. * Institutional and enterprise use cases where Ethereum wins by not disappearing into an invisible backend, gatekept by intermediaries or terrible UX, and by not compromising into a compliant fintech rail with web3 branding. Rather, we will win through proving that credibly neutral infrastructure can handle disintermediated coordination so competitively that trusted intermediaries have to meet Ethereum users on Ethereum’s terms. * Security-preserving scaling. L2s and related infrastructure will be able to meet institutional-level needs without accepting dependencies on closed operators, opaque sequencing, custodial UX, or upgrade committees that users cannot realistically exit. Scale is not throughput alone. Scale is the guaranteed availability of self-sovereignty under real load. We are ensuring Ethereum remains the hardest bedrock for settlement, local and worldwide; and beyond that, a civilizational ledger and execution substrate to stand the test of time. When future civilizations speak of the infrastructure they inherited from the Antiquity of the Information Age, their first example should be Ethereum. Ethereum will outlast all of us. More than enough people watching understand this. Many wondered why it needed saying at all, but it did. If you don't believe us or don't get it, we don't have time to try to convince you, sorry. 5. Addressing departures There has been a lot of online speculation about departures from EF, both before and after the mandate. Some people resigned, others were terminated. Some departures were about strategy, some about role fit, some about normal institutional change, and some simply about people deciding that their best work for Ethereum should happen somewhere else. We will not litigate individual personnel matters on Twitter. That is the default because it is better for EF, better for the people involved, and better for Ethereum. People who contributed through EF deserve dignity on the way out. They do not deserve to have their employment history turned into factional content. Where possible, we have let people describe their departures in their own words as a matter of courtesy, and not concession. If public claims materially mislead people about EF’s direction, decision-making, or mandate, we may correct the record at the level of policy, process, and institutional facts. We still will not turn personal files into public spectacle. Ethereum is permissionless. People may disagree, criticize, compete, fork, and build elsewhere. We intend to keep exits dignified and expect others to do the same. It will suffice to say that we are thankful for what all contributors have built; we will continue to do work Ethereum needs. 6. Addressing EF spinouts Some work should and will leave the EF in the months to come. We hope and expect this process to result in some excellent work being done in service of scaling self-sovereign adoption, but we also must take care lest it becomes an abdication of responsibility or an excuse for undisciplined spending. Some work is not mandate-compatible and should not be carried forward with EF funds or EF endorsement, either inside or outside the Foundation. The efforts carried out by the spinouts will vary widely. Some efforts will leave EF because another org would be a better home for them; others will leave because markets should decide on their worth. Some will leave because they are not compatible with the direction set out in the mandate; others because they are useful but not EF work. Just as a spinout is not automatically good because it reduces EF headcount, former EF affiliation is not a claim on EF funding. The question we ask when deciding on funding is not “did this come from the EF?” But, rather the questions that should be asked about all external funding: “Is this work mandate-critical? Would the EF do this work internally if it had the organizational and financial capacity? Is there no better natural home? Can the external party execute without increasing capture risk, private extraction, opacity, or dependence? Does supporting it reduce Ethereum’s dependence on the EF over time, without prematurely transferring resources and legitimacy to new organizations and thereby risking operational failure or mission drift?” EF funding for work being done externally can be appropriate when it is a capacity solution for mandate work - work the EF should responsibly want done; work that protects CROPS; work that advances self-sovereignty and scales it; essential work that no actor can or will reliably do without EF funding; and work that can be scoped, reviewed, and held accountable without creating a permanent dependency. Such funding is not appropriate when it is a lazy continuity payment, a friendship payment, a reputational hedge, a way to avoid making a hard decision, or a way to support work that is not compatible with the mandate. EF has finite funds, finite legitimacy, and a specific mandate. We will spend all three as if they matter. When we say “EF is one of many nodes”, we mean that we intend to be one of many nodes working to keep self-sovereignty and its scaling the North Star, and working to keep CROPS the undisplaceable first-class properties of the network. We don’t mean that we will support orgs or projects with different priorities. Diversity that leads to ecosystem resilience, coordination cost right-sizing, and better decision-making is good. Diversity that leads to mission drift is not. We are not neutral on the direction Ethereum takes. CROPS are not just things we “believe in”, they are characteristics we understand must be thoughtfully prioritized at every fork for Ethereum to realize its potential. We are partisans for and builders of something of such incredible neutrality that it will fundamentally reshape the world we live in; we wish to work with everyone committed to this shared purpose.
English
171
303
1.3K
377.5K
fara.eth retweetledi
AntChain OpenLabs
AntChain OpenLabs@AntChainOpenLab·
zkDTVM v0.6.2 is live on @eth_proofs: Proof size < 600KB while performance remains largely unchanged. Highlights: 🔹Path-Pruned FRI Verification 🔹Template-Clone Parallel Compilation 🔹FRI Early Termination 🔹Batched Witness Reads + Constant Deduplication
English
0
2
11
495
fara.eth retweetledi
Will Corcoran
Will Corcoran@corcoranwill·
There's a new chapter starting for the Protocol cluster. We're welcoming new leads and coordinators, and continuing our work toward Glamsterdam, Hegotà, and the Strawmap. More in the blog below 👇
English
96
48
392
153.7K
fara.eth retweetledi
Thomas Coratger
Thomas Coratger@tcoratger·
What if the final form of software development for zkVMs bypasses Rust, C, and compilers entirely? @pirapira from @zksecurityXYZ argues that combining raw RISC-V Assembly, Lean4, and AI agents is the ultimate path to bug-free zkVMs. Bullish on this approach since Cannes. 🧵👇
English
2
9
66
3.6K
fara.eth retweetledi
ethrex
ethrex@ethrex_client·
We've integrated @zksync's Airbender as a new proving backend for @ethrex_client on @eth_proofs! The average proving time is ~40s with a single GPU, achieving 14s in some blocks! These are our fastest zkVM proving times to date, and there's still much room for improvement. Thanks to the @zksync team for the great work on Airbender.
ethrex tweet media
English
5
17
75
11.5K
fara.eth retweetledi
ladislaus.eth
ladislaus.eth@ladislaus0x·
Why does L1-zkEVM need Block-in-Blobs (EIP-8142), even for optional proofs? zkEVM unlocks significantly higher gas limits. But without BiB, validators must still download full payloads to confirm tx data was published, even though zkEVM proofs already guarantee execution correctness. Today that's not a problem: data availability is implicit, because validators download & execute every tx anyway. zkAttesters break this coupling, and without BiB there would be proof-verified execution but no DA guarantee; an incomplete migration that removes the re-execution burden but preserves the download burden, scaling linearly with the very gas limits zkEVM is supposed to unlock. BiB closes the loop by encoding tx data into blobs that can be cryptographically verified without downloading them in full. Initially, validators may still download all payload blobs, but the data is now in a format that enables DAS for payload data eventually. That is when the gas limit can truly grow without proportionally growing every validator's bandwidth.
Toni Wahrstätter ⟠@nero_eth

One thing I learned over the past year: zkEVMs don’t just scale computation. If you pair them with blobs + DAS and you start scaling data too. With EIP-8142 (block in blobs), execution payloads move into blobs, and validators no longer need to download everything, they can sample data and still get the required availability guarantees. That's super powerful! h/t @kevaundray and @TauLepton_ for teaching me! More info im the post below.

English
3
14
53
7.9K
fara.eth retweetledi
Thomas Coratger
Thomas Coratger@tcoratger·
Two landmark papers from @Google & @TeamOratomic just shattered our timelines for Q-day (when quantum computers break crypto). Q-day might be closer than we think. Here is a breakdown of @nic_carter's latest analysis. 🧵👇
English
1
7
23
1.6K
Chamath Palihapitiya
Chamath Palihapitiya@chamath·
In today’s episode of “Clapping as a Strategy”, this is probably nothing for crypto.
Chamath Palihapitiya tweet media
English
103
20
297
105.2K
fara.eth
fara.eth@fbwoolf·
@leanEthereum is on this, don't worry.
Justin Drake@drakefjustin

Today is a monumentous day for quantum computing and cryptography. Two breakthrough papers just landed (links in next tweet). Both papers improve Shor's algorithm, infamous for cracking RSA and elliptic curve cryptography. The two results compound, optimising separate layers of the quantum stack. The results are shocking. I expect a narrative shift and a further R&D boost toward post-quantum cryptography. The first paper is by Google Quantum AI. They tackle the (logical) Shor algorithm, tailoring it to crack Bitcoin and Ethereum signatures. The algorithm runs on ~1K logical qubits for the 256-bit elliptic curve secp256k1. Due to the low circuit depth, a fast superconducting computer would recover private keys in minutes. I'm grateful to have joined as a late paper co-author, in large part for the chance to interact with experts and the alpha gleaned from internal discussions. The second paper is by a stealthy startup called Oratomic, with ex-Google and prominent Caltech faculty. Their starting point is Google's improvements to the logical quantum circuit. They then apply improvements at the physical layer, with tricks specific to neutral atom quantum computers. The result estimates that 26,000 atomic qubits are sufficient to break 256-bit elliptic curve signatures. This would be roughly a 40x improvement in physical qubit count over previous state-of-the-art. On the flip side, a single Shor run would take ~10 days due to the relatively slow speed of neutral atoms. Below are my key takeaways. As a disclaimer, I am not a quantum expert. Time is needed for the results to be properly vetted. Based on my interactions with the team, I have faith the Google Quantum AI results are conservative. The Oratomic paper is much harder for me to assess, especially because of the use of more exotic qLDPC codes. I will take it with a grain of salt until the dust settles. → q-day: My confidence in q-day by 2032 has shot up significantly. IMO there's at least a 10% chance that by 2032 a quantum computer recovers a secp256k1 ECDSA private key from an exposed public key. While a cryptographically-relevant quantum computer (CRQC) before 2030 still feels unlikely, now is undoubtedly the time to start preparing. → censorship: The Google paper uses a zero-knowledge (ZK) proof to demonstrate the algorithm's existence without leaking actual optimisations. From now on, assume state-of-the-art algorithms will be censored. There may be self-censorship for moral or commercial reasons, or because of government pressure. A blackout in academic publications would be a tell-tale sign. → cracking time: A superconducting quantum computer, the type Google is building, could crack keys in minutes. This is because the optimised quantum circuit is just 100M Toffoli gates, which is surprisingly shallow. (Toffoli gates are hard because they require production of so-called "magic states".) Toffoli gates would consume ~10 microseconds on a superconducting platform, totalling ~1,000 sec of Shor runtime. → latency optimisations: Two latency optimisations bring key cracking time to single-digit minutes. The first parallelises computation across quantum devices. The second involves feeding the pubkey to the quantum computer mid-flight, after a generic setup phase. → fast- and slow-clock: At first approximation there are two families of quantum computers. The fast-clock flavour, which includes superconducting and photonic architectures, runs at roughly 100 kHz. The slow-clock flavour, which includes trapped ion and neutral atom architectures, runs roughly 1,000x slower (~100 Hz, or ~1 week to crack a single key). → qubit count: The size-optimised variant of the algorithm runs on 1,200 logical qubits. On a superconducting computer with surface code error correction that's roughly 500K physical qubits, a 400:1 physical-to-logical ratio. The surface code is conservative, assuming only four-way nearest-neighbour grid connectivity. It was demonstrated last year by Google on a real quantum computer. → future gains: Low-hanging fruit is still being picked, with at least one of the Google optimisations resulting from a surprisingly simple observation. Interestingly, AI was not (yet!) tasked to find optimisations. This was also the first time authors such as Craig Gidney attacked elliptic curves (as opposed to RSA). Shor logical qubit count could plausibly go under 1K soonish. → error correction: The physical-to-logical ratio for superconducting computers could go under 100:1. For superconducting computers that would be mean ~100K physical qubits for a CRQC, two orders of magnitude away from state of the art. Neutral atoms quantum computers are amenable to error correcting codes other than the surface code. While much slower to run, they can bring down the physical to logical qubit ratio closer to 10:1. → Bitcoin PoW: Commercially-viable Bitcoin PoW via Grover's algorithm is not happening any time soon. We're talking decades, possibly centuries away. This observation should help focus the discussion on ECDSA and Schnorr. (Side note: as unofficial Bitcoin security researcher, I still believe Bitcoin PoW is cooked due to the dwindling security budget.) → team quality: The folks at Google Quantum AI are the real deal. Craig Gidney (@CraigGidney) is arguably the world's top quantum circuit optimisooor. Just last year he squeezed 10x out of Shor for RSA, bringing the physical qubit count down from 10M to 1M. Special thanks to the Google team for patiently answering all my newb questions with detailed, fact-based answers. I was expecting some hype, but found none.

English
0
0
2
59
fara.eth
fara.eth@fbwoolf·
Ethereum Foundation@ethereumfndn

Today, several teams at the EF are launching pq.ethereum.org, a dedicated resource for Ethereum's post-quantum security effort. What started with early STARK-based signature aggregation research in 2018 has grown into a coordinated, multi-team effort, all open source. The Post-Quantum team and Cryptography teams, with help from the Protocol Architecture and Protocol Coordination teams, have been working on this body of work for 8+ years. At pq.ethereum.org you'll find: - How PQ impacts each protocol layer - The full PQ roadmap (strawmap.org) - Open resources: repos, specs, papers, EIPs - FAQ: 14 questions across 5 categories, written by the PQ team - A 6-part lean Ethereum interview series (@zeroknowledgefm) - Interest form for the 2nd Annual PQ Research Retreat (Cambridge, UK, Oct 2026) - 10+ client teams are already building and shipping devnets weekly through PQ Interop. All the work is public and all of it is open. pq.ethereum.org

ZXX
0
0
1
114
fara.eth
fara.eth@fbwoolf·
11/ If you care about crypto’s long-term survival (and evolution), check out Post-Quantum Ethereum: pq.ethereum.org
English
1
0
1
53
fara.eth
fara.eth@fbwoolf·
1/ Quantum computing isn’t sci-fi anymore. @drakefjustin lays out a credible timeline to “Q-Day” — the moment quantum machines can break today’s cryptography. Estimate: ~2032. That’s not far away. 🧵
English
7
8
29
1.3K