Send the receiver's address using "Insert address" from the receiver's chat interface. Click on that address in the sender's chat interface and normally you should be able to choose blackbytes and send them. As HCP pointed out, you need bytes to pay for the transaction fees.
How should someone guess that? I mean, there is no instructions whatsoever for doing something lile that. I understand the idea of Byteball is to be easy to use to pursue mass user adoption, but that's certainly not easy unless you know the trick.
And by the way, it didn't work. I am getting now a mistake in red color:
"Impossible to send the payment: precommit callback failed: [a string of text]: conflicting spend proof in inner unit [a string of text]"
When you are stuck you try other things, you click wherever you can until something works ... Having said that, nobody's asking you to guess anything, that's why you can ask here and/or on Slack and people will help you. You actually didn't tell me what you did. For instance, I don't even know if you clicked the send button, copied the address you want to send to, selected blackbytes and were unable to send. It's interesting how you seem to be pissed off after receiving help
.
Anyway, back to the help
. Do you have the latest release on both devices? Are both of them synced?
I was not pissed off with you, sorry if I've given this impression. In fact, thank you for your help. And I am a big fan of Byteball, and I have been holding bytes already for a year, and I'm quite used to the interface, therefore I'm sorry when I find something not user-friendly which can be a serious obstable to a wider adoption.
So that's what I did:
1. I've paired the apps on two PC Windows devices, both apps are the latest light wallet 2.2.0
2. At this point as I went to send blackbytes I realized the dropdown menu of the available addresses of paired devices was not active.
3. I've asked on forum and you gave me a kind suggestion which I've followed.
4. Following your instructions I could actually get the destination address to appear in the field where you usually would get it by the way of the drop down menu, but as I've clicked send I've got the mistake: "Impossible to send the payment: precommit callback failed: [a string of text]: conflicting spend proof in inner unit [a string of text]"
It's not a big sum of blackbytes, it's worth 4$ in total now so it's not even worth the time of writing this post. But the point is that if there is a problem it must be solved, if we care about Byteball.
