-
Notifications
You must be signed in to change notification settings - Fork 60
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
starknet_getNonce on block_id=pending fails with starknet-devnet-rs 0.0.6 #474
Comments
Thank you for the clear description. @mikiw I assume it is related to your task. Can you TAL and see if your unreleased changes perhaps fix this? |
Yes, it's related. I'll check that. |
@0xknwn this problem is related to this task #445 (point defaulting to the latest state in case calls are done on pending (and there is no pending)) and once it is merged it will work as expected. Unfortunately I can't give any estimates since we are preparing to conference. With block on demand mode |
Similar issue reported on Discord: https://discord.com/channels/793094838509764618/1245283649356566620 |
Describe the bug (observed vs expected behavior)
I am starting
starknet-devnet-rs
with the latest 0.0.6 (I tried both from docker and a cargo install) with--seed=0
and when I run a getNonce on the account that is publicized as available with block_id = pending. That is the command:I get:
Note that:
"block_id": "latest"
works on v0.0.6"block_id": "pending"
works on v0.0.5"block_id": "pending"
(and an account that exists obviously) works on sepoliaThe CLI output shows the account is correct and again it works with block_id is latest anyway.
Is it an intended behavior or is it a bug? starknet.js does an implicit getNonce on
execute()
and it does not provide any feature (except fixing the code) to change the block_id tag frompending
tolatest
.Not reproducible on testnet
To Reproduce
see the description above:
Devnet version
System specifications
I did it on docker AND on my OSX with the
cargo install
version of starknet-devnet. Same behavior on the 2. Thank you for your helpThe text was updated successfully, but these errors were encountered: