ck, is it possible to make a support for reconnect command? i think this is a problem with MRR service There's supposed to be support, though I believe it broke somewhere along the line. I'll look into it when time permits. This is now fixed in git master.
|
|
|
This has been misbehaving for the last week or so. Any chance it could get a kick?
|
|
|
Still no idea why it got deleted here, but I moved the question to the KNC thread out of respect to some mystery person who deleted it here for unknown reasons. Overall, very strange.
Probably just some trigger happy mod that misinterpreted the discussion. Oh wait I'm the only active mod in mining.
|
|
|
[2016-09-17 04:27:38.472] Possible block solve diff 449192759803.872620 ! [2016-09-17 04:27:38.677] BLOCK ACCEPTED! [2016-09-17 04:27:38.677] Solved and confirmed block 430218 by 35JcVKhQiWgbTaBUHNnnod5o6do9r75Jg3_MRR8 [2016-09-17 04:27:38.677] User 35JcVKhQiWgbTaBUHNnnod5o6do9r75Jg3:{"hashrate1m": "1.97P", "hashrate5m": "1.93P", "hashrate1hr": "1.92P", "hashrate1d": "690T", "hashrate7d": "203T"} [2016-09-17 04:27:38.677] Worker 35JcVKhQiWgbTaBUHNnnod5o6do9r75Jg3_MRR8:{"hashrate1m": "1.97P", "hashrate5m": "1.92P", "hashrate1hr": "1.91P", "hashrate1d": "683T", "hashrate7d": "185T"} [2016-09-17 04:27:38.677] Block solved after 36623100600 shares at 16.2% diff
Well, luck's been rather good...
|
|
|
This has become a posting dumping ground for sigspammers and the question was answered long ago (which is basically no) so I'm locking the thread. If the opening poster wishes to ask a different question they can start a new thread.
|
|
|
Some one did : 17LAEZKNBCysBpVdggWJhqMFjkjMDSy6uB
[2016-09-16 12:54:46.079] Possible block solve diff 1465214763147.596680 ! [2016-09-16 12:54:46.303] BLOCK ACCEPTED! [2016-09-16 12:54:46.303] Solved and confirmed block 430118 by 17LAEZKNBCysBpVdggWJhqMFjkjMDSy6uB.port80 [2016-09-16 12:54:46.303] User 17LAEZKNBCysBpVdggWJhqMFjkjMDSy6uB:{"hashrate1m": "166T", "hashrate5m": "166T", "hashrate1hr": "168T", "hashrate1d": "101T", "hashrate7d": "22.3T"} [2016-09-16 12:54:46.303] Worker 17LAEZKNBCysBpVdggWJhqMFjkjMDSy6uB.port80:{"hashrate1m": "166T", "hashrate5m": "166T", "hashrate1hr": "168T", "hashrate1d": "101T", "hashrate7d": "22.3T"} [2016-09-16 12:54:46.303] Block solved after 33865001119 shares at 15.0% diff
https://www.blocktrail.com/BTC/block/000000000000000000c01a1c765dc5717ddb1c03324480a8f3b9e0fa8191e673
|
|
|
Just a brief notification that the redirection gateway at solo.ckpool.org will be going down for maintenance approximately 36 hours from now. The DNS has been updated to direct miners to the stratum server so if you are connected on port 3334 or your miners don't support redirection, they will disconnect when this maintenance begins but assuming your mining software properly rechecks dns then they will automatically reconnect to the stratum server without any interruption.
Miners already connected to the stratum server (which is most miners except for rentals) will not be affected by this downtime.
In short, most of you won't notice anything but I will notify once more when this maintenance is over.
The maintenance has been put off for another 3 weeks so this no longer applies. This maintenance is now complete. Did anyone notice anything?
|
|
|
ck, is it possible to make a support for reconnect command? i think this is a problem with MRR service There's supposed to be support, though I believe it broke somewhere along the line. I'll look into it when time permits.
|
|
|
Another block. by 1JzmafJYuuj7E3GFZ2MKj9bV4sqWLY8VRc. Nice!! With only 38th.
https://www.blocktrail.com/BTC/block/00000000000000000214b5ef43ca61e5efcd43b43c1d5ce2d684f2e6489f6a3d[2016-09-15 05:41:06.129] Possible block solve diff 528374390038.501343 ! [2016-09-15 05:41:06.304] BLOCK ACCEPTED! [2016-09-15 05:41:06.305] Solved and confirmed block 429912 by 1JzmafJYuuj7E3GFZ2MKj9bV4sqWLY8VRc.worker50 [2016-09-15 05:41:06.305] User 1JzmafJYuuj7E3GFZ2MKj9bV4sqWLY8VRc:{"hashrate1m": "36.3T", "hashrate5m": "38.5T", "hashrate1hr": "38.4T", "hashrate1d": "37.6T", "hashrate7d": "35.7T"} [2016-09-15 05:41:06.305] Worker 1JzmafJYuuj7E3GFZ2MKj9bV4sqWLY8VRc.worker50:{"hashrate1m": "4.69T", "hashrate5m": "4.69T", "hashrate1hr": "4.78T", "hashrate1d": "4.67T", "hashrate7d": "4.65T"} [2016-09-15 05:41:06.305] Block solved after 6725015660 shares at 3.0% diff
|
|
|
[2016-09-14 19:04:37.552] Possible block solve diff 4503376040763.755859 ! [2016-09-14 19:04:37.698] BLOCK ACCEPTED! [2016-09-14 19:04:37.698] Solved and confirmed block 429853 by 1FCAu2uKSRG1bidxMnRmNDLU71BYpGarfh [2016-09-14 19:04:37.698] User 1FCAu2uKSRG1bidxMnRmNDLU71BYpGarfh:{"hashrate1m": "3.7P", "hashrate5m": "2.8P", "hashrate1hr": "664T", "hashrate1d": "33T", "hashrate7d": "8.7T"} [2016-09-14 19:04:37.698] Worker 1FCAu2uKSRG1bidxMnRmNDLU71BYpGarfh:{"hashrate1m": "3.7P", "hashrate5m": "2.8P", "hashrate1hr": "664T", "hashrate1d": "33T", "hashrate7d": "8.7T"} [2016-09-14 19:04:37.698] Block solved after 87016386541 shares at 38.5% diff
|
|
|
Thank you for your wise words -ck
Tip finally went through c60949e9409df0f79ea040fa82a906e4cf4c2ab6e00047b094972b7a34b4ed70
Awesome, congrats on the block solve and thanks for donation! (You can't send money till the block has matured; well you can send it but it won't go anywhere till it matures.)
|
|
|
Please stick to the original poster's question. Do not use this thread as an opportunity to discuss other unrelated altcoin mining.
|
|
|
The original poster has not returned and the correct answer, "no" has been done to death making this thread now pointless and since GPU mining has nothing to do with bitcoin mining I'm locking this thread. Start another one in the correct place if you wish to continue discussing this please.
|
|
|
[2016-09-10 02:52:12.742] Possible block solve diff 258865204076.981262 ! [2016-09-10 02:52:12.885] BLOCK ACCEPTED! [2016-09-10 02:52:12.885] Solved and confirmed block 429098 by 1Gkru4p96rxyTZRxDefHYpGQHeUDaXwc89.proxy [2016-09-10 02:52:12.885] User 1Gkru4p96rxyTZRxDefHYpGQHeUDaXwc89:{"hashrate1m": "103T", "hashrate5m": "108T", "hashrate1hr": "106T", "hashrate1d": "106T", "hashrate7d": "66.8T"} [2016-09-10 02:52:12.885] Worker 1Gkru4p96rxyTZRxDefHYpGQHeUDaXwc89.proxy:{"hashrate1m": "68.5T", "hashrate5m": "72.3T", "hashrate1hr": "64.7T", "hashrate1d": "62.5T", "hashrate7d": "39T"}
https://www.blocktrail.com/BTC/block/0000000000000000043f5345dd0ffddc9577f984ea235540010b0f1a24de91e8
|
|
|
p.s. uthash.h - UTHASH_VERSION 2.0.1 - Give me a feedback please if it was not a good idead, but the Cgminer is working also perfect with it.
You want feedback? Sure. Updating uthash does precisely nothing.
|
|
|
but I would like to ask kano and or ck to pm me in the future if there is a problem with something I am doing on the site. I in turn will do the same with them.
You weren't doing anything wrong. I had zero intention of getting involved and making a judgement call on fubly's work. However, you asked me to sign off on it which is when I spoke up about my concerns. I still think if you're happy with the product he generates then it makes no difference what I think, but if you want me to bless it, I cannot do that for the reasons I've outlined. Getting Kano to sign off on his work is likely 100x harder. The language barrier is not helping the discussion either, where fubly is asking fellow German to explain why he might be accused of dishonouring the license requirements of the GPL when Kano's concern there is fubly's previous project, and Kano would refuse to "forgive and forget" unless fubly goes back and releases all the hidden code and retracts claims of improved performance.
|
|
|
[2016-09-02 23:48:42.439] Possible block solve diff 6338810159156.529297 ! [2016-09-02 23:48:42.667] BLOCK ACCEPTED! [2016-09-02 23:48:42.667] Solved and confirmed block 428055 by 1D6jWP3f9C8YevncEYiB7EZiuhkt4VypoW [2016-09-02 23:48:42.667] User 1D6jWP3f9C8YevncEYiB7EZiuhkt4VypoW:{"hashrate1m": "4.48P", "hashrate5m": "4.35P", "hashrate1hr": "3.65P", "hashrate1d": "492T", "hashrate7d": "354T"} [2016-09-02 23:48:42.667] Worker 1D6jWP3f9C8YevncEYiB7EZiuhkt4VypoW:{"hashrate1m": "4.48P", "hashrate5m": "4.35P", "hashrate1hr": "3.65P", "hashrate1d": "492T", "hashrate7d": "354T"} [2016-09-02 23:48:42.667] Block solved after 765223287753 shares at 346.6% diff
https://www.blocktrail.com/BTC/block/0000000000000000002c6782d427916ee5f207d62c02ef52f63f6d92cf10bbec
|
|
|
Cost is why I suggest filing with the FTC. IF the gov thinks there is is a valid case they bear the burden of pursing it. If the infringement is as cut and dry as Kano et al say, then given the size of Bitmain's market I'd think the FTC and their counterparts in other countries would be very interested. Would certainly make for some nice headlines I said they do eventually comply with it so there's no case to bring up against them. I doubt suing fubly would serve much purpose...
|
|
|
Well it's broken in that it's in violation of gpl. And since Kano ck are so bent out of shape about it I can't understand why they don't do something about it. Put their money where their mouth is and force bitmain to open source the code or face a hefty fine. Or is it that the gpl is a joke and no one actually ever does that? Bitmain skirt around the edges of legality with the GPL. You are obliged to provide code to any binaries you distribute within 30 days of being asked if someone has received those binaries and requested the source to them. Bitmain has always ended up releasing source code though it often takes longer than 30 days which is usually when Kano starts getting loud about them breaking the GPL - however if no one asks for the source code, and only those in possession of the binaries have that right, then they're not obliged to do anything. This is totally different to the fubly+cgminer+cryptoglance story which is the main complaint on this thread. As for pursuing companies breaking the GPL through law, that takes money and internationally is close to futile when it comes to China. We're not big companies with big budgets to burn on lawsuits with only a borderline chance of success, and I doubt it will lead to any great recompense on our part should we win. But as I said, Bitmain eventually have complied.
|
|
|
|