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

[Feature] Contract Tagging #440

Open
0xphilipp opened this issue Jul 16, 2023 · 1 comment
Open

[Feature] Contract Tagging #440

0xphilipp opened this issue Jul 16, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@0xphilipp
Copy link

Reasoning about what happens exactly in the Event Logs is difficult if you dont know what an address or wallet is.

There should be 2 or 3 ways of tagging.

  1. Global tagging managed by celatone / community that will be default for everyone. (Simple submission of wallet tags is necessary to make the experience smooth, ideally through the page)
  2. User tagging - Users should be able to tag their own addresses and to be better to reason about it.
  3. Optional: Index the labels of the contract instantiations and use them as default tag shown in the events log / guis. This should be able to be set based on a user setting, as it could also have some misleading / bad data on instantiations.

If a tag available instead of the full address, just show: {TAG} (neutron1...mkd2)

image

@tansawit tansawit added the enhancement New feature or request label Jul 18, 2023
@tansawit
Copy link
Contributor

Definitely! It's something we will be working on. Though it will require quite a bit of revamp on how we're currently parsing and sending data to the frontend to visualize, and also (currently) lower priority than things like contract verification/JSON Schema/state explorer that we've been getting more demand fo. So will be a bit before this gets to production.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants