well i put my auto payout to zero man... what is the max amount of coins i can held in "my" pool wallet? i dont want to add changes to my klondike folders without official backup of the devs  You can hold as many as you want on the pools. The pool just starts yelling at you to set a value if you go over the pool's set threshold. It's not a big deal. Just be careful with where you leave coins. -Fuse |
|
|
|
|
Changed my post to be more specific.
They are ddosing the stratum ports.
-Fuse
Edit: And it's over. Let's see if this continues. Payouts resumed.
|
|
|
|
|
Someone is DDOS'ing stratum on the CripToe.Com pool. Payouts have been shut down for now.
Looks like someone didn't like us encroaching on their forking profits.
-Fuse
|
|
|
|
But if I take the old code, add your changes and connect to "your" network, I can still create a new fork? At least to me it seems that way, I don't think you fixed the underlying issue. Also your fork is not the longest  84922 vs 84913 All my code does is change the wallet version number and limit nodes to only be able to connect with that version. If there is another issue, all this does is make sure that the version is eliminated as a possible variable. Who is on that chain, we are pushing along pretty fast right now, unless they are running my code without connecting to this version's network, we will pass them up pretty fast, or they will have lots of issues in a little bit. -Fuse Edit: block 84926 at 4:13PM PST |
|
|
|
I don't think it fixed the issue.
edit: new wallet was started with "-rescan -reindex"
Delete everything but your wallet.dat file and restart. We're pegging blocks on CripToe. -Fuse Please stop with the risk of everyone moving there and causing yet another fork? can we please calm down? You asume everyone to compile from your code and just go with it. Waiting for Dev ann Do you understand that if we are on the highest chain, it will be the proper fork? Essentially, the dev will need to verify the code, pull it, and then create a block checkpoint. Highest fork wins, mate. Right now, the pool is on the highest fork, and climbing. That's how this works. -Fuse Edit: Also, when a coin forks, you can't just wait around. You need to fix the issue before the forks grow too far apart and other forks happen. The only thing my change does was limit connections between nodes by only allowing newer clients to connect. It blacklists the old clients which probably caused the issue in the first place. Check my pull request on github, nothing fancy there. |
|
|
|
I don't think it fixed the issue.
edit: new wallet was started with "-rescan -reindex"
Delete everything but your wallet.dat file and restart. We're pegging blocks on CripToe. -Fuse |
|
|
|
|
KDC.CripToe.Com is running at highest block height with the my code change. WE ARE MINING, FOLKS.
-Fuse
|
|
|
|
Absolutely,
if a community fix can be sorted asap i'm happy to take a look and approve it and push everyone to update - Karl & Dave usually handle the bulk of the code however i cannot get hold of them as they both have work commitments early in the morning and have gone to sleep - as the update seemed to have gone fine. Dave usually wakes up at obscure times so should get my messages in the next few hours.
@fuse, i'll take a look
Klondike, and others... https://github.com/ny2cafuse/klondikecoin. Pull request submitted. Like I said, it could be a version issue, but without the original code, I can't verify. However, this is to test that anyway. It increases the version and protocol number and limits connections to only clients running that version(tested and verified). Essentially shutting out older clients. It's a first step to making sure everyone is updated. It may also solve the issues we are seeing, but I can't tell until we see it large scale. If you decide to compile and use this code, you will need to connect to another pool or node running it. But the pool or node will need to be on the correct chain. I'm reindexing (klondikecoind -reindex) right now to rescan the blocks, and I'm coming back up. Try the following addnode if you use the code: Like I said, it might not work, but it eliminates the variable. -Fuse |
|
|
|
|
Can someone verify the highest block height known right now?
-Fuse
|
|
|
|
Working on and testing a fix right now... I will report back.
If only the devs were in irc so we could all help out  Seriously, poor show. Well that's why I'm trying to work on a fix with a fellow pool op. Hang tight. -Fuse |
|
|
|
|
Working on and testing a fix right now... I will report back.
|
|
|
|
another oddity is that I cant get to the "pools" page on any of the mining pools I use.
That's a result of MPOS getting the fatal error I posted earlier. MPOS can't connect to the wallet, so it throws a PHP error that makes the page fail to load. That's how I knew the other pools were having the same issue. |
|
|
|
We are currently checking the seed nodes and code to check for errors.
ny2cafuse - if you have found any errors please suggest fixes on github and we'll take a look.
We'll update you as soon as we can/are sure there is a problem or what the problem may be.
Seed nodes aren't going to matter. It's an issue with bad clients still being connected. On some other coins, usually you can set the "badversion" option in the main.cpp file to a version that is known good. Then any client that submits a block to the chain via that node, and they get locked out. Without it, I think we've allowed older clients to connect and submit invalid blocks to the blockchain. Did you update the version and protocol numbers? If not, you need to do that, release an update with the new version and protocol number, and it will allow us to filter out the old clients via getpeerinfo. -Fuse |
|
|
|
|
Looking at the github code, it doesn't show a version change for the V2 code, nor code change to limit connections to only the proper wallet version. Was this done, or was the block reward the only thing changed?
If this wasn't done, this would cause a major problem on the blockchain. Can the devs please verify this was done. If it wasn't, this is going to go downhill really fast until that is resolved.
-Fuse
Edit- on second glance, it doesn't appear that anything was changed in the version.h file. If this wasn't changed, along with the version requirements in the main.cpp file, you just released a client that was bound to fork and break. There is nothing stopping another client from connecting and inputting invalid blocks into the chain.
Where is the original source located? I would like to compare the code.
|
|
|
|
It's causing a fatal error on MPOS: [02-Mar-2014 20:40:02 UTC] PHP Fatal error: Uncaught exception 'Exception' with message 'RPC call did not return 200: HTTP error: 500 - JSON Response: [-2] Safe mode: Warning: Displayed transact$
Stack trace:
#0 /var/www/MPOS/cronjobs/blockupdate.php(39): jsonRPCClient->__call('getblock', Array)
#1 /var/www/MPOS/cronjobs/blockupdate.php(39): BitcoinWrapper->getblock('fdf035ff214d057...')
#2 {main}
thrown in /var/www/MPOS/public/include/lib/jsonRPCClient.php on line 117 Personal wallet is borked now too. Not to mention that it appears that we were on another fork of the chain. We were last mining at a difficulty of 3-4, with a total network hashrate of around 350. Something isn't right. -Fuse |
|
|
|
@ criptoe pool
PLS! add back the normal dashboard features... only displaying tekst is just too boring LOL
and can the day estimate be fixed? i think its still calculating on 77 coin blocks
We are working to get this fixed something has gone awry... apologies. Switched back the old MPOS... but there are still some bugs... pool still mining... and is reporting the right block reward of 16... It appears that the client is now throwing an error related to clients requiring an upgrade. I'm guessing this is happening on all the pools right now. We are shutting down mining until the devs release a statement. -Fuse |
|
|
|
Looks good Fuse And that is why I switched to Fuse's pool. Something is not right over at cryptovein... Thanks for the props, and the support!  I'm working right now to get the network hashrate working again in the dashboard. Like I said, it's an early release, so there will probably be some things missing, but the front end/back end connections are the same. All the math is the same. It's just a new look. So if you spot something that isn't right, please do PM me so I can look into it. Thanks, Fuse |
|
|
|
84583 104 left alex1399 02/03 11:44:03 8.01 77.00 32,823 52,115 11,696 35.63
84579 100 left emik 02/03 11:39:39 8.11 77.00 33,206 61,545 32,944 99.21
coinarmy is definitely on a fork. Their email form isn't working for me.
Ill pm the pool op, he had said he'd updated obviously something went wrong. Abe is back up (i was just restarting it) If he's updated the client, more than likely he has his MPOS config for block reward set to a "fixed" value of 77, rather than "block". So he is probably going out of pocket right now because the wallet is only taking in 16 coins, and he's crediting for 77. -Fuse |
|
|
|
|
Just a reminder:
POT.CripToe.Com is still giving away 20POT block finder bonuses.
Also, I have transitioned the site over to a new MPOS theme. It is still in early development, but it is almost a 100% replacement of the old theme. There are a few charts and graphs that haven't been coded yet, but it's a faster cleaner interface that will work on any device. I will be making small style and color changes over the next few days.
Thanks,
Fuse
|
|
|
|
|
KDC.CripToe.Com is running fine with the new fork.(as pictured in tminer's post above)
We have officially transitioned over now. From here on out, we are doing a 1.6KDC block reward, and we are in the first round for the new jackpot system.
I have transitioned the site over to a new MPOS theme. It is still in early development, but it is almost a 100% replacement of the old theme. There are a few charts and graphs that haven't been coded yet, but it's a faster cleaner interface that will work on any device. I will be making small style and color changes over the next few days.
Thanks,
Fuse
|
|
|
|
|
Show Posts
