Re: BYTEBALL: Totally new consensus algorithm + private untraceable payments
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.
No problem and you are welcome
.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]"
Sounds like the "bytes" you have are possibly not valid... due to being used in another transaction. Not sure if it's referring to the "normal" bytes or the "blackbytes".
So, do you know if you are trying to send blackbytes that are no longer available? Did you at some point restore from an old backup or have the same wallet (same seed) running on more than one device or anything that you think could have somehow corrupted one or both the wallets?
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.
+1