[SDK] feat: return block and tx_hash from getStatusEvents#3834
Merged
[SDK] feat: return block and tx_hash from getStatusEvents#3834
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
Dzeranov
approved these changes
Mar 18, 2026
portuu3
approved these changes
Mar 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue tracking
Freestyle
Context behind the change
Extended
getStatusEventsreturn value with info about block and tx hash. Also fixedstatusfield to be human-readable in both SDK.How has this been tested?
examplescripts withgetStatusEventw/ filter by escrow addressRelease plan
Regular
Potential risks; What to monitor; Rollback plan
For both SDK changes might be considered as breaking:
statusto return string instead of number, which is also a breaking change; taking into account that JL seems to be the only consumer of this and change already applied - probably it's fine to go withminorhere