Skip to content

feat(rpc): populate block_number on pre-confirmed/pre-latest events#3348

Merged
zvolin merged 1 commit intoequilibriumco:mainfrom
m-kus:fix/pending-event-block-number
Apr 17, 2026
Merged

feat(rpc): populate block_number on pre-confirmed/pre-latest events#3348
zvolin merged 1 commit intoequilibriumco:mainfrom
m-kus:fix/pending-event-block-number

Conversation

@m-kus
Copy link
Copy Markdown
Contributor

@m-kus m-kus commented Apr 16, 2026

Summary

  • Populate block_number on events returned from pre-confirmed and pre-latest blocks in starknet_getEvents. Previously these were always null, even though the speculative block number is known. This broke event parsers that expect block_number to always be present.
  • block_hash remains null for pending events as it is genuinely unknown.

Resolves #3347

Details

match_and_fill_events now accepts a block_number: BlockNumber parameter and sets block_number: Some(block_number) on constructed events. The three call sites in get_pending_events pass the appropriate block number:

  • pre_latest_block.number for pre-latest events
  • pending.pre_confirmed_block_number() for pre-confirmed events

@m-kus m-kus requested a review from a team as a code owner April 16, 2026 16:09
Copy link
Copy Markdown
Contributor

@CHr15F0x CHr15F0x left a comment

Choose a reason for hiding this comment

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

LGTM

@zvolin zvolin merged commit 53fb8ae into equilibriumco:main Apr 17, 2026
20 of 22 checks passed
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.

Correctly assign block number for pending events

3 participants