Topic: [ANN] Copper Bars | Scrypt-Jane CPU | Accepted for Gold and Silver soon [CPR] - page 10. (Read 17251 times)
August 11, 2013, 04:06:11 PM
I can't sync up the block chain
August 11, 2013, 04:03:20 PM
@iGotSpots
In the spots thread you snapped back at a poster for saying the chain was under attack telling him not to comment if he didn't know what he is talking about. I can assure I do know what I am talking about.
With 16 second block time and 3 confirms, you have created the perfect storm for forking.
You have several long forks of legit miners all mining away.
There appears to be a large 40K chain, a 20K chain and growing 5K chain.
This coin won't be killed by an attacker, it's already been killed by design flaws.
Hate to tell you, this beast appears to be cooked.
Fix and restart.
~BCX~
In the spots thread you snapped back at a poster for saying the chain was under attack telling him not to comment if he didn't know what he is talking about. I can assure I do know what I am talking about.
With 16 second block time and 3 confirms, you have created the perfect storm for forking.
You have several long forks of legit miners all mining away.
There appears to be a large 40K chain, a 20K chain and growing 5K chain.
This coin won't be killed by an attacker, it's already been killed by design flaws.
Hate to tell you, this beast appears to be cooked.
Fix and restart.
~BCX~
A fork draws BCX like a flame does a moth
Seriously, though if there are indeed 3 chains, restarting with suitable parameters would be the right thing. Though, to be honest I am not really sure why you would get another coin to compete with Spots. If it being supposedly CPU friendly is the reason, do you then plan to release a ASIC friendly aka SHA256 coin? What about a SHA3 coin?
August 11, 2013, 03:55:22 PM
Hi,
just managed to compile GPU miner:
https://mega.co.nz/#!HgAR3aJC!dE3EiGNzE_ZmCM7IeALAshzgFS5dgDd0UM11Q2v1O4Q
tar -xjvf 1.bz2
CFLAGS="-march=native -O2 -pipe" ./configure --enable-scrypt
make
this is very dirty hack as I dont have programming skills - just my brain. It will produce executable file ybcminer but ignore the name - use it to mine CPRs
dont ask me to maintain it as I am not able to answer.
feeleep
BTW: working on pool for this coin but it seems to have the same problem as cosmoscoin and few others with submitblock function
just managed to compile GPU miner:
https://mega.co.nz/#!HgAR3aJC!dE3EiGNzE_ZmCM7IeALAshzgFS5dgDd0UM11Q2v1O4Q
tar -xjvf 1.bz2
CFLAGS="-march=native -O2 -pipe" ./configure --enable-scrypt
make
this is very dirty hack as I dont have programming skills - just my brain. It will produce executable file ybcminer but ignore the name - use it to mine CPRs
dont ask me to maintain it as I am not able to answer.
feeleep
BTW: working on pool for this coin but it seems to have the same problem as cosmoscoin and few others with submitblock function
August 11, 2013, 03:52:00 PM
15:51:51

