Skip to content

Conversation

@kirdatatjana
Copy link
Contributor

Closes #32

@kirdatatjana kirdatatjana added the documentation Improvements or additions to documentation label Oct 14, 2025
@kirdatatjana kirdatatjana changed the title docs: Sync specs docs (sync): Specs Oct 15, 2025
@kirdatatjana kirdatatjana self-assigned this Oct 15, 2025
- Restrict itself to providing only data available locally.

> Note:
> Emerald currently supports only archival Reth nodes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is no longer true.

Suggested change
> Emerald currently supports only archival Reth nodes.
> In order for a node to be able to sync, there has to be at least one archival node in the network that can provide historical data. We plan to add snapshot syncing to remove this constraint.

Suppose a situation where metadata is available, but the payload bodies for the corresponding block heights must be retrieved from Reth. In this case, the decided value is reconstructed and returned to Malachite, which then forwards it to the syncing peer.

When the peer receives the decided value, it must validate it via the `engine_newPayload` API call.
If Reth is still syncing and does not yet have the required data for validation, the call will return `PayloadStatus::SYNCING`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add references to the config flags. (their names and default values).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[docs] Add Sync specs

3 participants