ok I downloaded the latest wallet, and resync from scratch and on block 95..are we forked?
Vegas
Yes, we rolled back to block 48 and forked. We're all good now. |
|
|
|
Not syncing and one active connection on the network.
It pools dont update, this version will be useless... need find the pool guys (with priority the suprnova guy)... Once block 49 is found, all wallets will show as synced. I could be wrong, but how is a block to be found if the wallet is not in sync? Once the pools update, the blocks will run smoothly again. I'm not in a pool, solo mining. So if the whole thing depends on pools, something is wrong. You can solo mine, but more than likely you won't find a block at the moment. If you can find a block and get the chain running, that would help. |
|
|
|
Not syncing and one active connection on the network.
It pools dont update, this version will be useless... need find the pool guys (with priority the suprnova guy)... Once block 49 is found, all wallets will show as synced. I could be wrong, but how is a block to be found if the wallet is not in sync? Once the pools update, the blocks will run smoothly again. |
|
|
|
Not syncing and one active connection on the network.
It pools dont update, this version will be useless... need find the pool guys (with priority the suprnova guy)... Once block 49 is found, all wallets will show as synced. |
|
|
|
ATTENTION: Please Update To The Newest Wallet We have rolled back the chain to block 48. New Windows walletRe-Sync completely. Delete everything in your .xRadon folder except for your wallet.dat. Pools please do the same and update immediately. Can u talk directly with the suprnova guy? If he doenst change the wallet, we will have a lot of problems! PM'd. They should be up soon. |
|
|
|
|
ATTENTION:
Please Update To The Newest Wallet
We have rolled back the chain to block 48.
Re-Sync completely. Delete everything in your .xRadon folder except for your wallet.dat.
Pools please do the same and update immediately.
|
|
|
|
Windows wallet pulled for rollback. Stand by. Do not update yet.
Rollback to what? To get the chain started we are rolling back a few blocks to fork to a proper nTargetTimespan |
|
|
|
|
Windows wallet pulled for rollback. Stand by. Do not update yet.
|
|
|
|
will be in times easier to check the new code on testnet and if everything is OK to relaunch the whole blockchain
More than likely our next option. what why you want to relaunch? just make the hard fork sooner. NO, no relaunch! You will fuck even more the coin! Just make the hardfork sooner!!! Not relaunch the chain, rollback. My mistake, I should have clarified that. |
|
|
|
will be in times easier to check the new code on testnet and if everything is OK to relaunch the whole blockchain
More than likely our next option. |
|
|
|
I think the best solution is for us ALL agree to back off this and limit the hashspeed. Say 500Mhs MAX
Vegas
The problem is getting past block 51. The network is working at finding block 52 @ 512 difficulty, but it can't. If the chain is stuck, that's a whole different issue but for now we need to get past this block. If the times prove to be this slow, I can set the fork to happen much earlier. Edit: We're looking at quite a long time to find the next block at this point. |
|
|
|
|
Windows wallet will be up shortly. Hard fork at block 150.
|
|
|
|
|
Github updated. Ocminer, can you verify the fork?
|
|
|
|
@OCMiner @MinerPools, your pools are not mining to the network.
Not mining to the network? To what then? The wall? Do you mean there is a fork again or what? It seems the hash rates of the pools jump on and off of the network. Dude, seriously.. Think before you write.. No one is jumping off or on the network, the problem is you have set a wrong nTargetTimespan in the source.. This variable is NOT setting the blocktime i.e. 60 seconds per block, it sets the "look over the last blocks in this timespan to calculate the next diff" in the coin.. if you set this to 1 minute, it only looks at the last block and sets a diff which is much too high, the IvugeoMeoShitCoin Dev had the same problem with his coin. You have to set this to at least 5 mins, better 10 mins to get a working diff recalculation. If you don't know what you're talking about, its sometimes better to ask instead of writing anything that just comes into your mind.. So I guess we're gonna have to hard fork to a new retarget.. Let me get working on it. In the mean time, we've just got to live with slow blocks. Sounds good.. Please test the retarget before releasing an update or it will be a mess... you have to find the right value 5/10/15 minutes etc.. Will do. Everything will be working by the hard fork. Most likely the soonest time that it will be out is by tomorrow afternoon. |
|
|
|
@OCMiner @MinerPools, your pools are not mining to the network.
Not mining to the network? To what then? The wall? Do you mean there is a fork again or what? It seems the hash rates of the pools jump on and off of the network. Dude, seriously.. Think before you write.. No one is jumping off or on the network, the problem is you have set a wrong nTargetTimespan in the source.. This variable is NOT setting the blocktime i.e. 60 seconds per block, it sets the "look over the last blocks in this timespan to calculate the next diff" in the coin.. if you set this to 1 minute, it only looks at the last block and sets a diff which is much too high, the IvugeoMeoShitCoin Dev had the same problem with his coin. You have to set this to at least 5 mins, better 10 mins to get a working diff recalculation. If you don't know what you're talking about, its sometimes better to ask instead of writing anything that just comes into your mind.. So I guess we're gonna have to hard fork to a new retarget.. Let me get working on it. In the mean time, we've just got to live with slow blocks. |
|
|
|
@OCMiner @MinerPools, your pools are not mining to the network.
Not mining to the network? To what then? The wall? Do you mean there is a fork again or what? It seems the hash rates of the pools jump on and off of the network. BinPool work correct or not? Yes it appears to be working fine |
|
|
|
@OCMiner @MinerPools, your pools are not mining to the network.
Not mining to the network? To what then? The wall? Do you mean there is a fork again or what? It seems the hash rates of the pools jump on and off of the network. |
|
|
|
|
@OCMiner @MinerPools, your pools are not mining to the network.
|
|
|
|
|
Show Posts
