-
Notifications
You must be signed in to change notification settings - Fork 8
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_blockNumber #39
Comments
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. |
can i take this one pls Sir ? |
This one should be ready for review |
This one got the right behavior, waiting full sync to confirm but should work without any problems 🚀 |
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. |
Issue: Implement
starknet_blockNumber
RPC CallDescription:
The
starknet_blockNumber
RPC call has been implemented but requires further testing and verification against the entire state. This RPC call retrieves the most recent accepted block number.Parameters:
None.
Expected Result:
The latest block number.
Potential Errors:
NO_BLOCKS
: No blocks were 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.
The text was updated successfully, but these errors were encountered: