-
Notifications
You must be signed in to change notification settings - Fork 18
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
feat: rfc-1104 confirming transactions #140
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In addition to this, I would like to add an extra level.
Background:
Due to approvals in Eth contracts, there are a number of attacks where the user is tricked into signing a transaction granting access to the malicious user to act on their behalf. For example an attacker could create a phishing site and then trick the user to sign approval for an ERC20 to the attacker's public key.
In Tari approvals and transactions happen differently, but I think there is still some things we can do to prevent the user from falling victim to these attacks.
One thing we could do is add a warning to the confirmation dialog if there is something suscipious about the transaction they are signing. We want this to be a clear warning that cannot be missed by the user, so we need to be careful of showing the warning too often. We could also disable the approval button for a number of seconds (like a countdown) to make sure the user can taken the time to see the warning.
This would also require the UI to have some understanding of what a dangerous transaction is. This gets a bit complicated, but I think that the warning can be mentioned in this PR and the implementation can be left to a later date.
src/RFC-1104_ConfirmingTx.md
Outdated
|
||
#### Suggested solution | ||
|
||
As it was discussed, the security comes first, so definitely all transactions need to be confirmed before sending to the Tari Network. At the same time users shouldn’t be overwhelmed by the amount of information, especially not given just the “list of hashes” to sign, which are definitely not understandable for typical users. Therefore the idea is to show the transaction summary and quite a nice example of that is presented by [Radix Wallet](https://www.radixdlt.com/wallet). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"confirmed" is a term already used in blockchain, so for clarity, I suggest changing this to say "confirmed by the user"
Please rename this to "User confirmation when submitting transactions" |
RFC-1104 Tari Universe: rules of confirming transactions.
The aim of this Request for Comment (RFC) is to describe the rules for confirming transactions by the user.