 Show Posts
|
|
Pages: « 1 [2] 3 4 »
|
|
I had 1000 XRP, added the trust to bitstamp, and my XRP went down to 999.
Where did it go and why?
|
|
|
|
|
Ripple looks interesting.
rPTjUHPSVDQbhizzzH6QV2BeHoKZFy16sy
|
|
|
|
I refuse to quote that lucko character any more - I think he just loves the conflict - every time he's quoted he has 5 more idiot things to say.
He says he's left the pool but he insists on posting here to troll slush.
The best thing we can do as a group is to ignore his posts and don't quote him. Eventually he'll get bored and maybe move to the BFL thread where he can troll all he likes.
I think most people know, they humour him. Surely everyone has noticed it is BTCGuild that he promotes in his signature. |
|
|
|
I've been mining with 50Ghs for the 11th day now. Can you please evaluate the below log of earnings? Today I switched from diff8 to 6 and I think the rewards are coming more frequently and in a steadier manner. I plan to run it on 6 to get some more days worth of data to compare. Do you think I should set it lower?  the last record has 9 hours to go as of this post. I had no downtime, expect 2 occasions when the miners spent a few minutes offline Difficulty is pretty much just how big the calculation is that gets sent to you. It's used to control the rate of communication from you to the server. Rewards come in when a block is discovered so changing difficulty has no bearing whatsoever on frequency or steadiness. |
|
|
|
But can you say that I'm wrong? No you can't!
What you're saying is the same as, "I drove my car down the road and it broke down, therefore the road is broken. Hey everybody don't drive down there it's broken". "But thousands of other cars are using the road perfectly well", someone replies. "But can you say it wasn't the road that broke my car!" comes the response. |
|
|
|
There is a problem with the pool and not sure why slush is not here to correct any issues.
What makes you say that? (Besides the chance that you may be Lucko's alter ego  ) Well from 8th of May my daily reward dropped from 0.101 to 0.052 and no I'm not anyones alter ego. Ahh I see, yeah pool must be broke |
|
|
|
There is a problem with the pool and not sure why slush is not here to correct any issues.
What makes you say that? (Besides the chance that you may be Lucko's alter ego ) |
|
|
|
And 6 hours it was  |
|
|
|
In the meantime one thing I was thinking of doing was detecting when a new block was found and saving the previous total shares score. It would be accurate down to (Block Discovered Time - Last Refresh Time) so would miss a few shares.
I have a ticker running on http://blockchain.info/latestblock which pings me when a new block is found - not perfect but good enough for what you need maybe... Cheers for the input, but I'd know when a new block was detected by reading the blocks feed. |
|
|
|
Hi all I have added a couple of new features. First ... the previous refresh worker data is now shown in brackets after the current data ... this is useful for checking back on and also ensuring that you are submitting shares on each worker. Secondly I have also totaled the worker data in a row at the bottom. I have now put the download in a zip. Version 1.0.0.1 is here: http://fileshosting.co.uk/files/mineminder.zipCheers  Thanks for the quick update. Will be great if you can add my share contribution for each ended round as part of the table at the bottom. Unfortunately, submitted shares per round don't come out of the API feed from Slush, maybe it can be implemented?! In the meantime one thing I was thinking of doing was detecting when a new block was found and saving the previous total shares score. It would be accurate down to (Block Discovered Time - Last Refresh Time) so would miss a few shares. |
|
|
|
Hi all I have added a couple of new features. First ... the previous refresh worker data is now shown in brackets after the current data ... this is useful for checking back on and also ensuring that you are submitting shares on each worker. Secondly I have also totaled the worker data in a row at the bottom. I have now put the download in a zip. Version 1.0.0.1 is here: http://fileshosting.co.uk/files/mineminder.zipCheers |
|
|
|
The bottom line, is less than 1% of the miners are having problems. That doesn't mean there aren't problems, but chances are it's not with the pool. That doesn't mean your doing anything wrong, but it could be a bad dns entry between you and slush, or some issue between your isp and the amazon servers, or any of thousands of other weird little things that can happen on the internet.
That's why your getting the response you are. If you report a problem, then slush checks everything on his end and finds everything is good. Then there is nothing he can do about it. And I now what your going to say next, slush hasn't reported back. Well I can assure you, he has seen your posts, and if there was anything he could do about it, it would have been done already.
A=B, and B=C, therefore A=C, maybe a little simplified, but the principal is sound.
Couldn't have put it better myself. |
|
|
|
Just realized I cocked up the size of the stats window on the last compile.  Just resize the form and it should snap to where it's meant to be.  |
|
|
|
Hiya I have made the very first version of MineMinder available here: http://fileshosting.co.uk/files/MineMinder_1.0.0.0.exe.7zNot sure if I need Slush's permission to call the API but I have limited the refresh to 10 seconds minimum for now. It's very simple, it just looks up my wallet address on loading (for ahem donations but nothing mandatory:)), then you can put your APIToken in the top and click refresh or enable the timer to refresh for you. It requires the DotNET 2.0 framework. Any problems and I'll try and monitor here for now. If it's worth it (and if anyone wants it) more features to come. Cheers  |
|
|
|
Thanks for the feedback. I'll try and finalize a version for release tomorrow that you all can use. Then if there's sufficient interest, I'll try and put some bells and whistles into it, one other idea I've had is the ability to log each call so that you can immediately reload your account and see how it was at a point in time  Cheers |
|
|
|
This is a windows app that I recently wrote to get my stats/account info in one place. It was just for me and a mate but thought I would tidy it up a bit and post to see if it is maybe a stupid idea or not. It has configurable Auto Refresh and shows current duration when minimized so you don't need it maximized to check for block discovery. If there was interest/demand I would consider a mobile version too with maybe email alert for things like block discovery, threshold alerts, reward checks, worker offline etc.  |
|
|
|
But not a connectivity issue - can ping just fine
C:\Users\Rachael>ping 56.192.78.3
Pinging 56.192.78.3 with 32 bytes of data:
Reply from 56.192.78.3: bytes=32 time=1ms TTL=255
Reply from 56.192.78.3: bytes=32 time=11ms TTL=255
Reply from 56.192.78.3: bytes=32 time<1ms TTL=255
Reply from 56.192.78.3: bytes=32 time<1ms TTL=255
Ping statistics for 56.192.78.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% l
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 11ms, Average = 3ms
But other servers can be pinged! |
|
|
|
C:\Users\Rachael>ping stratum.bitcoin.cz
Pinging stratum.bitcoin.cz [54.225.116.221] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 54.225.116.221:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Surely this is your issue as was posted earlier! |
|
|
|
Well it's very likely our hero knows all about what's been going on despite or because of all the caterwaul on the forums, from me included.
Your hero I think! Well over $1000 dollars a day should have afforded at least some public response from him or his representitive! |
|
|
|
|
