[RPC-Spec-V2] chainHead/follow: Provide multiple block hashes to the initialized event #3432
Labels
I5-enhancement
An additional feature request.
Comments
This was referenced Feb 21, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Mar 6, 2024
…ent (#3445) This PR extends the Initialized event of the chainHead_follow subscription. Now, the event provides multiple finalized block hashes. This information allows clients that are disconnected, and that want to reconnect, to not lose information about the state of the chain. At the moment, the spec encourages servers to provide at least 1 minute of finalized blocks (~10 blocks). The users are responsible for unpinning these blocks at a later time. This PR tries to report at least 1 finalized block and at most 16 blocks, if they are available. Closes: #3432 cc @paritytech/subxt-team --------- Signed-off-by: Alexandru Vasile <[email protected]> Co-authored-by: Niklas Adolfsson <[email protected]>
bgallois
pushed a commit
to duniter/duniter-polkadot-sdk
that referenced
this issue
Mar 25, 2024
…ent (paritytech#3445) This PR extends the Initialized event of the chainHead_follow subscription. Now, the event provides multiple finalized block hashes. This information allows clients that are disconnected, and that want to reconnect, to not lose information about the state of the chain. At the moment, the spec encourages servers to provide at least 1 minute of finalized blocks (~10 blocks). The users are responsible for unpinning these blocks at a later time. This PR tries to report at least 1 finalized block and at most 16 blocks, if they are available. Closes: paritytech#3432 cc @paritytech/subxt-team --------- Signed-off-by: Alexandru Vasile <[email protected]> Co-authored-by: Niklas Adolfsson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Backport:
Initializedevent json-rpc-interface-spec#136The
initializedevent of the chainHead_follow subscription must provide multiple finalized block hashes.This information allows clients that are disconnected, and that want to reconnect, to not lose information about the state of the chain.
The text was updated successfully, but these errors were encountered: