Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update EIP-7542: modify eip-7542 wrong words to correct #8258

Closed
wants to merge 2 commits into from
+4 −4
Closed

Update EIP-7542: modify eip-7542 wrong words to correct #8258

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1e21672
wrong word check
t0m1sacat Feb 24, 2024
4173bfd
modify eip-7542 wrong words correct
t0m1sacat Feb 24, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions EIPS/eip-7542.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,8 +42,8 @@ Nodes must retain connections regardless of a peer's available block range, with
## Rationale

Including the available block range in the `eth` handshake allows for immediate understanding of peer capabilities. This can lead to more efficient networking as nodes can prioritize connections based on the data they need.
The new message types are introduced to allow nodes to reuqest updated available block range from other nodes since the range can change by the node syncing or pruning blocks.
Maintaining connections with peers that dont have the desired range ensures network resilience, while the exception facilitates efficient block sync under full peer capacity.
The new message types are introduced to allow nodes to request updated available block range from other nodes since the range can change by the node syncing or pruning blocks.
Maintaining connections with peers that don't have the desired range ensures network resilience, while the exception facilitates efficient block sync under full peer capacity.

## Backwards Compatibility

Expand All @@ -53,7 +53,7 @@ This EIP doesn't affect the consensus engine and doesn't necessitate a hard fork

## Test Cases

Testing will involve ensuring that nodes can correctly communicate and understand the block range information during the handshake. Additionally, it will involve ensuring nodes can correcly request and share updated block range when requested.
Testing will involve ensuring that nodes can correctly communicate and understand the block range information during the handshake. Additionally, it will involve ensuring nodes can correctly request and share updated block range when requested.

## Security Considerations

Expand Down
2 changes: 1 addition & 1 deletion _config.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ kramdown:
parse_block_html: false
# This is the default, but be explicit as some EIPs depend on it
auto_ids: true
# This is to ensure more determistic behaviour
# This is to ensure more deterministic behaviour
auto_id_stripping: true
syntax_highlighter: rouge

Expand Down
Loading