Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
  • Loading branch information
samajammin committed Nov 11, 2020
1 parent f17bce9 commit d96a53b
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions src/content/developers/docs/layer-2-scaling/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,22 +36,22 @@ Rollup solutions require relayers who have staked a bond in the rollup contract.

There are two types of rollups with different security models:

- Zero knowledge: runs computation off-chain and submits a <b>validity proof</b> to the chain
- Optimistic: assumes transactions are good and only runs computation, via a <b>fraud proof</b>, in the event of a challenge
- Zero knowledge: runs computation off-chain and submits a **validity proof** to the chain
- Optimistic: assumes transactions are valid by default and only runs computation, via a **fraud proof**, in the event of a challenge

### Zero knowledge rollups {#zk-rollups}

Zero knowledge rollups, also known as ZK-Rollups, bundle hundreds of transfers off-chain into a single transaction via a smart contract. From the data submitted, the smart contract can verify all of the transfers that are included. This is known as a validity proof.

With a ZK rollup, validating a block is quicker and cheaper because less data is included. You don't need all the transaction data to verify the transaction, just the proof.

The sidechain where ZK rollups happen have optimised a few things to reduce transaction size further. A user signs up and gets an index rather than an address... this reduces a transaction from 32 bytes to just 4 bytes.
The sidechain where ZK rollups happen can be optimised to reduce transaction size further. For instance, an account is represented by an index rather than an address, which reduces a transaction from 32 bytes to just 4 bytes.

### Optimistic rollups {#optimistic-rollups}

Optimistic rollups use a side chain that sits in parallel to the main Ethereum chain. They can offer improvements in scalability because they don't do any computation by default. Instead, after a transaction they propose the new state to mainnet. Or "notarise" the transaction.

As computation is the slow, expensive part of using Ethereum, this can offer up to 10-100x improvements in scalability dependent on the transaction. This number will increase even more with the introduction of the Eth2 upgrade: [shard chains](/en/eth2/#shard-chains). This is because there will be more data available in the event that a transaction is disputed.
As computation is the slow, expensive part of using Ethereum, this can offer up to 10-100x improvements in scalability dependent on the transaction. This number will increase even more with the introduction of the Eth2 upgrade: [shard chains](/en/eth2/shard-chains). This is because there will be more data available in the event that a transaction is disputed.

#### Disputing transactions {#disputing-transactions}

Expand Down

0 comments on commit d96a53b

Please sign in to comment.