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_estimateFee #37

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

feat/starknet_estimateFee #37

antiyro opened this issue Sep 17, 2023 · 3 comments
Assignees
Labels
exec This rpc method concern an execution RPC RPC implementation related issues stale

Comments

@antiyro
Copy link
Member

antiyro commented Sep 17, 2023

Issue: Implement starknet_estimateFee RPC Call

Description:
The starknet_estimateFee RPC call has been implemented but requires further testing and verification against the entire state. This RPC call estimates the resources required by transactions when applied on a given state.

Parameters:

  • request: The transaction(s) to estimate. This is a sequence of transactions to estimate, running each transaction on the state resulting from applying all the previous ones. This parameter is required.
  • block_id: The hash of the requested block, or number (height) of the requested block, or a block tag, for the block referencing the state or call the transaction on. This parameter is required.

Expected Result:
A sequence of fee estimations where the i'th estimate corresponds to the i'th transaction.

Potential Errors:

  • CONTRACT_NOT_FOUND: The specified contract could not be found.
  • CONTRACT_ERROR: An error occurred in the contract.
  • BLOCK_NOT_FOUND: The specified block could not be found.

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
@Tbelleng
Copy link

Tbelleng commented Jan 5, 2024

can i take this one Boss ?

@Tbelleng Tbelleng moved this from 🆕 New to 🏗 In progress in Deoxys Jan 5, 2024
@github-actions github-actions bot removed the stale label Jan 6, 2024
@Tbelleng Tbelleng moved this from 🏗 In progress to 👀 In review in Deoxys Jan 8, 2024
@antiyro antiyro moved this from 👀 In review to 🏗 In progress in Deoxys Jan 9, 2024
@antiyro antiyro moved this from 🏗 In progress to 👀 In review in Deoxys Jan 29, 2024
@antiyro antiyro added the exec This rpc method concern an execution label Jan 30, 2024
Copy link

github-actions bot commented Mar 1, 2024

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 Mar 1, 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
exec This rpc method concern an execution RPC RPC implementation related issues stale
Projects
Status: ✅ Done
Development

No branches or pull requests

2 participants