well i think they can... since criptoe pool is having a giveaway (you can win kdc) to all miners who mine at least 75% of 10000 blocks i think.. so i think they can calculate that
It's relatively easy to calculate with a GApps script that I co-wrote. I find out the rounds for a period of time, and then see who submitted shares to those rounds. Then it's just finding out who met the required round number. I'm sure there's a better way to do it via SQL and PHP, but I'm happy with the way the script works so I never dug in to how to do it that way. -Fuse |
|
|
|
I've seen this on one of my pools before. Not sure what the issue was, but a change in email address usually resolved it. For some strange reason the mail daemon fails to send to certain email addresses. Contact the pool OP with another email address and ask them to change it in the DB, then try again. It might resolve the issue. -Fuse |
|
|
|
I do sincerely and always have wished KDC the best of luck in the market. It's my favorite coin. I've held every single one I've mined since day 1. Though these days I'm starting to question exactly why.
I'm sorry, mate. You're right about all your points. I'll shut up now. Let me know when you're ready to leave though. I'll buy your KDC and throw it up for a block bonus reward, and give it back to the community. -Fuse |
|
|
|
Not that I'm taking sides, but a pool 'owner' 'fixing' a block chain in the absence of the dev team then telling people to join your fork regardless of your intentions raised every security hair on my neck the other night.
Just like any healthy market this community needs people who have a contrarian view to things especially if they jeopardize the coins value or security.
Don't hate us embrace us!
I can understand your skepticism of my fix. The beauty of using github as a code repository though is that you can see what I changed. I've been around long enough to see these things happen in the past. Hell it just happened with TAG, and I did the same fix for my pool. If you look at the code, all it did was limit who could connect to you. You can do this manually with IPtables in linux, or you can code it in the client. I coded it in the client as I was almost 100% sure that the issue was older clients submitting erroneous blocks to the chain. I just want to clear up something though... it wasn't "my fork". I resynced the wallet numerous times until I got on the fork with the highest block height(which I was told was the highest block height by the community). I just pushed a fork along. At that point really, any fork would have worked. It's just best practice to try to push the furthest chain if it is valid. I agree with the point on contrary views comment you made. It's good to hear the other side. Hell, in the last week, I called out the owner/dev of Tagcoin. I've put 4 months into that coin, and I ran one of the largest pools for it. But the owner was ready to walk away from this forum. So I spoke up. That being said, the devs and a community leader made a pool. Sure the block bonus was definitely questionable, but the devs/leaders corrected that. That's good leadership. No need for Kheg to knock them on that. They are trying, just like the rest of us. +1 to your comments, but just two things... I'm not the 'owner' of a pool. I'm the owner of the pool. And my 'fix' was the fix. I'm here for the long haul... until the wheels fall off. I'll embrace anything that looks like a positive attempt to better the coin. -Fuse |
|
|
|
I have no problem with the coin. I have some serious questions about the rather misguided direction and decisions that its apparent "leaders" are taking now. It's almost like one hand is trying to apply a bandage to a wound while the other is trying to stab itself in the eye. But hey, who cares about that... OOOH SHINY!
Kheg, you need to take it down a level, mate. You crapped on the fix I made, you crapped on the people adopting it, and now you're crapping on the leadership of the coin. Over what? Creating an official pool? Let them create an official pool. If your pool, hell even my pool, is as good as we pride ourselves on making it, then what worries should we have if an "official" pool goes live? We all get our chunk, and we all contribute. However, since the fork, the only thing I've seen you contribute is FUD and snide remarks. If you don't want to be a part of the community, and a productive part of the community at that, then go away. Shut down your KDC pool and let the community work on strengthening the coin network, and in turn the coin's future. Stop belittling the effort of others to make something of the coin, and in turn themselves. -Fuse |
|
|
|
Just a reminder: KDC.CripToe.Com is giving away a 1.6KDC block finder bonus! That's 10% per block you can bank on! -Fuse |
|
|
|
Waking up to good news this morning and no additional issues sure is nice. Now that things are settled, and the fix is official: KDC.CripToe.Com is once again accepting registrations. I want to publicly thank those of you that adopted the fix and moved the fork along on the right path. It was a team effort, and you guys really pulled through yesterday. Thanks, Fuse |
|
|
|
|
If it's worth anything, I can vouch for Vesper. He's a stand-up guy with solid character. I have traded with him in the past with private coin trades, and I can say without a doubt that he is worth trusting.
-Fuse
|
|
|
|
From previous post it appears the fork with the fix is unofficial, but other pools may be joining this fork.
From a security standpoint with out making any judgments on intention, the unofficial fork is not dev sponsored code and should be considered as such until KDC devs wake up from their nap!
Actually, KlondikeCoin already addressed this: @roastbeef - there was a problem with the update, a fix was supplied by another user and the wallet can be grabbed from here: https://github.com/ny2cafuse/klondikecoinAt the moment that will put you on the new official/unofficial chain. We will confirm 100% asap if we need to rollback or anything else. I'm currently updating some of our nodes and the block explorer so we can get a better idea of whats going on. The windows wallet will also need to be recompiled. The official github will be updated once we are 100% happy this has resolved everything. While they haven't made it "official" yet, they have addressed the update and started using it. -Fuse |
|
|
|
I have been watching this all unfold over the past few days. I truly hope that this is a new starting point for tagcoin. I started mining it months ago when the value was high, and I loved the concept of the coin and the whole business aspect of it. I was seriously considering selling off all my tag after the recent community debacle, but after reading the last few posts, I will keep them and might start mining again when the waters settle. Here's to hoping tag will rise once again and become the coin of the future!
+1 I think this will be a turning point for TAG. -Fuse |
|
|
|
Thanks for your work. Post a KDC address, when everything settles down, I have some for you  Same here Fuse, please post your KDC address.
No need, gents. Honestly, I just wanted to try to help out the community. When everything settles and is sorted out I'll be happy... that's good enough for me. Thank you CripToe Team !!! You guys rock!
Thanks to you guys for supporting us. You're the reason we do what we do. -Fuse |
|
|
|
I'm going to bed guys, see you later today.
Thanks for helping KDC, criptoe-team!
No problem, mate. I'm going to hang out for a little while longer, then step away from computer for the first time today. What a day! -Fuse |
|
|
|
|
Can anyone verify that multipools aren't mining KDC right now? I doubt any of them have followed this thread today.
-Fuse
|
|
|
|
I've verified that we and cryptofountain are on the same chain. By proxy, that means our pool is on the official chain. https://chunkypools.com/kdc/Criptoe is on the same chain as well. KDC.CripToe.Com is mining again. |
|
|
|
Maybe some background... we run both a public and private pool network... we noticed a fork... we were the first to announce it... we alerted the dev... we were told that the technical side of the dev time was asleep(literally)... we have been in constant contact with Klondikecoin... we made the choice to push ahead with a fix... the dev knew this... we spent nearly 4 hours of writing and testing the fix... we pushed everything to Github as soon as we confirmed that the fix worked for us... we informed the dev of the fix and code changes... we announce we had a fix and that the fix was on Github... the dev team has reviewed the fix... it has become the unofficial fix... and we have made a huge effort to not take over the network including closing pool registrations... and as far as I know the technical dev team has not yet woken up.
Would have you preferred that we let KDC burn?
In addition, the second we mined the first block and verified it working, I was on the thread letting people know we had a initial fix. There was no secrecy. If you'd like I'll pull up the exact time of the block and the time of my announcement. -Fuse Edit: Announcement was made at 3:16:18PM forum time about the github fork.
At 18:47:17PM, my server time(3:47:17PM forum time), we found the first block. At that time I verified that it was broadcast to another pool op.
At 3:50:24PM forum time, I made an announcement that we were mining. That's 31 minutes between when I announced the code, and when we found our first block, and then 3 minutes to when we announced it in the forums.Kheg, you can go ahead and verify if you'd like. -Fuse |
|
|
|
Kheg, for god sake. It's possible that this is a temporarily solution. I don't know. Even if it's not, what does it matter? If the pool team did the same thing the developers was going to do, but did it faster should devs decline the help and then rewrite the same thing? I think it's a good thing that the community is helping the developer team, don't you? I'm not one of the developers but I and a few more are helping them anyway. Is that wrong too? Oh and Kheg, no offense but what are you doing to help the community at the moment? Except deprecate the developer team. Criptoe started for a little while there btw, then you shut it down  It's one thing to help. It's another thing to create a fork and then just "slide it out there". The fork was already there, kheg. All I did was push a fork along. It's what would need to have happened anyway. One fork needs to be correct. I asked the community what was the highest fork, and I tried to push that along. Not to be mean, but you honestly need to read a little about how forks happen, and how they are fixed before you start screaming from your soapbox. -Fuse |
|
|
|
Wait wait wait... you're telling me that a "fix" was pushed by someone OTHER than the dev team? And you're asking us to willingly get on a fork run/started by a rogue pool?
That's freaking ridiculous.
To top it off, that means Criptoe has had EXCLUSIVE access to this fork for how long now at a ridiculously low difficulty?
I'm sorry... this is bullshit.
Cool your jets, turbo. That's the beauty of open source... it's open for anyone to modify. I announced the pool was up and running as soon as I announced the code change. There was no "exclusive access". Everyone was able to download the code if they wanted. On another note, something isn't right on CripToe. Restarting services right now. It might take a few minutes. |
|
|
|
Delete all the files from your config folder, with the exception of your wallet.dat file, and restart. -Fuse Edit: Error is probably: "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade." |
|
|
|
ok, I can set this up. do you have new nodes?
You can add me right away with : My peer info list, as follows: {
"addr" : "178.32.52.52:52640",
"services" : "00000003",
"lastsend" : 1393808796,
"lastrecv" : 1393808796,
"bytessent" : 83446074,
"bytesrecv" : 6236232,
"blocksrequested" : 73438,
"conntime" : 1393803778,
"version" : 70003,
"subver" : "/Satoshi:0.8.6.2/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "148.251.70.243:10691",
"services" : "00000003",
"lastsend" : 1393808796,
"lastrecv" : 1393808796,
"bytessent" : 99063554,
"bytesrecv" : 3221429,
"blocksrequested" : 84986,
"conntime" : 1393804960,
"version" : 70003,
"subver" : "/Satoshi:0.8.6.2/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "184.69.136.30:40517",
"services" : "00000003",
"lastsend" : 1393808796,
"lastrecv" : 1393808771,
"bytessent" : 90489688,
"bytesrecv" : 2994851,
"blocksrequested" : 79063,
"conntime" : 1393805640,
"version" : 70003,
"subver" : "/Satoshi:0.8.6.2/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "37.59.28.23:56680",
"services" : "00000003",
"lastsend" : 1393808796,
"lastrecv" : 1393808796,
"bytessent" : 36041264,
"bytesrecv" : 1905696,
"blocksrequested" : 36940,
"conntime" : 1393806389,
"version" : 70003,
"subver" : "/Satoshi:0.8.6.2/",
"inbound" : false,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "88.208.205.38:59736",
"services" : "00000003",
"lastsend" : 1393808801,
"lastrecv" : 1393808801,
"bytessent" : 29834277,
"bytesrecv" : 7708829,
"blocksrequested" : 30259,
"conntime" : 1393807955,
"version" : 70003,
"subver" : "/Satoshi:0.8.6.2/",
"inbound" : true,
"startingheight" : 4,
"banscore" : 0
},
{
"addr" : "94.23.152.226:54027",
"services" : "00000003",
"lastsend" : 1393808798,
"lastrecv" : 1393808798,
"bytessent" : 1399634,
"bytesrecv" : 189208,
"blocksrequested" : 5000,
"conntime" : 1393808771,
"version" : 70003,
"subver" : "/Satoshi:0.8.6.2/",
"inbound" : true,
"startingheight" : 0,
"banscore" : 0
} |
|
|
|
always! i had it set though... but like i said.. i dont want to update wallet with these settings for now... i'm waiting for dev response before i fuck up anything lol.. having said that i trust your pool since you even helped the devs with this  My only intention in my actions was to provide an immediate response to the problem at hand. I don't want to step on anyone's toes here. If I did, I apologize. I just have a vested interest in this coin succeeding, as well as my pool. If my fix doesn't solve the issue, then at least it's a step toward insuring that people update to the proper version. If it is the fix, then the devs need to keep on eye on these things in the future so this doesn't happen again. Again, I'm sorry if I over-stepped my bounds. I'm just a take charge kind of guy, and I hate waiting around for things that I can try to fix myself. -Fuse |
|
|
|
|
Show Posts
