or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Syncing
xxxxxxxxxx
Optimistic Sync Homepage
In lighthouse#2691 we discuss the need for "optimstic sync" for post-merge consensus clients (a.k.a. eth2 clients). That issue establishes the need for optimistic sync and presents some of the unanswered questions that surround it.
This document follows from lighthouse#2691 to provide a "homepage" for research into optimistic sync in Ethereum consensus clients.
The status-quo
Optimistic Sync: How many heads? defines four different types of heads we can track in optimistic sync:
That document establishes that (1, 2) are simple-enough to implement, but (3, 4) are complex enough to strike fear in the hearts of client developers.
Optimistic Sync: Which is the right head for the job? then goes to enumerate all the components in a consensus client and aims to specify their behavior when the head of the beacon chain does not yet have a verified
ExecutionPayload
.Implementation requirements
If the assumptions in this document are correct, consensus clients need to make the changes along the lines of:
SYNCING
.ProtoArray
to indicate if that block is: verified, yet-to-be-verified, invalid or irrelevent (pre-merge).ExecutionPayload
.status
RPC method to present the verified ancestor head when the optimistic head has an unverified payload.Known Issues
Resources