Quote from: tonych on September 13, 2016, 04:43:27 PM

Quote from: kaicrypzen on September 13, 2016, 09:41:36 AM

Quote from: tonych on September 12, 2016, 10:14:17 AM

Having both options adds complexity on both technical and usability sides:
1. More code that needs to be written, debugged, and tested. Despite all the testing, more code is always more complexity and greater probability of errors, including security errors. Complexity is the enemy of security.
2. More options for users means more options for attackers too. This needs to be analyzed, and with growing complexity the chances of missing something increase.
3. Longer instructions for users. They are scared off by the abundance of text or unfamiliar words, like "signing a message".
4. Users have to evaluate both options and make their choices. Choice is difficult when the difference between the choices is not immediately clear.

All this is fine as long as there is a real tangible benefit in adding more options that overweights the negatives. In this particular case, there isn't.

Thx for clarifying these points. Points 3 and 4 are okay but as I said earlier they do not apply to all users, I think we won't reach an agreement on that and that's okay

.

What I find negative about this, is the lack of options ... (I want to send a signed message to claim, I can't. I want to see the transaction id and/or fees before sending, I can't. I don't want to use Google Play

, I can't).

Looks like you want more control than an average user (well, as I perceive an average user). That's OK, there is no one size that fits all. I envisage that we'll have multiple wallets in Byteball ecosystem that fit different preferences, like we already have in Bitcoin.

Nice to hear that

, I can accommodate with the current wallet though Wink

.

Quote from: CryptKeeper on September 14, 2016, 03:25:26 PM

You can send some Bytes to me: MBACPRCMAYRWFVHZQHZZYQRN3XEUECVR
and if you post your address I'll send you some back! Grin

Here you go, just sent you 100 000 bytes.

- My DEVICE ADDRESS is 0CGP3QJM2ZUGYO6TYLG4KAGYWNWW6BLDV.
- The address that displays when I click on INSERT MY ADDRESS (it changes every time) in the chat window with Testnet Faucet is KRMI2HTBIML3CB3KEG3LB4QP75QQHDQ5.

If you are interested in pairing devices, here is my pairing code:

Code:

AmOIR5s+WxMyYUhUbEUwvr4lSP68ftSd9My8vJ1Esz2/@byteball.org/bb#gnSZxT7d0S2R

I actually tried pairing two of my devices by adding the pairing code from one to the other but this doesn't seem to be enough (I chatted from one device to another but never received messages), maybe I need to perform the operation on both devices? or maybe both must be online?

Some observations:
- 0 is considered as a valid amount, I mean when I type 0, Not valid does not appear (whereas it appears for -1 for instance), however 0 does not trigger the SEND button (which is normal), so maybe 0 should be considered not valid.
- When writing a very long number the digits overlap on bytes.
- I tried sending very large numbers and it resulted in sending 1 or 2 bytes.
- Why is it compulsory to backup the wallet keys before receiving a payment?