From d858edb8658cfb86710a433a4cb61355d4b422e8 Mon Sep 17 00:00:00 2001 From: Ori Pomerantz Date: Wed, 1 Feb 2023 09:08:16 -0600 Subject: [PATCH] fix(specs): Lint --- specs/README.md | 4 ++-- specs/introduction.md | 2 +- specs/predeploys.md | 2 +- specs/proposals.md | 4 ++-- specs/rollup-node.md | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/specs/README.md b/specs/README.md index d837716f7673..e2ddf1805193 100644 --- a/specs/README.md +++ b/specs/README.md @@ -27,7 +27,7 @@ Our aim is to design a protocol specification that is: - **Fast:** When users send transactions, they get reliable confirmations with low-latency. For example when swapping on Uniswap you should see that your transaction succeed in less than 2 seconds. -- **Scalable:** It should be possible to handle an enormous number of transactions +- **Scalable:** It should be possible to handle an enormous number of transactions per second which will enable the system to charge low fees. V1.0 will enable Optimism to scale up to and even past the gas limit on L1. Later iterations should scale much further. @@ -44,7 +44,7 @@ Our aim is to design a protocol specification that is: systems team consuming the spec is also key! - **Secure:** This is self-evident. User’s assets are at stake. Every component of the system must be incredibly secure. -- **Decentralizable:** Optimism must be designed to avail itself of the security and +- **Decentralizable:** Optimism must be designed to avail itself of the security and censorship-resistant guarantees achieved by a decentralized system. Currently centralized components of the system should have a clear path towards decentralization. Already decentralized components of the system should be protected and preserved. diff --git a/specs/introduction.md b/specs/introduction.md index 3455e0dd6a5e..7bcdd16dba14 100644 --- a/specs/introduction.md +++ b/specs/introduction.md @@ -94,7 +94,7 @@ At the heart of the network are users (us!). Users can: The sequencer is the primary block producer. There may be one sequencer **or** many using a consensus protocol. For 1.0.0, there is just one sequencer (currently operated under the oversight of the Optimism Foundation). -In general, specifications may use "the sequencer" to be a stand-in term +In general, specifications may use "the sequencer" to be a stand-in term for the consensus protocol operated by multiple sequencers. The sequencer: diff --git a/specs/predeploys.md b/specs/predeploys.md index 6139bae56c44..1a0691614624 100644 --- a/specs/predeploys.md +++ b/specs/predeploys.md @@ -108,7 +108,7 @@ permissionlessly removed from the L2 supply by calling the `burn()` function. Address: `0x4200000000000000000000000000000000000002` -The `DeployerWhitelist` is a predeploy that was used to provide additional safety +The `DeployerWhitelist` is a predeploy that was used to provide additional safety during the initial phases of Optimism. It previously defined the accounts that are allowed to deploy contracts to the network. diff --git a/specs/proposals.md b/specs/proposals.md index b869941086eb..2c3b32c6c23c 100644 --- a/specs/proposals.md +++ b/specs/proposals.md @@ -26,8 +26,8 @@ proving any piece of data captured by the outputs. Proposers submit the output roots to L1 and can be contested with a fault proof, with a bond at stake if the proof is wrong. -_Note_: Fault proofs on Optimism are not fully specified at this time. Although fault proof construction and verification -[is implemented in Cannon][cannon], +_Note_: Fault proofs on Optimism are not fully specified at this time. Although fault proof +construction and verification [is implemented in Cannon][cannon], the fault proof game specification and integration of a output-root challenger into the [rollup-node][g-rollup-node] are part of later specification milestones. diff --git a/specs/rollup-node.md b/specs/rollup-node.md index 4dcd01a59f8a..a254c1798ea5 100644 --- a/specs/rollup-node.md +++ b/specs/rollup-node.md @@ -55,7 +55,7 @@ For a complete specification of the L2 block derivation, refer to the [L2 block ## L2 Output RPC method -The Rollup node has its own RPC method, `optimism_outputAtBlock` which returns a 32 +The Rollup node has its own RPC method, `optimism_outputAtBlock` which returns a 32 byte hash corresponding to the [L2 output root](./proposals.md#l2-output-commitment-construction). [SSZ]: https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md