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.

Sign up for GitHub

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

Jump to bottom

Split status in RPC v0.4 #881

Closed
joshklop opened this issue Jul 4, 2023 · 0 comments · Fixed by #878
Closed

Split status in RPC v0.4 #881

joshklop opened this issue Jul 4, 2023 · 0 comments · Fixed by #878
Labels
RPC JSON RPC API

Comments

@joshklop
Copy link
Contributor

joshklop commented Jul 4, 2023

Once starkware-libs/starknet-specs#107 is merged, we need to replace the Status field on the rpc.TransactionReceipt struct with two new fields: execution status and finality status. We should create corresponding enums for the new statuses.
@joshklop joshklop added the RPC JSON RPC API label Jul 4, 2023
This was referenced Jul 4, 2023
Merged
Closed
@joshklop joshklop linked a pull request Jul 10, 2023 that will close this issue
Split Status into FinalityStatus and ExecutionStatus #878
Merged
@joshklop joshklop changed the title Update RPC handlers for v0.4.0 Split status in RPC v0.4 Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
RPC JSON RPC API
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Split Status into FinalityStatus and ExecutionStatus NethermindEth/juno
1 participant
@joshklop