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

Add base layer transaction type for API #3307

Closed
pavitthrap opened this issue Sep 28, 2022 · 2 comments
Closed

Add base layer transaction type for API #3307

pavitthrap opened this issue Sep 28, 2022 · 2 comments
Assignees
Labels
enhancement Iterations on existing features or infrastructure. good first issue Appropriate for a new open source contribution. locked

Comments

@pavitthrap
Copy link
Contributor

Currently, the API determines that a particular tx included in a block came from the base layer by checking to see that the raw_tx field is set to 00. We can add another field to the transaction object to include the type of the base layer payload as an option.

This is inspired by a change that is going to be made for subnets: hirosystems/stacks-subnets#155

@pavitthrap pavitthrap added enhancement Iterations on existing features or infrastructure. good first issue Appropriate for a new open source contribution. stacks-future labels Sep 28, 2022
@jcnelson
Copy link
Member

I think this is already done? Burnchain operation events now contain a burnchain_op key. Please reopen the issue if not.

@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 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Iterations on existing features or infrastructure. good first issue Appropriate for a new open source contribution. locked
Projects
Archived in project
Development

No branches or pull requests

3 participants