Skip to content

Add transaction_index to getTransactionReceipt and getEvents#327

Open
cchudant wants to merge 3 commits intostarkware-libs:release/v0.10.1-rc.0from
cchudant:patch-4
Open

Add transaction_index to getTransactionReceipt and getEvents#327
cchudant wants to merge 3 commits intostarkware-libs:release/v0.10.1-rc.0from
cchudant:patch-4

Conversation

@cchudant
Copy link
Copy Markdown
Contributor

@cchudant cchudant commented Jul 28, 2025

Changes

This was proposed by @kkovaacs, but I added the field to getTransactionReceipt too instead of just getEvents.
Related to #326 (which adds finality_status to the same types) and #325 (which fixed block_number in the same types)
Affects #323

Checklist:

  • Validated the specification files - npm run validate_all
  • Applied formatting - npm run format
  • Performed code self-review
  • If making a new release, checked out the guidelines

(i'm using the github interface for these spec PRs, should I really clone the repo on my machine to test it there and check this checklist?)

@eitanm-starkware eitanm-starkware changed the base branch from release/v0.9.0-rc.3 to release/v0.10.1-rc.0 January 4, 2026 08:31
@eitanm-starkware
Copy link
Copy Markdown
Contributor

Can we make this non-breaking(ie add flag to receive index)? Also, it would be good to not have code duplication. Can create a component for TRANSACTION_INDEX(see BLOCK_NUMBER for example). Is this pr useful independently of the prs you referenced above? @cchudant

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.

2 participants