|
Jilixi
|
 |
March 02, 2014, 11:53:18 PM |
|
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 |
Owner of BlackCoin Store - BlackCoin StoreBC: BNatbck1SDJebHRMQemkUEFPVZR9uLHLrM BTC: 161EcdmbgmxpZMk2ssZCjGQqB6gypduu97 |
|
|
|
|
|
|
|
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, which will follow the rules of the network no matter what miners do. Even if every miner decided to create 1000 bitcoins per block, full nodes would stick to the rules and reject those blocks.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
ny2cafuse
Legendary
 Offline
Activity: 1582
Merit: 1002
HODL for life.
|
|
March 02, 2014, 11:54:30 PM |
|
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. |
Community > Devs
|
|
|
|
barryzand
|
|
March 03, 2014, 12:01:18 AM |
|
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 i hope so man... were getting lots of coins like this LOL |
|
|
|
|
|
phrozenspite
|
|
March 03, 2014, 12:02:48 AM |
|
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 that's how it's supposed to work anyways. look at the bitcoin fork last year, slush's pool found a bunch of blocks on a chain and was on the correct wallet, but they rolled it back to keep the exchanges and some others who were still running older versions of the software happy. |
|
|
|
|
24Kilo
|
|
March 03, 2014, 12:06:47 AM |
|
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
Thanks for the compliments! Fuse, myself, another private pool operator and another experienced miner just spent the last 6 hours working on a fix... running tests, compiling wallets, setting up temporary servers and whatever... we did this to help KDC recover from a rapidly deteriorating situation. All the fixes have been pushed to Github for Klondikecoin to review... plus he just confirmed the technical coin dev team was asleep!!! Of course, they are humans and need and deserve sleep... but since this is a team effort we volunteered our time and resources instead of waiting for another few hours for them to wake up and KDC to slide into a real mess. All the code and fixes is there for everyone to use. I can confirm that the compiled Windows wallet on the KDC homepage works... I used to to run a solo mining server... it may need a slight fix... but it is on the right block chain and will confirming transactions. BUT DO NOT MOVE KDC UNTIL ALL IS CONFIRMED BY DEV TEAM!!!So no need for the panic... Criptoe is not hard-forking KDC or organising a hostile takeover... we just provided a much needed community service in a time of need. |
|
|
|
|
|
hash.so
|
|
March 03, 2014, 12:07:53 AM |
|
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. 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 |
Hash.so mining pools with easy coin switching! vardiff, pplns, and 0% fee (1% default donation). Come join us! Currently we have 40 scrypt coins and adding new ones all the time. Support/request thread here.
|
|
|
|
barryzand
|
|
March 03, 2014, 12:10:15 AM |
|
with this difficulty and current blocksize were getting more coins an hour then with the old blocksize lol  |
|
|
|
|
Sparkzor
Member
Offline
Activity: 112
Merit: 10
|
|
March 03, 2014, 12:11:24 AM |
|
with this difficulty and current blocksize were getting more coins an hour then with the old blocksize lol But we don't know which blockchain is the correct one. The coins that is mined at criptoe is worthless if it's not the longest blockchain as I understand it. |
|
|
|
|
|
Jilixi
|
|
March 03, 2014, 12:11:27 AM |
|
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. 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 I can confirm this, you are not on the longest chain. |
Owner of BlackCoin Store - BlackCoin StoreBC: BNatbck1SDJebHRMQemkUEFPVZR9uLHLrM BTC: 161EcdmbgmxpZMk2ssZCjGQqB6gypduu97 |
|
|
|
24Kilo
|
|
March 03, 2014, 12:12:29 AM |
|
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 You are not connecting to 'our' network... you are connecting to the network which the dev team compiled and supplied widows wallet is on... we did not create our own network... we only fixed the pool wallet so it would connect to the personal wallet network... that is what seems to have caused the fork. Agreed - my Windows server wallet is about 2 blocks ahead... hmmm... |
|
|
|
|
ny2cafuse
Legendary
Offline
Activity: 1582
Merit: 1002
HODL for life.
|
|
March 03, 2014, 12:14:02 AM |
|
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 |
Community > Devs
|
|
|
|
LeBarton
|
|
March 03, 2014, 12:19:39 AM |
|
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
Thanks for the compliments! Fuse, myself, another private pool operator and another experienced miner just spent the last 6 hours working on a fix... running tests, compiling wallets, setting up temporary servers and whatever... we did this to help KDC recover from a rapidly deteriorating situation. All the fixes have been pushed to Github for Klondikecoin to review... plus he just confirmed the technical coin dev team was asleep!!! Of course, they are humans and need and deserve sleep... but since this is a team effort we volunteered our time and resources instead of waiting for another few hours for them to wake up and KDC to slide into a real mess. All the code and fixes is there for everyone to use. I can confirm that the compiled Windows wallet on the KDC homepage works... I used to to run a solo mining server... it may need a slight fix... but it is on the right block chain and will confirming transactions. BUT DO NOT MOVE KDC UNTIL ALL IS CONFIRMED BY DEV TEAM!!!So no need for the panic... Criptoe is not hard-forking KDC or organising a hostile takeover... we just provided a much needed community service in a time of need. Thanks for your help. It's good to see dedicated miners like you working hard for this coin. |
|
|
|
|
|
Jilixi
|
|
March 03, 2014, 12:20:33 AM |
|
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 We need a statement from the devs that this is ok, compile release wallets for the public and be done with it, I can compile the mac wallet as soon as I get the green light. |
Owner of BlackCoin Store - BlackCoin StoreBC: BNatbck1SDJebHRMQemkUEFPVZR9uLHLrM BTC: 161EcdmbgmxpZMk2ssZCjGQqB6gypduu97 |
|
|
rynomite
Newbie
Offline
Activity: 3
Merit: 0
|
|
March 03, 2014, 12:22:33 AM |
|
Yeah.. My new windows wallet that I started solo mining against about 8 hours ago is 2 blocks ahead of the CripToe pool.
|
|
|
|
|
ny2cafuse
Legendary
Offline
Activity: 1582
Merit: 1002
HODL for life.
|
|
March 03, 2014, 12:25:06 AM |
|
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
|
Community > Devs
|
|
|
|
barryzand
|
|
March 03, 2014, 12:25:57 AM |
|
Someone is DDOS'ing the CripToe.Com pool. Payouts have been shut down for now.
Looks like someone didn't like us encroaching on their forking profits.
-Fuse
serious?? i'm not having any issues reaching the site... |
|
|
|
|
ny2cafuse
Legendary
Offline
Activity: 1582
Merit: 1002
HODL for life.
|
|
March 03, 2014, 12:27:19 AM |
|
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.
|
Community > Devs
|
|
|
|
barryzand
|
|
March 03, 2014, 12:27:25 AM |
|
Yeah.. My new windows wallet that I started solo mining against about 8 hours ago is 2 blocks ahead of the CripToe pool.
and what does this mean for the pool? |
|
|
|
|
|
24Kilo
|
|
March 03, 2014, 12:27:52 AM |
|
And someone has just hammered the Windows wallet as well...
me thinks we have a big solo miner on a different fork...
|
|
|
|
|
KlondikeCoin (OP)
Member
Offline
Activity: 84
Merit: 10
|
|
March 03, 2014, 12:29:38 AM |
|
Hi, I'm currently doing further testing on the update provided by fuse, will confirm if this is the new official chain asap and push everyone to update, at the moment id either reccomend mining on that chain or not at all The windows wallet won't be correct as it will still be open to the same problem as before - we'll compile and update that asap, once we are sure which chain we're using etc 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
I doubt you're being ddos'd, it is probably because everyone is currently using you as the only node to re sync the blockchain |
|
|
|
|
|
