hirosystems
Label "0 STX" genesis block transaction
As initially discussed on https://github.com/blockstack/explorer/issues/377, all addresses with Stacks 1.0 activity appear to have received a "0 STX" transaction upon transition to Stacks 2.0.
E.g. https://explorer.stacks.co/txid/0x2f079994c9bd92b2272258b9de73e278824d76efe1b5a83a3b00941f9559de8a?utm_source=stacks-wallet&chain=mainnet
It may be confusing to users to see this transaction and suggest to them that something is broken or "off". We could resolve this perceptual issue by labeling this transaction specially as "Stacks 2.0 Genesis Block" and providing an explanation or something.
We may also want to tackle this separately in the wallets. But it seems prudent to resolve it on the explorer first since that's where we provide the most detail generally.
I think a short term fix could be to change that specific transaction to Stacks 2.0 Genesis Block or something like that. However, the larger issue at play here is that there is information contained within that transaction that is meaningful to the address it's displayed on, but it's hard to display. There is an event that has an associated balance that should be reflected in place of where this "0 STX" transfer is being displayed.
In an ideal world when we're querying data for a given address, in this kind of instance we'd get back the information that is most relevant to the address we're looking at. Meaning that the event which contains the stx for the address would appear, and maybe it's that we'd display the "root" transaction as a caption, or tag or something else, but there is a shift away from the transaction that holds all the events as the primary item, to the event specific to address as the primary item.
I have kind of been viewing this transaction, and any contract call that has token-transfers associated with it as having "side effects". Currently we don't have a great way to query/display the side effect data in place of the root transaction.
See these other issues: https://github.com/blockstack/explorer/issues/373 https://github.com/blockstack/explorer/issues/365 https://github.com/blockstack/explorer/issues/364
