Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat/starknet_getTransactionByBlockIdAndIndex #30

Open
antiyro opened this issue Sep 17, 2023 · 3 comments
Open

feat/starknet_getTransactionByBlockIdAndIndex #30

antiyro opened this issue Sep 17, 2023 · 3 comments
Assignees
Labels
RPC RPC implementation related issues stale

Comments

@antiyro
Copy link
Member

antiyro commented Sep 17, 2023

Issue: Implement starknet_getTransactionByBlockIdAndIndex RPC Call

Description:
Get the details of a transaction by a given block id and index. If no transaction is found, null is returned.

Parameters:

  • block_id: The hash of the requested block, or number (height) of the requested block, or a block tag. This parameter is required.
  • index: The index in the block to search for the transaction. This parameter is required.

Expected Result:
The details of the transaction given by the identified block and index in that block, including its hash.

Potential Errors:

  • BLOCK_NOT_FOUND: The specified block could not be found.
  • INVALID_TXN_INDEX: The specified transaction index in the block is invalid.

Testing:
Initial testings can be found here. However, these should not be considered complete and improvements are welcome.

Resources:

Comments:
Please comment below for coordination.

@antiyro antiyro added this to Deoxys Sep 17, 2023
@antiyro antiyro converted this from a draft issue Sep 17, 2023
@antiyro antiyro added the RPC RPC implementation related issues label Sep 17, 2023
@github-actions
Copy link

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍
Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs.
Thank you for your contributions!

@github-actions github-actions bot added the stale label Oct 18, 2023
@Trantorian1 Trantorian1 self-assigned this Jan 9, 2024
@Trantorian1
Copy link
Member

Working on it !

@Trantorian1 Trantorian1 removed the stale label Jan 9, 2024
@Trantorian1 Trantorian1 moved this from 🆕 New to 🏗 In progress in Deoxys Jan 9, 2024
@antiyro antiyro assigned jbcaron and unassigned Trantorian1 Jan 10, 2024
@jbcaron jbcaron moved this from 🏗 In progress to 👀 In review in Deoxys Jan 29, 2024
Copy link

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍
Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs.
Thank you for your contributions!

@github-actions github-actions bot added the stale label Feb 10, 2024
@antiyro antiyro moved this from 👀 In review to ✅ Done in Deoxys Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RPC RPC implementation related issues stale
Projects
Status: ✅ Done
Development

No branches or pull requests

3 participants