Because for normal transfer you need memo. how else do you send Hive to binance? and how else they recognize it's you?
You are viewing a single comment's thread from:
Because for normal transfer you need memo. how else do you send Hive to binance? and how else they recognize it's you?
I know but do we need hire world's best programmers and NASA engineers to figure out how to block the option in that case? It shouldn't be users responsibility to know that memo shouldn't be used there, it's just poor design.
there is no instruction on adding memo people are adding on their own lol. memo is not poor design, it's mandatory for most transfer. it just is not manadatory for leopool transfer.
So there is no way that there could be a view without the memo and it's only function in this case is to mess up the transaction?
You have keychain and signer...
Yes, which leads us back to the original question, why use a system that will halt the transaction? I mean, let's say you go to a store to buy fresh fruits and there were sharp knives hidden next to the fruits so when a customer picks up a fruit, they can harm themselves while doing that. Now why would the store owner do this? And not add any warming signs? In my opinion it could be bad for the business.
its user choice to use manual or auto... what khal has did here is allowed all possible option to acccept on leopool.. what you are considering is core engineering and single option that suits all and doesn't require thinking.. which is ideal in enterprise but we are open source blockchain product we break more than we fix... it's normal.
Open source projects don't have to stay stagnant. They too can develop, question and mature but that does not happen by saying that "this is just the way it is". Web3 projects can and should be ambitious, constantly going forward or they are stepped on.
Of course we can allow different options but none of the options should lead the user straight down the cliff.