Crystality & PREDA | Parallel EVM Runtime

270 posts

Crystality & PREDA | Parallel EVM Runtime banner
Crystality & PREDA | Parallel EVM Runtime

Crystality & PREDA | Parallel EVM Runtime

@PREDALang

Parallel Relay-and-Execution Distributed Architecture designed to scale out smart contracts [email protected]

Deterministic Parallel VM Katılım Ocak 2023
32 Takip Edilen296 Takipçiler
Sabitlenmiş Tweet
Crystality & PREDA | Parallel EVM Runtime
New benchmark report for Crystality-REVM — Deterministic State Parallelism now LIVE for REVM users @base, @OPLabsPBC, & @Scroll_ZKP. ⚡️Higher concurrency, near-linear scaling. Six representative Solidity contracts tested on 1–64 cores, compared against high-performance chains like Sui , Aptos , & Sei. Full report + test suites: github.com/preda-devteam/… — download and reproduce the benchmarks. A 🧵👇
Crystality & PREDA | Parallel EVM Runtime@PREDALang

Crystality's now live for Reth/REVM The PREDA parallel execution runtime evolves with each expansion

English
1
1
1
898
Crystality & PREDA | Parallel EVM Runtime
One step closer to CROPS, EIP-8182 a protocol-managed private transfer layer introducing a shielded pool where transactions are globally invisible
Crystality & PREDA | Parallel EVM Runtime tweet media
English
0
0
1
16
Crystality & PREDA | Parallel EVM Runtime
Lean EF makes sense. Degoverning Ethereum is genuinely one of the core challenges. On CT people are still very used to pointing at one figure for both praise & criticism. The world has rarely seen a largescale decentralized system operate successfully for decades with low friction. (btc's closed while having plenty of frictions) This is still the very early stage of a real experiment. We’re in.
vitalik.eth@VitalikButerin

Some of my perspective on where the @ethereumfndn is going. First of all, this is only my own view. The board is not just me, and I have no extra special powers on the board that the other board members do not. @aerugoettinea is the one executing much of this transition. My input has been largely on technical questions. The board is in the process of expanding, and my own power within the org will continue to decrease, which is honestly what I want. The 2025 era brought many important improvements to EF and its ability to execute. Many issues were resolved, and EF continues to benefit from its improved efficiency and greater focus on concrete goals to this day. And so with those problems resolved, early this year, the largest remaining hole that I perceived was something different nagging at me: I would regularly spot people saying things like "vitalik says these beautiful things about ethereum needing to be decentralized, and have privacy, and be a sanctuary technology, but why do the EF's actions not reflect that?" Now, you may have been hearing something different. You may not have been sensing a feeling of crisis at all, and maybe were hearing people saying that finally we were taking execution and BD seriously and the main task for us is to keep going that way and be even better and faster. Then probably there is genuine difference between you and me, in what kinds of criticism I take most seriously, and what kinds of critics through their criticism are most able to make me feel pain. As an analogy, let's briefly switch over to a different domain. One belief you can have about Google is that it is a success story, and has brought a lot of good to humanity in organizing the world's information. Another belief you can have about Google is that they had a beautiful idealistic beginning, but at some point the corruption of mainstream corporate attitudes seeped in, and they slowly bit by bit completely abandoned the "don't be evil" slogan. My belief on Google specifically is probably somewhere between the two. BUT, if you had taken me back in time to ~2008, and offered me a button to press to make Google one or two standard deviations more "dogmatic", eg. give Richard Stallman permanent veto power over some key policies, I would immediately press it. Why? Because a choice for one company is not a choice for the world, or even one country. Google existed and exists in the context of a technology industry generally drifting away from early idealistic don't-be-evil roots and toward greed for financial gain, totalizing visions of accelerated superintelligence, infiltration by sociopaths, and craven capitulation to (or worse, active participation in) government pressure for ideological control, surveillance and war. And so *one company* doing something different, positioning itself to be what George Bernard Shaw calls the Unreasonable Man, resisting the trend of the times, would have been better for freedom, balance of power and stability of society as a whole, than *all* large companies bending to dominant trends. This is a part of my version of pluralism. This line of thinking is not just mine, but I also is not too far off from what Aya and others had in mind with the Mandate. Now how does this all get to the role of the EF? EF is not a "center of Ethereum", rather EF is "one node, with a defined purpose, alongside other nodes". We've always said that the EF should be the latter, but many in the Ethereum ecosystem (and even within the EF) wanted us to be the former. Now, we are taking action to ensure that we will be the latter. This is particularly important because EF is a limited organization, with limited resources and limited organizational capacity. The EF has only ~0.16% of all ETH (less than many other individual ETH holders), whereas among other blockchains it's common for "the central foundation" to have 10-50%. Fiscally, the EF was originally designed to fulfill a limited work scope defined in the token sale docs and other pre-launch materials (building the chain software; getting through Frontier, Homestead, Metropolis, Serenity), which was fully completed in 2022; it was not designed to be an eternal steward. And so today, the EF is choosing to use its remaining resources to pursue longevity over breadth (yes, this means we sell less ETH). The EF focuses *specifically* on those activities critical to the success of ethereum as a censorship/capture-resistant, open, private and secure system, that would not happen otherwise. This means making hard choices, and in some cases even activities that we highly approve of and people that we highly respect becoming outside of the EF. People of great technical talent, public respect and even alignment with the mission and CROPS being outside of the EF is in fact necessary if we want important tasks to be able to attract outside capital. This also means the EF taking opinionated stands culturally. This is all intended in cooperation with all other parts of ethereum. We recognize that many other parts of the ethereum world highly respect CROPS and related values. But highly respecting is not the same as choosing to specialize and totally dedicate to a domain (Compare in a different domain: I think reducing animal cruelty is important, and I like vegan food, but am not full unconditional vegan myself) EF is still in a transition period, and we expect its new long-term form to stabilize over the next few months. What are the guiding principles of this new form? Again, I am only one person, but I can give my answer from a technical perspective (there are also critical non-technical aspects). At the core, *Ethereum must be impressive*. We are living in an age of highly intelligent AI and all kinds of other technological acceleration. "Status quo EVM, with a hard fork or two a year to optimize for short-term needs of users" is not interesting. To some, "impressive" means: 250ms latency and 1M TPS. I think Ethereum trying to go that route is a mistake. Being as fast and as scalable as possible, and only a small epsilon more decentralized than the others, is a route to mediocrity, and if we try it we will lose. I think Ethereum should scale. But I think Ethereum should strive the hardest to be deeply impressive in a different dimension: the CROPS dimension. This means things like: * Provably bug-free Ethereum. This is a goal that all cybersecurity researchers would have thought is absurd and impossible, up until roughly 6 months ago. Now, it's on the cusp of being possible, thanks to AI-assisted formal verification. So we should be frontrunners in doing this. * Available chain consensus. Ethereum is, and with lean consensus will cotninue to be, the ONLY chain that has both (i) traditional-BFT style properties that it's safe under asynchrony up to a high level of fault tolerance, and (ii) the bitcoin PoW-style property that under synchrony it's safe up to 49% attackers. As far as I can tell, literally no other chain has this or is planning for it; bitcoin goes for (ii) only and most other chains go for (i) only. Some will remember I fought hard for this, Unreasonably insisting that it is not OK for ethereum to rely on social consensus and hard forks to rescue ethereum from 34% of nodes going offline. It's OK for chains like hyperledger, bnb, solana, tempo, etc. It's not OK for bitcoin or ethereum or eg. zcash. * Intermediary minimization. The fact that smart contract wallets, protocols like railgun, etc have to send transactions through intermediaries to get included onchain is honestly embarrassing, and it's a constant point of fragility. Hence the work on FOCIL and EIP-8141 (and 7701 and years of work before) to make transaction sending intermediary-minimized with public mempool and strong inclusion properties, in a truly general-purpose way, that covers not just eg. secp256r1, but also privacy protocols and much more. Kohaku is pushing intermediary minimization at the user layer, pulling Ethereum away from the dystopian status quo world where our wallets don't even verify the chain, send our private data out to a dozen third-party servers, and toward a brighter CROPS future. Some of these goals are Unreasonable - maybe Ethereum would be "fine" getting only 50% of the way - what if we depend on intermediaries, but make it easy to switch? But going 50% of the way would not make Ethereum Deeply Impressive in the CROPS way. So we push for 100%. Fortunately all these goals are compatible with high TPS, this is a major focus of research (esp. on scaling the state). Well-designed L2s can also help, especially L2s optimized for specific applications (eg. high-volume trading, privacy...). These goals are even compatible with significantly lower slot times, thanks to Raul's work on erasure-coded P2P, and many other optimizations. The most high-value "product" of the ethereum blockchain, financially speaking, is ETH the asset. Ethereum secures $250 billion of ETH. The types of properties of Ethereum that I mentioned above are very good for ETH the asset. Nearly 90% of my net worth is in ETH, and most of the remainder is ~$40m of onchain fiat of which every dollar has already been allocated for some open-source biotech or software or hardware initiative. That said, there are aspects of supporting ETH the asset - *necessary* aspects even - that are outside the scope of the EF. This is where we need other heroes (some of whom hold more ETH than the EF does) to step in and help. EF has been recently thinking more about how it will relate to other such organizations, and give them needed initial support. EF will be a smaller ship than in previous years, a more opinionated one - in some cases more opinionated in ways that might be difficult to comprehend - but a longer-lasting one, and one suited to making sure that ethereum brings something meaningful to the world. We are grateful to all those inside and outside the EF who are helping to make this happen.

English
0
0
0
20
Crystality & PREDA | Parallel EVM Runtime retweetledi
Token Terminal 📊
Token Terminal 📊@tokenterminal·
Ethereum is losing the race among L1s.
Token Terminal 📊 tweet media
English
78
60
512
125.3K
Crystality & PREDA | Parallel EVM Runtime retweetledi
Toni Wahrstätter ⟠
Ethereum is about to fundamentally change how blocks are executed. With the upcoming Glamsterdam hardfork, it's shipping EIP-7928: Block-level Access Lists, a proposal that brings parallelization to the EVM. Here's a short explainer of what it is, how it works, and why it's a big deal for scaling. Let's start from the top. Alongside EIP-7732 (ePBS), EIP-7928 is the execution-layer (EL) headliner for Glamsterdam. Like ePBS, the main focus has been scaling Ethereum, though both proposals come with a bunch of other, equally important properties on the side e.g. removing trust requirements from the PBS pipeline or improving sync. EIP-7928 adds a Block Access List (BAL) to every Ethereum block. A BAL is a list of accounts and storage slots that the block touches, but that's not all: it also contains post-transaction state diffs (this part is critical!). Post-transaction state diffs tell you what the state looks like after each transaction. Quick example: user A swaps 1 ETH for DAI on DEX B. The BAL tells you that user A's ETH balance decreased by 1 ETH + tx fees and their nonce went up by 1; that DEX B's ETH balance went up by 1 ETH; and that inside the DAI contract, user A's DAI balance increased while DEX B's decreased. In other words, all of that info becomes statically available, something that previously required tracing the transaction. Client software (Geth, Nethermind, Besu, Erigon, Reth, Ethrex, Nimbus) can use this to do a few very powerful things: 1. Parallelize transaction execution. Knowing the post-state of each tx resolves the dependencies between them. No transaction has to wait on the previous one anymore, so execution can be perfectly parallelized. Instead of large parts of block validation sitting idle waiting on sequential execution, clients can finally make much better use of modern hardware. 2. Batch prefetch. One of the most cumbersome jobs for a node has been fetching the state needed for execution from disk. Because state locations (e.g. the exact storage slot in the DAI contract where user A's balance lives) are only discovered along the way, while executing, state-fetching has been a real drag on scaling: it blocks execution, takes time, and eventually slows everything down. With BALs, everything a node needs for execution is known upfront and can be loaded into cache in one go, in parallel. This speeds things up even further. 3. Parallelize post-state root calculation. Another expensive task is walking the updated state tree to compute the post-state root, which is needed so that everyone agrees on what's on disk after executing the block. With the post-tx state already in the BAL, nodes can do this in parallel while executing. A heavy task that used to wait until all transactions had finished can now run alongside prefetching and execution. 4. Snap sync (v2). An often overlooked, less sexy aspect of blockchains is syncing. Nodes need to catch up with the chain, and they need to catch up faster than the chain progresses. Today, most nodes do snap sync: downloading blocks, headers, and state in parallel while chasing the tip, and then "healing" the database once they're close to the head. Healing means asking peers for trie nodes, receiving them, validating them, and updating the local DB. It's iterative, networking-heavy, can take a while, and especially higher throughput pushes that phase to its limits. BALs help here too: with snap v2, nodes can catch up to the tip and skip the healing phase entirely. Syncing at higher throughput becomes more robust and reliable. So, to summarize, a BAL contains two things: -> The state locations the block accesses -> The state changes after each tx (incl. the new values) We're already seeing big performance gains today: on 6-core machines, EL clients validate blocks up to 5x faster, making block gas limits of 300M a very realistic outcome. ePBS will add to that by decoupling the block from the payload, giving validators 2-4x more time for execution. To not overshoot (security stays priority #1), the fork will likely ship with a 200M gas limit, but we shouldn't be stuck there for long before pushing to 300M and beyond. That's a 10x in scaling since we started taking the topic seriously, without touching hardware requirements. None of this would have happened without people going all-in, heads down, shipping: so many hours spent in calls debating the right design, so many iterations refining the specs, and tons of test cases written (and still being worked on). The road from whiteboard to production-ready code has been a journey, and we're not at the finish line yet, but from what I can tell, things look super bullish for Ethereum. Glamsterdam will be a fork that shows what's possible when a distributed, decentralized community works on a shared goal, laser-focused on providing enough block space to onboard the next wave of users.
English
41
151
753
63.6K
Crystality & PREDA | Parallel EVM Runtime
We’d experimented with the Eth EL on GPU, Crystality-G, firslty introduced @0xETHRiyadh CuEVM has done important work in pushing EVM execution toward CUDA-compatible, massively parallel execution. Crystality-G shares this direction, but takes a different architectural path: deterministic parallelization at the txn state level. Crystality-G (SM-Level Parallelism) binds each parallel EVM instance to a dedicated Streaming Multiprocessor (SM) on the GPU. By assigning each instance its own global memory region and utilizing CUDA dynamic parallelism, the system attempts to maximize data locality . This design aims to reduce/eliminate state conflicts, rollback overhead, and coordination costs. Two graphics for a clearer view of scalability Crystality on GPU unlocks
Crystality & PREDA | Parallel EVM Runtime tweet mediaCrystality & PREDA | Parallel EVM Runtime tweet media
English
0
0
0
24
Crystality & PREDA | Parallel EVM Runtime retweetledi
Brendon (Jiaping)
Brendon (Jiaping)@Brendon_Jiapw·
For a reason too ridiculous to explain, I’m back on Twitter after five years. And apparently Twitter is X now. Hello World, again ~
Brendon (Jiaping) tweet media
English
1
2
4
258
Crystality & PREDA | Parallel EVM Runtime retweetledi
Nethermind
Nethermind@Nethermind·
No third-party bridge. No custodial risk. A user on an L2 swaps xDAI to USDC using a Sushiswap liquidity pool on Gnosis L1. The rollup accesses L1 liquidity natively and settles the result back to L2 in a single transaction. 15 seconds.
English
5
8
75
10.2K
Crystality & PREDA | Parallel EVM Runtime retweetledi
Base Build
Base Build@buildonbase·
Introducing Base Azul, our first independent network upgrade. Now live on Testnet with a targeted Mainnet release on May 13th.
Base Build@buildonbase

x.com/i/article/2046…

English
57
137
635
101.4K
raulk
raulk@raulvk·
confession: i keep a long-running Codex thread where i paste excellent Claude responses, then have Codex update its global AGENTS.md and a Claude Collaborator skill to behave more like that. it works.
English
3
0
7
861
Crystality & PREDA | Parallel EVM Runtime retweetledi
Toni Wahrstätter ⟠
Toni Wahrstätter ⟠@nero_eth·
txdelay.xyz is live. See how long Ethereum transactions wait on average to land on-chain. Let me provide some additional context: how the website works, what Glamsterdam (the next hardfork), in particular ePBS (EIP-7732), changes, and what this means for different stakeholders. With 12s slots, the average inclusion delay is ~6s. Shortening slot time reduces it. This number will increase by ~2s with ePBS, which is an unfortunate downside, degrading UX. Under ePBS, builders should wait until the beacon block committing to their payload has enough attestations before releasing it. Thus, ePBS has a similar effect to increasing slot time to 16s, and Ethereum would need ~8s slots just to get back to today’s inclusion delay. A similar effect applies to zkEVM provers: if provers are separate from builders, they effectively lose ~2s of proving time, delaying real-time proving and slowing down the rollout of zkEVMs. With shorter slots (e.g. 8s), this means provers would need to be ~25% faster. The data is sourced from @ethPandaOps’ Xatu nodes, comparing when transactions are first seen in the mempool vs when they are included in a block. It filters for transactions that can afford the base fee and pay at least $0.01 in priority fees. If you're a dApp builder, infra provider, zkEVM prover, exchange, power user, etc., I'd be curious how much every second of inclusion delay matters. Drop your thoughts in the comments or reach out via dm.
English
11
21
133
12K
Crystality & PREDA | Parallel EVM Runtime
1. From 30M to 300M: The Engineering Behind Ethereum’s Gas Li youtube.com/watch?v=0mmoUp… 2. Achieving 10 GigaGas/s EVM Execution with Block-Level Ac youtube.com/watch?v=a_t7VK… 3. How Ethereum Can Scale to Billions of Users youtube.com/live/fSpWyd4mK… 4. Competition through Spam on L2s youtube.com/watch?v=llZPzw… 5. Optimising Block Building with Genetic Algorithms youtube.com/watch?v=MNA3tA… (Still expanding this bucket 👀)
YouTube video
YouTube
YouTube video
YouTube
YouTube video
YouTube
YouTube video
YouTube
YouTube video
YouTube
English
0
0
0
56
Crystality & PREDA | Parallel EVM Runtime
** Not another ETHCC takeaway post @EthCC has been & will always be one of our fav tech conf, the ONE of the few places where we genuinely feel both "at home" & “in the zone.” We’ve been through a mix of talks & side convos, can usually tell within the first few slides: some talks are deeply crafted, others… came together a bit rushy If you're into scaling, benchmarks, and real numbers, we put together a heavily biased TALK MAP for ETHCC9. No fluff, no endings like“we’re making the world a better place” 🤣 👇👇👇
English
1
1
3
166
Crystality & PREDA | Parallel EVM Runtime retweetledi
EthCC - Ethereum Community Conference
Xiangru Ma (@PREDALang), a leading voice in blockchain scalability solutions, explores "Forget Private AMMs: Scaling DeFi Back Onchain with Parallel AMM" at the Built on Ethereum track. This could be the breakthrough that finally makes onchain DeFi trading competitive with centralized alternatives.
EthCC - Ethereum Community Conference tweet media
English
1
1
3
270