kubuminer
|
|
May 25, 2015, 09:13:58 PM |
|
@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 thanks, the best.
|
|
|
|
ocminer
Legendary
Offline
Activity: 2688
Merit: 1240
|
|
May 25, 2015, 09:15:08 PM |
|
@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..
|
suprnova pools - reliable mining pools - #suprnova on freenet https://www.suprnova.cc - FOLLOW us @ Twitter ! twitter.com/SuprnovaPools
|
|
|
kampretkabur
|
|
May 25, 2015, 09:19:27 PM |
|
looks like a joke already., any option for scrypt mine? dont want to waste time here
|
|
|
|
hakbr
Newbie
Offline
Activity: 36
Merit: 0
|
|
May 25, 2015, 09:20:02 PM |
|
Diff is jumping like a crazy rabbit...
|
|
|
|
tm2013 (OP)
|
|
May 25, 2015, 09:24:22 PM |
|
@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
Legendary
Offline
Activity: 2688
Merit: 1240
|
|
May 25, 2015, 09:25:55 PM |
|
@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..
|
suprnova pools - reliable mining pools - #suprnova on freenet https://www.suprnova.cc - FOLLOW us @ Twitter ! twitter.com/SuprnovaPools
|
|
|
tm2013 (OP)
|
|
May 25, 2015, 09:29:50 PM |
|
@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.
|
|
|
|
vegasguy
Legendary
Offline
Activity: 1610
Merit: 1003
"Yobit pump alert software" Link in my signature!
|
|
May 25, 2015, 09:31:52 PM |
|
OC would you mind if the dev sent you the new code to look at first before release? We REALLY need it MUCH sooner than tomorrow afternoon, this diff is a nightmare @dev, you have a development fund. I STRONGLY urge you to use some of it and hire OCMINER to expedite the new fork. He can get this done MUCH faster, and get everyone moving forward. I want to post your coin on my site that is ranked #1-3 for searches for every coin on google, but not in the condition its in. Google ANY recent coin released in the last few months, Ill be at the top of the page. www.bitcoinlasvegas.netVegas
|
I want to make sure everyone knows that I just released my software called "Yobit pump alert". THis is custom software that uses an algo to detect the start of a pump here on yobit, the second it starts. YOu can even filter the coins you see by price. Most pumps start less than 100 sats , so you can easily filter the cheap coins, so they are the only ones displayed https://bitcointalk.org/index.php?topic=1945937.msg20241953#msg20241953
|
|
|
hakbr
Newbie
Offline
Activity: 36
Merit: 0
|
|
May 25, 2015, 09:39:07 PM |
|
It's almost impossible continue mining with this crazy diff... We REALLY need an update much sooner!
|
|
|
|
tm2013 (OP)
|
|
May 25, 2015, 10:24:44 PM |
|
Github updated. Ocminer, can you verify the fork?
|
|
|
|
vegasguy
Legendary
Offline
Activity: 1610
Merit: 1003
"Yobit pump alert software" Link in my signature!
|
|
May 25, 2015, 10:28:39 PM |
|
After github source is verified. Please post new windows binary on OP and report here. Thank you for your dedication. In the meantime Ill begin my article on the coin. 300-500 set of eyes per day will see it.
Vegas
|
I want to make sure everyone knows that I just released my software called "Yobit pump alert". THis is custom software that uses an algo to detect the start of a pump here on yobit, the second it starts. YOu can even filter the coins you see by price. Most pumps start less than 100 sats , so you can easily filter the cheap coins, so they are the only ones displayed https://bitcointalk.org/index.php?topic=1945937.msg20241953#msg20241953
|
|
|
idol
|
|
May 25, 2015, 10:30:38 PM |
|
dev passed the first test
|
|
|
|
tm2013 (OP)
|
|
May 25, 2015, 10:59:35 PM |
|
Windows wallet will be up shortly. Hard fork at block 150.
|
|
|
|
vegasguy
Legendary
Offline
Activity: 1610
Merit: 1003
"Yobit pump alert software" Link in my signature!
|
|
May 25, 2015, 11:03:53 PM |
|
Windows wallet will be up shortly. Hard fork at block 150.
Ok.. I think I like this dev! right on top of things. Its not the fact you made an error, its how you deal with it. Well done! +1000 Vegas
|
I want to make sure everyone knows that I just released my software called "Yobit pump alert". THis is custom software that uses an algo to detect the start of a pump here on yobit, the second it starts. YOu can even filter the coins you see by price. Most pumps start less than 100 sats , so you can easily filter the cheap coins, so they are the only ones displayed https://bitcointalk.org/index.php?topic=1945937.msg20241953#msg20241953
|
|
|
hakbr
Newbie
Offline
Activity: 36
Merit: 0
|
|
May 25, 2015, 11:05:28 PM |
|
Windows wallet will be up shortly. Hard fork at block 150.
Good job! But we will spend "a life" to reach block 150...
|
|
|
|
tm2013 (OP)
|
|
May 25, 2015, 11:17:50 PM |
|
|
|
|
|
hakbr
Newbie
Offline
Activity: 36
Merit: 0
|
|
May 25, 2015, 11:23:25 PM |
|
The hardfork cant be done earlier, like 80-100?? More than 50min at block 52... at this way, we will reach block 150 in a week (or more)... We cant even put more hashes (or the situation will be worse)....
|
|
|
|
vegasguy
Legendary
Offline
Activity: 1610
Merit: 1003
"Yobit pump alert software" Link in my signature!
|
|
May 25, 2015, 11:36:27 PM |
|
I think the best solution is for us ALL agree to back off this and limit the hashspeed. Say 500Mhs MAX
Vegas
|
I want to make sure everyone knows that I just released my software called "Yobit pump alert". THis is custom software that uses an algo to detect the start of a pump here on yobit, the second it starts. YOu can even filter the coins you see by price. Most pumps start less than 100 sats , so you can easily filter the cheap coins, so they are the only ones displayed https://bitcointalk.org/index.php?topic=1945937.msg20241953#msg20241953
|
|
|
tm2013 (OP)
|
|
May 25, 2015, 11:55:11 PM |
|
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.
|
|
|
|
hakbr
Newbie
Offline
Activity: 36
Merit: 0
|
|
May 26, 2015, 12:03:18 AM |
|
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. No, its not only the block 52... if you analise the pattern, after block 52 it will decrease the next 2 or 3 blocks to a minimum diff, than to a too high diff again, and it will take hours again...
|
|
|
|
|