Skip to content

Conversation

@timothymcmackin
Copy link
Collaborator

Instant confirmations are enabled in the 6.0 update but they will not be available for use until they are enabled in the EVM node.

  • Update the updates page to show that instant confirmations are available
  • Add info to finality discussion about this new layer of finality
  • Add example of submitting transaction with the sync endpoint and waiting for the receipt
  • Add example of using the new websockets to listen for confirmations

@timothymcmackin timothymcmackin self-assigned this Dec 2, 2025
@vercel
Copy link

vercel bot commented Dec 2, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
docs-etherlink Ready Ready Preview, Comment Jan 13, 2026 2:41pm


Beginning with EVM node 0.48 and the version 6.0 upgrade, Etherlink supports instant confirmations.
You can send a transaction with the `eth_sendRawTransactionSync` method and receive an instant confirmation from the sequencer that it intends to put the transaction in the next block.
This confirmation includes a transaction receipt that provides information about the completed transaction, such as the status, hash, gas used, and index of the transaction in the next block.
Copy link
Collaborator

Choose a reason for hiding this comment

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

This sentence is confusing because it blends the frontiers between two responsibilities (inclusion, and execution) and suggests the sequencer provides the receipt (it does not)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I removed "from the sequencer" here and clarified a bit -- how it is now?

Beginning with EVM node 0.48 and the version 6.0 upgrade, Etherlink supports instant confirmations.
You can send a transaction to a node with the eth_sendRawTransactionSync method and receive an instant confirmation from the node that the sequencer intends to put the transaction in the next block. This confirmation includes a transaction receipt that provides information about the transaction, such as the status, hash, gas used, and index of the transaction in the next block. The only information missing from the receipt is the hash of the next block, because it has not been created yet.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Yep right on point!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants