Commit bc10b10d authored by 0xYYY's avatar 0xYYY

doc: set ordered list index to 1

parent ed31c640
...@@ -58,7 +58,7 @@ byte sequence. The first version has `0x00` as the version byte and then as the ...@@ -58,7 +58,7 @@ byte sequence. The first version has `0x00` as the version byte and then as the
[EIP-2718]: https://eips.ethereum.org/EIPS/eip-2718 [EIP-2718]: https://eips.ethereum.org/EIPS/eip-2718
- `bytes32 sourceHash`: the source-hash, uniquely identifies the origin of the deposit - `bytes32 sourceHash`: the source-hash, uniquely identifies the origin of the deposit.
- `address from`: The address of the sender account. - `address from`: The address of the sender account.
- `address to`: The address of the recipient account, or the null (zero-length) address if the - `address to`: The address of the recipient account, or the null (zero-length) address if the
deposited transaction is a contract creation. deposited transaction is a contract creation.
......
...@@ -63,10 +63,10 @@ liveness, availability, and validity. ...@@ -63,10 +63,10 @@ liveness, availability, and validity.
- There are two ways transactions can be sent to the rollup chain: 1) via the sequencer, and 2) directly on layer 1. - There are two ways transactions can be sent to the rollup chain: 1) via the sequencer, and 2) directly on layer 1.
The sequencer provides low latency & low cost transactions, while sending transactions directly to layer 1 provides The sequencer provides low latency & low cost transactions, while sending transactions directly to layer 1 provides
censorship resistance. censorship resistance.
2. **Availability** - Anyone must be able to download the rollup chain. 1. **Availability** - Anyone must be able to download the rollup chain.
- All information required to derive the chain is embedded into layer 1 blocks. That way as long as the layer 1 - All information required to derive the chain is embedded into layer 1 blocks. That way as long as the layer 1
chain is available, so is the rollup. chain is available, so is the rollup.
3. **Validity** - All transactions must be correctly executed and all withdrawals correctly processed. 1. **Validity** - All transactions must be correctly executed and all withdrawals correctly processed.
- The rollup state and withdrawals are managed on an L1 contract called the `L2 State Oracle`. This oracle is - The rollup state and withdrawals are managed on an L1 contract called the `L2 State Oracle`. This oracle is
guaranteed to _only_ finalize correct (ie. valid) rollup block hashes given a **single honest verifier** assumption. If guaranteed to _only_ finalize correct (ie. valid) rollup block hashes given a **single honest verifier** assumption. If
there is ever an invalid block hash asserted on layer 1, an honest verifier will prove it is invalid and win a bond. there is ever an invalid block hash asserted on layer 1, an honest verifier will prove it is invalid and win a bond.
......
...@@ -72,4 +72,4 @@ The input and return types here are as defined by the [engine API specs][engine- ...@@ -72,4 +72,4 @@ The input and return types here are as defined by the [engine API specs][engine-
OR `String` - one of `"safe"`, `"latest"`, or `"pending"`. OR `String` - one of `"safe"`, `"latest"`, or `"pending"`.
- returns: - returns:
1. `version`: `DATA`, 32 Bytes - the output root version number, beginning with 0. 1. `version`: `DATA`, 32 Bytes - the output root version number, beginning with 0.
2. `l2OutputRoot`: `DATA`, 32 Bytes - the output root. 1. `l2OutputRoot`: `DATA`, 32 Bytes - the output root.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment