directing your users to CfB in case you make mistakes with the withdrawals is indeed bad style.
CfB is right when he says ECC can be implemented client side.
CfB is right when he says ECC can be implemented client side.
Bad style is not giving any valid reason why you can't add 3 bytes per transaction to prevent people from losing money, while simultaneously adding 1000-byte arbitrary messages.
Error check on the client doesn't solve the problem of memory corruption, so you will still lose your money occasionally, just less often.
Not to mention that now we have a whole bunch of clients and need to somehow switch to the new format.
If we're afraid of memory corruption then we need to add error check for the amount of money sent and for the fee, don't we?
