Provide stacks ID within transaction response

[aulneau]

@zone117x would it be possible for the transaction object to contain both a stacks address and the corresponding ID if there exists one? The explorer provides options for displaying that relationship.

[zone117x]

Possibly -- we'll have to see how quickly names can be queried once BNS is implemented in Stacks 2.0. If a tx list response requires hundreds of data-map lookups to the core-node it might not be doable.

[stale[bot]]

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.

[sabbyanandan]

@zone117x: Given that the BNS implementation is now available, do we have a way to return the ID as part of the response payload? It seems logical to present the opportunity to trace the parent<->child relationship.

[zone117x]

This sounds possible -- although we'd be querying the BNS table(s) we already have in pg rather than doing requests to the stacks-node. However, we'd need to figure out which endpoints and payloads containing addresses that we'd want to add associated name fields. The original request here is referring to the /tx/<txid> endpoint which was one of the only ones implemented at the time, but it's not clear to me if adding associated BNS names to addresses in this endpoint's payload would be useful or make sense today.

And note that we do already have BNS endpoints to lookup names associated with an address.

[smcclellan]

Closing due to inactivity.