-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add burnchain op type to the new_block
event
#168
Conversation
Codecov Report
@@ Coverage Diff @@
## master #168 +/- ##
===========================================
+ Coverage 79.32% 90.47% +11.14%
===========================================
Files 266 6 -260
Lines 173476 294 -173182
===========================================
- Hits 137616 266 -137350
+ Misses 35860 28 -35832 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks great @pavitthrap !
Is there a Docker build I could use through clarinet integrate
so I can go over the NFT use case with these new payloads? Or what do you suggest?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cool test!.. can we just wait to submit the commented stuff later?
Hi! I haven't actually run any subnets Docker images, but the command |
Closing in favor of #216 |
Description
This PR adds greater information about burnchain operations (such as DepositNft, DepositStx, etc), to the
new_block
event emitted by the event observer.A new field is added for each tx json object, called
burnchain_op
, which contains information specific to the burn transaction.Applicable issues
nft_mint_event
#160 as well (will confirm with @rafaelcr )