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.
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 |
|
|
|
|
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
|
|
|
|
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... |
|
|
|
@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~
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... |
|
|
|
You're also good. Let's see some posts or pics of the forked chains? Everyone has been synced up so far |
|
|
|
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 |
|
|
|
|
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)
|
|
|
|
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.
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 |
|
|
|
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.
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 |
|
|
|
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.
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 |
|
|
|
Hm, well, that's weird. I have a balance of 2 blocks and 2 blocks immature, but only 2 transactions listed (and 20 orphans).
Edit: as for forking, it's constantly switching between them. There's a 3300 fork, a 40,000 fork, and a 20,000 fork that I've seen (under Debug > Estimated total blocks)
I think one of the nodes must be bad. I'm watching the same info on multiple rigs and I haven't jumped off the 40k chain at all on any of them You guys still seeing that even if you remove all the nodes from conf file? |
|
|
|
|
Yes I know we were pushing the envelope with the low block times. But personally I'm not getting any forking on any of the machines I have so far and I've got 5 separate rigs on it
|
|
|
|
|
I've got 5 rigs that I just restarted and they're all on the 40k block chain...try deleting the two blk files in your appdata folder and let me know if you still find yourself on a different fork
|
|
|
|
|
15:51:51

{
"blocks" : 39147,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00147012,
"errors" : "",
"generate" : true,
"genproclimit" : 4,
"hashespersec" : 123885,
"pooledtx" : 0,
"testnet" : false
}
|
|
|
|
XPM should have been the proof positive that any CPU only coin will fall victim to botnetters as soon as there is any profit to be made.
This one will be no different.
~BCX~
Yes, but I assume some people will be using GPUs very soon anyway |
|
|
|
|
No idea why you guys aer getting that. I just reloaded and didn't have the problem. Maybe a bad node
Remove the addnodes from your conf, you shouldn't need them anyway, and let me know if it works
|
|
|
|
So is the only way to mine this directly from the wallet client with CPU?
That's how I'm doing it. I'm sure you can find something else if you really look, but I don't have much experience with mining Scrypt-Janes, so I've been using the wallet to mine it, just to make sure it's running smoothly Ok. As soon as you find an alternative method, can you please post it here? Yea, for sure. Although I kinda hope nobody makes a GPU miner, though, so you guys can mine these and Spots at the same time like we had designed them to be Also, I have another question. I just downloaded the wallet onto one of my computers and it just finished syncing. When I opened the debug console and typed setgenerate true -1, nothing happened and my CPU usage is still at 5% or so. What happened? How do we mine this from the client? Thanks Just type setgenerate true |
|
|
|
So is the only way to mine this directly from the wallet client with CPU?
That's how I'm doing it. I'm sure you can find something else if you really look, but I don't have much experience with mining Scrypt-Janes, so I've been using the wallet to mine it, just to make sure it's running smoothly Ok. As soon as you find an alternative method, can you please post it here? Yea, for sure. Although I kinda hope nobody makes a GPU miner, though, so you guys can mine these and Spots at the same time like we had designed them to be |
|
|
|
So is the only way to mine this directly from the wallet client with CPU?
That's how I'm doing it. I'm sure you can find something else if you really look, but I don't have much experience with mining Scrypt-Janes, so I've been using the wallet to mine it, just to make sure it's running smoothly |
|
|
|
|
Show Posts
