Show delegate-stack-stx event on address page

I’m looking at this account https://explorer.stacks.co/address/STBB835X9NGMHWSH5E767X420GYCAV3WD12P5JJH?chain=testnet

It shows that only the delegate-stx method was called (for 200k stx). This method only delegates tokens but does not lock them up. A delegator would need to run delegate-stack-stx for that. The explorer view seems not to distinguish between delegated and stacked tokens.

[aulneau]

Just a note, this is really referencing a larger issue that we have:

Events that are related to a given address are not currently displayed on their pages. This is no different than showing when an address has received STX from a send-many type contract. I personally think it’s important to find a way to display these, even with the potential spam vectors.

I’m not sure we’d want this behavior. It would allow for a mild spam attack where someone could write a spam.clar contract that could be called with a bunch of victim addresses, over and over, making their wallet or explorer address page only display useless/spam txs.

This seems to be more of a UX problem. For example we could collapse all events from a given contract, allow pagination, expanding, searching, allow filtering, etc. It seems to be a separate (but important) issue. Token spam will be real too. I can mint 1 billion NFTs and send them all to you, but I don’t think that means we should not display or give the ability to view all related events for an address.

See these related issues: https://github.com/blockstack/explorer/issues/383 #373 https://github.com/blockstack/explorer/issues/386 #365 #364

[friedger]

Note, that delegate-stack-stx and other functions can be called by smart contracts like pool-tool or xverse-pool. Therefore, handling the locking events better is not only about the delegate-stack-stx contract call, but more on any tx that emits the lock event.