In fact - it's seems there are users / bots that try to send the 0.0006 GB before anyone else (also under my tutorial posts) to steal the reward :D This kinda solves the mistery!
Yeah, maybe happens also in my comments too because I have not yet been able to send anybody the fee because every address I check, already have been funded, sometimes within 5 minutes after posting.
Too bad that they don't know that 0.0006 GB is clear overkill because they only need to send as much as 49 588 Bytes (or 0.000049588 GByte) :D
When the wallet chooses which input to use for a payment, it will chose the input closest to, but not less than, the output required. The input closest to the 49,000 + fees will be chosen. If there are two identical and equally close inputs, I think the latest input is the one that will be used.
Hah, maybe that's the case :)
Just got request for this address:
https://explorer.byteball.org/#7CC5QETO365SSCRUEGHQAFY5LK6ZYMBC
But someone was faster :) But for the most part I think I was first? Will check it for the other addresses, thanks!
In fact - it's seems there are users / bots that try to send the 0.0006 GB before anyone else (also under my tutorial posts) to steal the reward :D This kinda solves the mistery!
Yeah, maybe happens also in my comments too because I have not yet been able to send anybody the fee because every address I check, already have been funded, sometimes within 5 minutes after posting.
Too bad that they don't know that 0.0006 GB is clear overkill because they only need to send as much as 49 588 Bytes (or 0.000049588 GByte) :D
When the wallet chooses which input to use for a payment, it will chose the input closest to, but not less than, the output required. The input closest to the 49,000 + fees will be chosen. If there are two identical and equally close inputs, I think the latest input is the one that will be used.
What? But then this "whoever funds first" rule is not correct? You would also need to fund the most accurate amount too, which is 49 588 Bytes?