{
"blocks" : 39147,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00147012,
"errors" : "",
"generate" : true,
"genproclimit" : 4,
"hashespersec" : 123885,
"pooledtx" : 0,
"testnet" : false
}
August 11, 2013, 03:48:20 PM
anyone using GPU on this?
August 11, 2013, 03:47:53 PM
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
Done. Now it's a 30k blockchain. Remove the addnodes from your conf, you shouldn't need them anyway, and let me know if it works
Edit: 40k. Lol
August 11, 2013, 03:45:28 PM
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
August 11, 2013, 03:43:23 PM
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
Remove the addnodes from your conf, you shouldn't need them anyway, and let me know if it works
August 11, 2013, 03:39:29 PM
seems to be jumping between two chains in sync, one has 20k+ block and the other 5k+ blocks
August 11, 2013, 03:38:19 PM
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
I just typed setgenerate true 4 (or however many cores you have, 4 in my case lol)
Yeah, I just realized why it did not work. It said it was done syncing and the I started to mine. However, it did not really sync because it discovered another 25k blocks and then started to sync those. Basically, every few minutes it discovers another few thousand blocks that have to sync. It is quite odd and at this rate, it should take roughly a few hours to sync. Is it supposed to take this long?
August 11, 2013, 03:32:58 PM
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
I just typed setgenerate true 4 (or however many cores you have, 4 in my case lol)
August 11, 2013, 03:27:20 PM
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
August 11, 2013, 03:26:26 PM
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
August 11, 2013, 03:22:59 PM
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
August 11, 2013, 03:20:59 PM
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?
August 11, 2013, 03:19:29 PM
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
August 11, 2013, 03:18:24 PM
So is the only way to mine this directly from the wallet client with CPU?
August 11, 2013, 03:13:09 PM
Reserved
August 11, 2013, 03:12:54 PM
CPR was released in the Spots thread and on Cryptsy last night for a few hours head start for the Spots community. I told you guys for almost a week that we were going to do it, so don't say it wasn't a fair start. Cryptsy chat also knew about it the second it was launched
August 11, 2013, 03:09:04 PM
IF YOU HAVE ANY ADDNODES IN YOUR CONF FILE, DELETE THEM IMMEDIATELY! IT MAY CAUSE YOU TO OWN FORK DUE TO A BAD NODE(S)
You shouldn't need them in there anyway. The way it's set up you should connect automatically to the right nodes
You shouldn't need them in there anyway. The way it's set up you should connect automatically to the right nodes
We are ready to announce the fourth currency that will be accepted for trade on iGotSpots.com
That currency is...Copper Bars! We designed this coin to be mined in conjunction with Spots and took the complete opposite approach when it came to parameters. Spots is a Scrypt coin made to be mined with GPU's, while Copper Bars are Scrypt-Jane and meant to be mined with CPU's. This will allow you to mine both coins concurrently and double your precious metals profits! Spots is a slow block time coin that rewards 49 Spots per block. Copper Bars will be fast blocks with small rewards. This will attract miners that like slow, big numbers, as well as the people that prefer fast, frequent payouts. Copper Bars will be used to purchase...imagine that, copper bars and coins on iGotSpots.com - We were going to take an already established currnecy, but since Spots launed so well and so smoothly, we decided to make our own that will be mined at the same time as Spots. It's the first package deal coin, so let's do this!
Copper Bars (CPR) - NO PREMINE - NO INSTAMINE - NO BULLSHIT
Scrypt-Jane
16 Second Blocks
.0064 Block Reward x 80 Billion Blocks for 512 Million total Coins
NO SUPERBLOCKS AT ALL
1% Stake with 365 Days of Coin Age Required, 730 days for full weight
RPC Port = 7873
P2P Port = 7874
Scrypt-Jane
16 Second Blocks
.0064 Block Reward x 80 Billion Blocks for 512 Million total Coins
NO SUPERBLOCKS AT ALL
1% Stake with 365 Days of Coin Age Required, 730 days for full weight
RPC Port = 7873
P2P Port = 7874
Mining Pools
http://cpr.coinmine.pl:7060
Still looking for a P2Pool
Clients
Windows: https://docs.google.com/file/d/0B49exKIsGBn5dDdleDVjbnBXQlE/edit?usp=sharing
Source: https://docs.google.com/file/d/0B49exKIsGBn5N3R5RElvUXUzTmc/edit?usp=sharing
Github: https://github.com/copperbars/copperbars
IF YOU HAVE ANY ADDNODES IN YOUR CONF FILE, DELETE THEM IMMEDIATELY! IT MAY CAUSE YOU TO OWN FORK DUE TO A BAD NODE(S)
You shouldn't need them in there anyway. The way it's set up you should connect automatically to the right nodes
You shouldn't need them in there anyway. The way it's set up you should connect automatically to the right nodes
Jump to: