-
Notifications
You must be signed in to change notification settings - Fork 89
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-rs Deployment: Checking Transaction Status for Subsequent Invocation #389
Comments
Thanks for reaching out and I'm glad you like the library :) Transaction watching isn't something that's built-in right now, and applications must implement their own watching logic. For example, this is how it's currently implemented in This feature should be part of That said, as of today, a naive loop as demostrated in the I'll leave this issue open for tracking the implementation of this feature. |
Thanks for the speedy response, @xJonathanLEI! Thank you for referencing me to the Also, your insights make sense - a built-in TransactionWatcher could be a strong addition to starknet-rs. For now, using the simple loop from starkli seems like our best bet for the Book. Looking forward to tracking the progress of this feature. Thanks for keeping the conversation open! |
Hey! Big fan of
starknet-rs
here.We're currently authoring tutorials about starknet-rs for the StarkNet Book. As part of this effort, we're developing a function that deploys a contract and then calls upon this newly deployed contract, all within the same script.
To ensure seamless operation, we need to verify that the contract deployment transaction has been accepted on L2 before we proceed to the invocation part. Could you recommend the best approach for confirming a transaction's status on L2 using starknet-rs?
I can imagine something like:
Specifically, we're looking for a function or method that efficiently fetches the status of a specific transaction hash, and then allows further execution only if the status is 'Accepted' on L2.
Thank you for your time and support.
Best Regards,
The text was updated successfully, but these errors were encountered: