Igotspots. You really should've included your nodes with the release. It could've saved the chain a lot of troubles.
Topic: [ANN] Copper Bars | Scrypt-Jane CPU | Accepted for Gold and Silver soon [CPR] - page 8. (Read 17251 times)
August 11, 2013, 05:02:11 PM
It's only been out for 2 hours an it's already at 40k blocks?
Igotspots. You really should've included your nodes with the release. It could've saved the chain a lot of troubles.
Igotspots. You really should've included your nodes with the release. It could've saved the chain a lot of troubles.
August 11, 2013, 05:02:05 PM
Please post your stats if you feel you are on a forked chain or are seeing random jumps. Everyone that's posted so far has the right stats for the network. I still have 5 rigs up with no issues...I'm really not seeing a fork of any kind from where I'm sitting. Not saying I don't trust you guys, but we can't fix it if we can't replicate the issue
Actually, it hasn't jumped for several minutes, perhaps it solved itself amongst the network, I'll take a screenie if it jumps back. All good now (aside from 55 orphans and 10 confirmed, but that's somewhat expected for now) 
August 11, 2013, 05:01:39 PM
All good now.
If you are having problems do not put nodes in the config file.
If you are having problems do not put nodes in the config file.
Awesome, thanks. I had a feeling it was just a bad node.
August 11, 2013, 05:01:21 PM
Is it possible that the 2 blockchains (Spots and CopperBars) are getting mixed up on some people's computers?
It looks like the Spots blockchain is about the size that some people are seeing on CopperBars.
I suggest people delete the nodes from their config files if they haven't already. It seems to be working alright for me after I did that.
It looks like the Spots blockchain is about the size that some people are seeing on CopperBars.
I suggest people delete the nodes from their config files if they haven't already. It seems to be working alright for me after I did that.
I'm mining Spots and CPR at the same time right now and still not seeing any funny issues. Yea, I removed the nodes from the OP, you shouldn't need them anyway the way it's set up you should connect automatically to the right nodes
August 11, 2013, 05:00:42 PM
All good now.
If you are having problems do not put nodes in the config file.
If you are having problems do not put nodes in the config file.
August 11, 2013, 04:59:00 PM
Please post your stats if you feel you are on a forked chain or are seeing random jumps. Everyone that's posted so far has the right stats for the network. I still have 5 rigs up with no issues...I'm really not seeing a fork of any kind from where I'm sitting. Not saying I don't trust you guys, but we can't fix it if we can't replicate the issue
August 11, 2013, 04:56:03 PM
Might as well restart now. More time used up on this means people will miss their coins more and not be willing to restart.
No point, yet. Everyone that is posting their stats has been posting accurate network stats...
August 11, 2013, 04:55:41 PM
@Spots
Do the only thing you can now.
Call this an Alpha Test and let everyone know this chain will not be accepted, There's really no way to fix this now.
Fix and relaunch.
Just a suggestion.
~BCX~
Do the only thing you can now.
Call this an Alpha Test and let everyone know this chain will not be accepted, There's really no way to fix this now.
Fix and relaunch.
Just a suggestion.
~BCX~
I really think it's going to be ok. Nobody is posting their "forked" info. Everyone is on the right chain so far that's posted...
August 11, 2013, 04:55:34 PM
Might as well restart now. More time used up on this means people will miss their coins more and not be willing to restart.
August 11, 2013, 04:54:49 PM
You're also good.
Let's see some posts or pics of the forked chains? Everyone has been synced up so far
August 11, 2013, 04:52:44 PM
August 11, 2013, 04:52:31 PM
16:47:34

getmininginfo
16:47:34

{
"blocks" : 40654,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00157376,
"errors" : "",
"generate" : true,
"genproclimit" : 4,
"hashespersec" : 71164,
"pooledtx" : 0,
"testnet" : false
}
This is the correct chain.
If you are seeing anything else, please post your getmininginfo along with your getpeerinfo so I can figure out the bad node(s)
Also, as above posts ask for... Even if it's just moving to a 24 second block timer would probably be for the best (that's still a 50% increase while still keeping it super low)
August 11, 2013, 04:50:34 PM
after running all night 44 transactions but only 5 paids i love spots and am running on them also and i love the idea and concept behind copper bars just way too many orphans for me
just trying to get a feel here: how many hashespersec?
"blocks" : 40664,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00157451,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 73896,
"pooledtx" : 0,
"testnet" : false
Ok, you are on the correct chain
August 11, 2013, 04:50:28 PM

{
"blocks" : 40733,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00157942,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 0,
"testnet" : false
}
August 11, 2013, 04:49:02 PM
after running all night 44 transactions but only 5 paids i love spots and am running on them also and i love the idea and concept behind copper bars just way too many orphans for me
just trying to get a feel here: how many hashespersec?
"blocks" : 40664,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00157451,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 73896,
"pooledtx" : 0,
"testnet" : false
August 11, 2013, 04:48:03 PM
16:47:34

getmininginfo
16:47:34

{
"blocks" : 40654,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00157376,
"errors" : "",
"generate" : true,
"genproclimit" : 4,
"hashespersec" : 71164,
"pooledtx" : 0,
"testnet" : false
}
This is the correct chain.
If you are seeing anything else, please post your getmininginfo along with your getpeerinfo so I can figure out the bad node(s)
August 11, 2013, 04:47:24 PM
Is it possible that the 2 blockchains (Spots and CopperBars) are getting mixed up on some people's computers?
It looks like the Spots blockchain is about the size that some people are seeing on CopperBars.
I suggest people delete the nodes from their config files if they haven't already. It seems to be working alright for me after I did that.
It looks like the Spots blockchain is about the size that some people are seeing on CopperBars.
I suggest people delete the nodes from their config files if they haven't already. It seems to be working alright for me after I did that.
Deleting the add nodes just prevents you from jumping around the forks and confines you to a particular chain. The add nodes were on different chains, thus the chain jumping.
There are still several long chains running.
If this chain isn't restarted I would hate to see the anger when quite a few people try to buy silver on spots exchange and can't because of the forking issue.
~BCX~
Right, but if the right blockchain has more nodes, that will be the one people get onto
August 11, 2013, 04:46:44 PM
Is it possible that the 2 blockchains (Spots and CopperBars) are getting mixed up on some people's computers?
It looks like the Spots blockchain is about the size that some people are seeing on CopperBars.
I suggest people delete the nodes from their config files if they haven't already. It seems to be working alright for me after I did that.
It looks like the Spots blockchain is about the size that some people are seeing on CopperBars.
I suggest people delete the nodes from their config files if they haven't already. It seems to be working alright for me after I did that.
Deleting the add nodes just prevents you from jumping around the forks and confines you to a particular chain. The add nodes were on different chains, thus the chain jumping.
There are still several long chains running.
If this chain isn't restarted I would hate to see the anger when quite a few people try to buy silver on spots exchange and can't because of the forking issue.
~BCX~
Yes, that's why we are running it for a week before we accept it, to get this shit worked out. I'm not ignoring your posts, I'm actually using yours the most to get this worked out since I know what you're talking about
August 11, 2013, 04:45:32 PM
Is it possible that the 2 blockchains (Spots and CopperBars) are getting mixed up on some people's computers?
It looks like the Spots blockchain is about the size that some people are seeing on CopperBars.
I suggest people delete the nodes from their config files if they haven't already. It seems to be working alright for me after I did that.
It looks like the Spots blockchain is about the size that some people are seeing on CopperBars.
I suggest people delete the nodes from their config files if they haven't already. It seems to be working alright for me after I did that.
I have not looked at the code. But interesting history: Spots is a copy of Nuggets code. But Spots has the "feature" of still using the same network as nuggets. That caused all types of confusion for a while.
It'd be sad if that was a problem again. I doubt it?
That's definitely not the issue here. The spots issue was simply shared ports
August 11, 2013, 04:42:17 PM
Is it possible that the 2 blockchains (Spots and CopperBars) are getting mixed up on some people's computers?
It looks like the Spots blockchain is about the size that some people are seeing on CopperBars.
I suggest people delete the nodes from their config files if they haven't already. It seems to be working alright for me after I did that.
It looks like the Spots blockchain is about the size that some people are seeing on CopperBars.
I suggest people delete the nodes from their config files if they haven't already. It seems to be working alright for me after I did that.
I have not looked at the code. But interesting history: Spots is a copy of Nuggets code. But Spots has the "feature" of still using the same network as nuggets. That caused all types of confusion for a while.
It'd be sad if that was a problem again. I doubt it?
Jump to: