You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this is a meta-issue for an alternative approach to #64
the reason for suggesting #64 was mainly that in a praxis dogfooding test it showed users ignored warnings that where written in bold - it looked like this:
The idea was now to use HD wallets to prevent this user error.
But there might actually be another way.
For people that did this mistake: offer an option to sign a message with their account to prove the tx is from them and correlate this way.
This should solve most of the problems.
The rest (e.g. using an exchange that rounds) can even be small enough that manual support is feasible.
Advantage is that is is less complexity and cheaper.
The text was updated successfully, but these errors were encountered:
to decide between #69 and #64 we should gather some data. Assemble a list of the error cases and gather the reason for each one (most of the time this will need us to contact the users as there is no trace of it on chain)
this is a meta-issue for an alternative approach to #64
![Selection_156](https://user-images.githubusercontent.com/111600/61531599-944c8500-aa27-11e9-9deb-1ab865c92cea.png)
the reason for suggesting #64 was mainly that in a praxis dogfooding test it showed users ignored warnings that where written in bold - it looked like this:
The idea was now to use HD wallets to prevent this user error.
But there might actually be another way.
For people that did this mistake: offer an option to sign a message with their account to prove the tx is from them and correlate this way.
This should solve most of the problems.
The rest (e.g. using an exchange that rounds) can even be small enough that manual support is feasible.
Advantage is that is is less complexity and cheaper.
The text was updated successfully, but these errors were encountered: