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

waitForAcceptance bug #441

Open
wms2537 opened this issue Jan 20, 2025 · 3 comments
Open

waitForAcceptance bug #441

wms2537 opened this issue Jan 20, 2025 · 3 comments
Assignees

Comments

@wms2537
Copy link

wms2537 commented Jan 20, 2025

Describe the bug
the current implementation only waits for execution status, instead it should wait for finality status. The description is correct, but the implementation is wrong.

https://github.com/focustree/starknet.dart/blob/37d0192351ad57632a6a9933530e2b3b69c39fb4/packages/starknet/lib/src/util.dart#L120C1-L142C2

@ptisserand
Copy link
Collaborator

If execution_status is SUCCEEDED it means that finality_status is either ACCEPTED_ON_L2 or ACCEPTED_ON_L1
https://docs.starknet.io/architecture-and-concepts/network-architecture/transaction-life-cycle/

So I think implementation is correct but description is not fully correct.
What do you think @wms2537 ?

@wms2537
Copy link
Author

wms2537 commented Jan 26, 2025

I think there is still a slight delay between SUCCEEDED and ACCEPTED_ON_L2 right? Some problems might arise when we are executing multiple transactions together that depend on one another sequentially.

If the term acceptance is being used, I suppose it is referring to finality_status?

@ptisserand
Copy link
Collaborator

ptisserand commented Jan 27, 2025

Yes you are right, waitForAcceptance should check finality_status instead.

@ptisserand ptisserand self-assigned this Jan 28, 2025
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

No branches or pull requests

2 participants