This means that in a chain running BOLD, anyone (yes, including you!) can fully participate in the rollup protocol, and if necessary submit challenges on Ethereum.
Jan 29, 2023 • 13 tweets • 2 min read
There's a narrative out there that ZK Rollups will be able to do everything that Optimistic Rollups do but better.
The way this story goes is that we're just waiting for ZK rollups to be ready, but as soon as they are, they win hands down.
Let me tell you why I disagree 🍿🧵
First, there's the fact that there is no zkEVM in production today. For the past few years, we've been perpetually told that it's 3-6 months away, but that never seems to get shorter.
Current indications also point to ZKRUs being more expensive and less compatible than ORUs.
Oct 16, 2022 • 5 tweets • 1 min read
I don’t know who needs to hear this, but here goes:
We are NOT 12 days away from the first zkEVM on mainnet in any meaningful way.
And anyone pushing this narrative is doing a disservice to the community 🧵
Here's the current state of zkEVM: lots of teams are making steady progress, but we're not ready for prime time by any means.
Unfortunately the race to be first is sometimes allowing marketing to take over.
This is dangerous ‼️
Jul 29, 2022 • 10 tweets • 2 min read
Some scattered thoughts on Arbitrum Nitro, zk-rollups, and plumbing 🧵
Our mission at Arbitrum is to scale Ethereum without compromising on security.
Notice that we're focused on the result, not the tool. On the end, not the means.
We're committed to develop and use the best tools available to carry out that mission.
Aug 29, 2019 • 8 tweets • 2 min read
If your Ethereum dapp is running into scalability issues, Arbitrum can help!
One common question that we get is how Arbitrum differs from other Layer 2 protocols. I've previously answered this for TrueBit, and today I'll do the same for state-channels
Arbitrum has two modes of operation: channels and chains.
Arbitrum channels are a drop in replacement for state-channels and are ideal for contracts that have a closed set of participants (e.g. a multiplayer game).
Jul 2, 2018 • 4 tweets • 3 min read
@nicolagreco@AFDudley0@paddyucl Right. The bisection protocol predates Truebit and we definitely don’t claim it as an innovation. Some of the differences between us and Truebit:
1. Our architecture guarantees small constant size one-step proofs. Truebit uses wasm which has no such guarantees.
@nicolagreco@AFDudley0@paddyucl 2. We have a complete stateful system. Our VMs are full operators in the system and can send/receive messages and money. TrueBit is a stateless system used to get the solutions to computations (and those solutions can in turn be used in a smart contract).