Open walter-hernandez opened 11 months ago
@walter-hernandez is there a way to reach you to discuss this issue a bit further? via discord/email/etc We a few issues related to this labels topic and wanted to aggregate the requirements and ensure a solution that satisfies the ask
Hello @SimiHunjan! Email me at walter.hernandez.18@ucl.ac.uk
Problem
As a developer and user of Hedera, I would like to know the context of certain transactions happening in the network as well as why certain wallet and smart contract addresses have received certain labels (see https://github.com/hashgraph/hedera-mirror-node-explorer/issues/417 and https://github.com/hashgraph/hedera-mirror-node-explorer/issues/565 for labelling of address proposals).
Additionally, previously, the possibility of labelling addresses for wallets and smart contracts (see https://github.com/hashgraph/hedera-mirror-node-explorer/issues/417 and https://github.com/hashgraph/hedera-mirror-node-explorer/issues/565) has been suggested. However, having the labelled wallets and smart contract addresses would not help that much in understanding the context of the assigned label.
Solution
Understanding the context of a label assigned to an address could be achieved following Twitter's example for tweets. For example, Twitter has a functionality for the community to provide context to certain tweets:
Therefore, community notes can be provided for why a wallet or smart contract address has been assigned a certain label improving confidence and trust in why a wallet and smart contract address has been labeled the way it is.
Likewise, a similar functionality that gives context to transactions that happened in the network (e.g., a community note detailing that certain transactions are related to a scam, hacking attack, or even donations, etc.) for users of the network to decide how to engage with a wallet or smart contract address.
Everyone in the network (from retail users, research community, policymakers, and even exchanges) can benefit from these community nodes to understand what is happening in the network contextually
Alternatives
No response