-
Notifications
You must be signed in to change notification settings - Fork 2
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
[Enhancement] Add text descriptions to proposals/history #77
Comments
This was discussed before with @tj825 and @oteku.
|
That's an interesting discussion, thank you for pointing it out. I think it does not affect the history page, though: while I agree with @tj825 that malicious metadata can be used by an adversarial user, giving an opportunity for the members of a multisig to label past transactions should not be as harmful. Also, I still don't think such labeling should be stored on the blockchain. |
Oh sorry, I forgot about this issue. I mean useful, intelligible text for every users to see (so not in local storage). Let's say that I manage a safe with a few friends. We use the money to pay for parties that we throw out at one another's house. In retrospect (a few months after throwing a few parties), I want to be able to remember which action on TzSafe was for what party, i.e. have "Transfer 100 tez" with "Birthday party at Mark's house". |
Sorry, too. I realized that I forgot clicking comment button... |
The History page in its current form is very good (I don't remember seeing it when I used the dApp the first time). I totally understand why I would need to go back in time to understand what was voted in my absence.
However, for less technical people, I think having the opportunity to add short descriptions of every past action would be nice: "deposit X amount of token", "send X money to Alex", "place X into Youves vault"…. I would argue that these messages do not need to be stored on the blockchain (and actually probably shouldn't, for privacy reasons).
The text was updated successfully, but these errors were encountered: