You are viewing a single comment's thread from:
RE: Security Suggestion for Crypto Exchanges - Withdraw Behavioral-Lock
An interesting possibility that I've never considered.
I think it would be safe to allow someone to select their own behavioral preferences.
It could save them a headache in the case of being hacked, however it may end up being just as much of a pain and would consider setting up an override anyway.
Limiting a persons transaction capabilities can also safeguard them from making a bad decision based on emotion, however it could also inhibit them from their full potential on a sure bet.
Thank you, @akrid, both for your up-vote as well as your excellent comment. :c)
That you had never considered this avenue I consider to be highly encouraging.
Depending upon how tight the behavioral controls are, I do suspect that this could thwart the vast majority of cases of wrongful access (phishing/hacking).
The only scenario where I could see any kind of override being desirable is a situation where one has placed a 'won't withdraw funds before X date' behavioral lock and ends up needing funds sooner (in which case a/he needs to reflect upon the possibility that s/he is engaging in over-investment) - or perhaps made a mistake. 26 Dec 2018 is a whole year beyond 26 Dec 2017.
In the event of such a mishap standard security checks could involve specifying the Day and month - although full ID verification (for exchanges where such applies).
For decentralized exchanges one could use a master password as an override. It might be an interesting feature for behavioral locks to offer to send emails or allow a print-out for one's personal records.
As for emotion - that is not the kind of safeguard that I had in mind - but I can see what you mean. :c) I personally feel that there should be as few hindrances as possible where placing traces are concerned (although I would favorably consider warnings where attempting to buy or sell outside the day norms of a given exchange (example - missing or appending a '0' in price). I'd consider such a three-click process (because once in a while, two-click is not enough).
Source
Thanks again! :c)