Skip to content

Conversation

@timothymcmackin
Copy link
Collaborator

@timothymcmackin timothymcmackin commented Nov 25, 2025

Docs for proposed kernel 6.0.

  • Support for EVM Osaka
  • SUpport for instant confirmations via eth_sendRawTransactionSync and two new websocket event streams but they may not be enabled at the time this kernel update goes live
  • Change to an FA bridge event

Info about actually using instant confirmations moved to #396 for when this is enabled and usable.

@timothymcmackin timothymcmackin self-assigned this Nov 25, 2025
@vercel
Copy link

vercel bot commented Nov 25, 2025

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

Project Deployment Review Updated (UTC)
docs-etherlink Ready Ready Preview, Comment Dec 15, 2025 5:22pm

@skenaja
Copy link
Collaborator

skenaja commented Nov 25, 2025

secp256r1 precompile should be at 0x0000000000000000000000000000000000000100 on all networks

If you pass `latest` instead of `pending`, the sequencer waits until the transaction is in a block to send the confirmation.
Etherlink supports this `pending` value only on the `eth_sendRawTransactionSync` method, not on any other methods.

The sequencer returns information about the transaction, such as its gas price and gas cost.
Copy link
Contributor

Choose a reason for hiding this comment

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

Sam here I think could be interesting to mention we return a receipt.
Side note, returning this format and using this name for the endpoint isn't out of my mind we follow a draft EIP on ethereum : https://eips.ethereum.org/EIPS/eip-7966 (but we added the optional block parameter to fill our needs). Might be interesting to mention

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Makes sense. How's this? d29fae4

When the sequencer executes the transaction and intends to put it in the next block, the sequencer returns a receipt for the transaction that includes information such as its gas price and gas cost. This receipt matches the specification for the eth_getTransactionReceipt endpoint except that the blockHash field is always 0x000... because the block has not been created yet. The blockNumber field provides the correct level for the block that the transaction will be in. You can take this response as a confirmation that the sequencer will put the transaction in the next block.

const web3Instance = new Web3(new Web3.providers.WebsocketProvider('ws://127.0.0.1:8545/ws'));
// Subscribe to new instant confirmations
const newConfirmationsSubscription = await web3Instance.eth.subscribe('NewIncludedTransactions');
Copy link
Contributor

Choose a reason for hiding this comment

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

tez_NewIncludedTransactions

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 changed it to tez_newIncludedTransactions -- is that capitalization correct?

Copy link
Collaborator

@skenaja skenaja left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

Copy link
Collaborator

@NicNomadic NicNomadic left a comment

Choose a reason for hiding this comment

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

LGTM

@timothymcmackin timothymcmackin merged commit 03f46a3 into main Dec 16, 2025
2 checks passed
@skenaja skenaja deleted the etherlink-6 branch December 17, 2025 08:04
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.

5 participants