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

Send additional data to event observer for Stacks-over-BTC wire formats #2591

Closed
zone117x opened this issue Apr 14, 2021 · 6 comments
Closed
Labels

Comments

@zone117x
Copy link
Member

See issue hirosystems/stacks-blockchain-api#415

this address should be the first output address of the bitcoin transaction. I realize that the stacks-node doesn't currently provide enough information to obtain this, so changes would be required there as well, but we should discuss in a new issue.

Originally posted by @kantai in hirosystems/stacks-blockchain-api#414 (comment)

The API is unable to generate accurate data for stx-stack operations performed via btc txs.

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Apr 16, 2022
@zone117x
Copy link
Member Author

Not stale AFAIK. @kantai any modern context here?

@stale stale bot removed the stale label Apr 19, 2022
@kantai kantai changed the title Send additional bitcoin-op data to event observer Send additional data to event observer for Stacks-over-BTC wire formats Apr 25, 2022
@kantai
Copy link
Contributor

kantai commented Apr 25, 2022

No more modern context here. Is the API currently able to get this data for the stx-transfer BTC operations? Or is this issue for providing data on both stack-stx and stx-transfer BTC ops?

@zone117x
Copy link
Member Author

I believe the stx-transfer data can be correctly derived from context in the event payload, although explicit info would be nice.

The stack-stx operation derives incorrect data IIRC, and more info in the event payload is required.

@jcnelson
Copy link
Member

This now happens in 2.1.

@blockstack-devops
Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Nov 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
Archived in project
Development

No branches or pull requests

4 participants