Block Winner 310908
-
another message ive seen is
{ result: 'Passphrase does not match reward recipient', requestProcessingTime: 0 }that result boggles me a bit. shouldnt that say reward recipient does not match. or address does not match reward recipient.
someone was clearly up all night :D
-
When solo mining, if you get a green font "DL confirmed" message does that mean the network has received the DL?
-
So just briefly returning to my OP.... I can understand that it is possible that a 6 second deadline can be sent to a Pool and confirmed, but fail to make it's way into the network.
However what I find odd is the coincidence that the Winning deadline was later reported by the Pool as 6 Seconds but when checking the the Deadline in Block Explorer it is reported as being 6.4 Minutes?
I just happened to see this one, but does anyone have any idea how often this sort of thing happens? Makes me tempted to run 2 instances of the Miner so that all deadlines are submitted twice?
Rich
-
@RichBC This is speculation on my part - don't know if it's actually correct. The pool probably thought it won on your block - moved onto the next one. The actual block continued mining to the 6.4 minutes, and that propagated. When the pool realized it didn't actually win the block, it put the correct winner, but your time.
@Lexicon there is work being done for the next version of the wallet to allow better control over who the wallet peers with - so making a peerlist of pools will be possible.
-
@haitch Sound likely. I actually saw it report me as the winner, but then went away and came back some Blocks later and was surprised to see I was no longer the winner.
-
-
@tross I have one instance in my pool where the pool says someone wins for NEWS POOL but in fact it was another one who actually won. The sad part is, NEWS Pool paid our miner the burst. I don't know if it will be ever given back to the pool. Luckily, I found it out right away and sent Burst to the pool to avoid negative balance. :(
-
@jervis, that happens a lot when a pool's wallet sticks. Not sure how they reconcile the payout mistakes. Unless the admin for the pool sees the stuck wallet, every consecutive block is mistakenly won my one of the pool miners. If they post low DLs, before you know it the pool has paid distributions with 4 confirmations, then it's a done deal. Maybe they ask for refunds or back calculate and withhold from subsequent payouts. Messy.
-
This post is deleted!
-
@luxe update on the feature we spoke about. it turns out theres nothing brought back about the submit being not accepted.
im currently adding into the code something where if we hit a good deadline below lets say 1 hour. then it resubmits this to multiple online wallets.
ive tested it and so far it works. the other wallet ooks like it accepts the data. and it even returns me the string back to tell me its taken it. albeit almost 4 times slower. this shouldn't matter much as its called asynchronously
{ result: 'success', requestProcessingTime: 141, deadline: 893735 } new best deadline 893735 //External Api Call { status: true, data: { result: 'success', requestProcessingTime: 453, deadline: 893735 } }rather than make this a static list though. ill use http://util.burst-team.us:8888/network/json and pick the wallet's out of this json and use those.




