Lol, r3wt was sayin earlier in Cryptsy that you already killed it. "NAN dead from BitcoinExpress 51% attack" lol
More like a loving ass whooping. ~BCX~ It's ok, he's in a I hate everyone mood today |
|
|
|
AnalysisStrengths- popular
- potentially gpu resistant
- dedicated dev
- can be traded for real world commodity(Copper)
- Scrypt Jane works great with Retarget.
Weaknesses- Block Times to short
- No seednode, encourages forking
- poor launch
SolutionRelaunch with Seednode, er go making conf file useless for the purpose of finding nodes. build with upnp(like j-coin) to decrease network latency and time spent finding peers. this should limit forking. increase block times to atleast 20 seconds, with 30 seconds being preferrable. if these steps are taken, coin should have no more issues of forking(and therefore decrease or atleast minimize chainbloat due to orphans) Unpnp is enabled that's why we don't need nodes |
|
|
|
try getblock 00000042565f9bfd1bc89702d28c8b94c5b97674c1547c7f54233e447ae445ab
That should be 55684 on the official chain. {
"hash" : "00000042565f9bfd1bc89702d28c8b94c5b97674c1547c7f54233e447ae445ab",
"confirmations" : 29,
"size" : 266,
"height" : 55684,
"version" : 3,
"merkleroot" : "a43f8be1f7ba8998af2e7a7d068bb82bf0b5cbccbeecdc964cae10f3db682b76",
"mint" : 0.00640000,
"time" : 1376289651,
"nonce" : 2296264,
"bits" : "1e0139bb",
"difficulty" : 0.00318740,
"previousblockhash" : "000000925ac491075b034d79d4fd72c27df243126527c1ee423dae23f36ebc32",
"nextblockhash" : "0000000015fd4660c96cfe75be964ff0f8f70d960971486551ec8d421f77b4a6",
"flags" : "proof-of-work",
"proofhash" : "00000042565f9bfd1bc89702d28c8b94c5b97674c1547c7f54233e447ae445ab",
"entropybit" : 1,
"modifier" : "9af3b58e01855bc5",
"modifierchecksum" : "54b0ac78",
"tx" : [
"a43f8be1f7ba8998af2e7a7d068bb82bf0b5cbccbeecdc964cae10f3db682b76"
],
"signature" : "30460221008e6c493e7e543aa26709752a6a61a6502e8ea36a04d9a6df44f1b18cd6ab6344022100ca6b91fd413ed9723df2c7202137a0c273c8a43da54f8eb6380ce957b687814f"
}
Can try and find differences at least. Linux test has gotten past most of the orphans I think, hit 43000 01:51:04  getblock 00000042565f9bfd1bc89702d28c8b94c5b97674c1547c7f54233e447ae445ab 01:51:04  { "hash" : "00000042565f9bfd1bc89702d28c8b94c5b97674c1547c7f54233e447ae445ab", "confirmations" : 215, "size" : 266, "height" : 55684, "version" : 3, "merkleroot" : "a43f8be1f7ba8998af2e7a7d068bb82bf0b5cbccbeecdc964cae10f3db682b76", "mint" : 0.00640000, "time" : 1376289651, "nonce" : 2296264, "bits" : "1e0139bb", "difficulty" : 0.00318740, "previousblockhash" : "000000925ac491075b034d79d4fd72c27df243126527c1ee423dae23f36ebc32", "nextblockhash" : "0000000015fd4660c96cfe75be964ff0f8f70d960971486551ec8d421f77b4a6", "flags" : "proof-of-work", "proofhash" : "00000042565f9bfd1bc89702d28c8b94c5b97674c1547c7f54233e447ae445ab", "entropybit" : 1, "modifier" : "9af3b58e01855bc5", "modifierchecksum" : "54b0ac78", "tx" : [ "a43f8be1f7ba8998af2e7a7d068bb82bf0b5cbccbeecdc964cae10f3db682b76" ], "signature" : "30460221008e6c493e7e543aa26709752a6a61a6502e8ea36a04d9a6df44f1b18cd6ab634402210 0ca6b91fd413ed9723df2c7202137a0c273c8a43da54f8eb6380ce957b687814f" } Yep |
|
|
|
But everyone is hopping over to the correct chain. That's why the coins are disappearing. That should be done now
I'll hang with you, I lost 3.25 Copperbars or 509 blocks and generated right at 10500 orphans. While I'm mining this you're actually buying NAN some extra life  ~BCX~ Lol, r3wt was sayin earlier in Cryptsy that you already killed it. "NAN dead from BitcoinExpress 51% attack" lol 01:49:19  getmininginfo 01:49:19  { "blocks" : 55863, "currentblocksize" : 1000, "currentblocktx" : 0, "difficulty" : 0.00321462, "errors" : "", "generate" : true, "genproclimit" : 4, "hashespersec" : 84111, "pooledtx" : 0, "testnet" : false } That's the chain you're on, yes? |
|
|
|
Orphans were expected. That's not the issue. I'm going to keep it running for a little while longer and see what happens. I really think it will sort itself out. I'm not seeing any forks at all on the 5 nodes I've had running since minute 1
Sheer number of them seems to be messing with syncing. The linux node I launched has been sitting at around 10034 blocks with thousands upon thousands of orphans being processed ( im guessing these are the other forks getting trashed). Been there for several minutes now. Once it does get synced (assuming you dont restart) it seems to be okay. It may correct itself in time, will have to see. Forks are bad though =/ The only forks were from bad nodes. We got rid of them this morning. You guys...it really is going fine. I understand some of you lost coins and you're pissed. If I had any to give you to replace them I would. Just take a few days off if you're that mad, and check back to see that we have fixed everything It is sorting itself out. Be patient. I'm not going to bail and leave you guys with wasted days. Look how I've been handling Spots. I've been fair and taken care of you guys. Just bear with me. Let the difficulty rise when we get more miners and things will be just fine. I actually had non-orphaned copperbars that I mined before the forking started, but when I attempted to resync it failed at block 3705 and corrupted my wallet with ~0.6 copperbars. Now, I'm worried about trying to resync my other machines. I don't want to lose my other ~2.4 copperbars. How many ounces of copper were going to be in each copperbar? Copper is by the pound that's why we have super low rewards. Just rename it to wallet2.DAT before you do it I'll try renaming the wallet and resyncing. So, how many pounds of copper was 1 copperbar going to be worth? Hoping it will be traded before we accept it, but if it's not on an exchange 7 days from now, I would probably do about 1 Bar per Pound, just to make good on my promise to accept it within a week. That's obviously a total hypothetical price, but the goal was to have it somewhere around there |
|
|
|
Orphans were expected. That's not the issue. I'm going to keep it running for a little while longer and see what happens. I really think it will sort itself out. I'm not seeing any forks at all on the 5 nodes I've had running since minute 1
Sheer number of them seems to be messing with syncing. The linux node I launched has been sitting at around 10034 blocks with thousands upon thousands of orphans being processed ( im guessing these are the other forks getting trashed). Been there for several minutes now. Once it does get synced (assuming you dont restart) it seems to be okay. It may correct itself in time, will have to see. Forks are bad though =/ The only forks were from bad nodes. We got rid of them this morning. You guys...it really is going fine. I understand some of you lost coins and you're pissed. If I had any to give you to replace them I would. Just take a few days off if you're that mad, and check back to see that we have fixed everything It is sorting itself out. Be patient. I'm not going to bail and leave you guys with wasted days. Look how I've been handling Spots. I've been fair and taken care of you guys. Just bear with me. Let the difficulty rise when we get more miners and things will be just fine. I actually had non-orphaned copperbars that I mined before the forking started, but when I attempted to resync it failed at block 3705 and corrupted my wallet with ~0.6 copperbars. Now, I'm worried about trying to resync my other machines. I don't want to lose my other ~2.4 copperbars. How many ounces of copper were going to be in each copperbar? Copper is by the pound that's why we have super low rewards. Just rename it to wallet2.DAT before you do it |
|
|
|
The only forks were from bad nodes. We got rid of them this morning.
You guys...it really is going fine. I understand some of you lost coins and you're pissed. If I had any to give you to replace them I would. Just take a few days off if you're that mad, and check back to see that we have fixed everything
It is sorting itself out. Be patient. I'm not going to bail and leave you guys with wasted days. Look how I've been handling Spots. I've been fair and taken care of you guys. Just bear with me. Let the difficulty rise when we get more miners and things will be just fine.
Those chains didn't re-merge, miners kept adding onto them and now you have two running neck and neck, with each right around 53K blocks as best as I can tell. ~BCX~ But everyone is hopping over to the correct chain. That's why the coins are disappearing. That should be done now |
|
|
|
The only forks were from bad nodes. We got rid of them this morning.
You guys...it really is going fine. I understand some of you lost coins and you're pissed. If I had any to give you to replace them I would. Just take a few days off if you're that mad, and check back to see that we have fixed everything
It is sorting itself out. Be patient. I'm not going to bail and leave you guys with wasted days. Look how I've been handling Spots. I've been fair and taken care of you guys. Just bear with me. Let the difficulty rise when we get more miners and things will be just fine.
Actually I haven't lost anything yet ( I have always been on the correct chain, even with the bad nodes in the config). Just going by what others have mentioned (still seems to be forking). That is why I am bringing up a new client to check. Just not a fan of needing 2-3 hours to sync a chain. You could have just moved the chain files. I know you are checking for it to sync but in the future you can do that |
|
|
|
|
We are getting so many orphans because the hash rate is still too low. It was designed to support higher hash rates more efficiently. I was expecting more initial network power. Just chill. I promise it will work out
|
|
|
|
After you compile in linux what command line are you guys using to run ybcminer, I can't seem to get it to run.
I get "unrecognized option"
ybcminer --scrypt
and ybcminer --scrypt-jane
You have to enable scrypt when you run ./configure (see the build.txt files for a list) Edit: That being said, I am not sure having more GPU miners on is a good idea ... It would raise the difficulty enough to get rid of the orphans |
|
|
|
Orphans were expected. That's not the issue. I'm going to keep it running for a little while longer and see what happens. I really think it will sort itself out. I'm not seeing any forks at all on the 5 nodes I've had running since minute 1
Sheer number of them seems to be messing with syncing. The linux node I launched has been sitting at around 10034 blocks with thousands upon thousands of orphans being processed ( im guessing these are the other forks getting trashed). Been there for several minutes now. Once it does get synced (assuming you dont restart) it seems to be okay. It may correct itself in time, will have to see. Forks are bad though =/ The only forks were from bad nodes. We got rid of them this morning. You guys...it really is going fine. I understand some of you lost coins and you're pissed. If I had any to give you to replace them I would. Just take a few days off if you're that mad, and check back to see that we have fixed everything It is sorting itself out. Be patient. I'm not going to bail and leave you guys with wasted days. Look how I've been handling Spots. I've been fair and taken care of you guys. Just bear with me. Let the difficulty rise when we get more miners and things will be just fine. |
|
|
|
Orphans were expected. That's not the issue. I'm going to keep it running for a little while longer and see what happens. I really think it will sort itself out. I'm not seeing any forks at all on the 5 nodes I've had running since minute 1
Remember the nodes you bolded to remove? Those were nodes on different chains. ~BCX~ Yea, I fucked up on the nodes. They are gone and everyone should have removed them by now That shouldn't be a coin killer though |
|
|
|
|
Give me a few more days to see if I can get it smooth. If it does fail, the ones that stick around I'll reward in some Spots for your wasted time. I wouldn't keep going if I didn't think it would work
"blocks" : 55347,
I haven't had any fork or network issues personally, so I really can't justify quitting on it so easily
|
|
|
|
Maybe I should've just stayed out of scrypt-jane...but it fits so well with what my plan was to have Spots and Bars mined at the same time
scrypt chacha i'snt the problem, too fast of blocks with a low diff is. Not that I want to see it restarted (I have quite a lot mined), but a coin does need to be sustainable. Just launched a new linux client to see if I can get the same problem. First 10k seem fine (no crashes yet etc), biggest issue is there are a ridiculous amount of orphans on the chain (page after page of them in the log) Orphans were expected. That's not the issue. I'm going to keep it running for a little while longer and see what happens. I really think it will sort itself out. I'm not seeing any forks at all on the 5 nodes I've had running since minute 1 |
|
|
|
|
Maybe I should've just stayed out of scrypt-jane...but it fits so well with what my plan was to have Spots and Bars mined at the same time.
At this point, if we re-start the coin, it's going to lose all respect and will be completely worthless after the re-launch
|
|
|
|
|
I really wish I would get any of the errors you guys are running in to.
Also, I never said this was a test. I said the plan was to accept it on iGotSpots.com in 7 days
I'm having a real hard time justifying killing this project without getting any errors myself...I believe you guys, but I think once everything is sorted out and diff rises, everything will be running fine, just like it had been for me this whole time
|
|
|
|
Can we get a windows GPU build  I'm also interested in this. I'd be willing to throw a little bit down on a bounty for it too in either BTC or Spots. I don't have shit for CPR yet, or I'd offer those too |
|
|
|
|
You guys really need to make sure you delete all the addnodes from your conf or you're going to keep losing coins...
|
|
|
|
Block chain is almost 250 MB. If it keeps going at this rate it'll be 5.25 GB a week.  and the facepalm continues Its ok to be jealous but if you could take it elsewhere that would be awesome jealous? j-coin > copperbars (PERIOD) Right. So anyway |
|
|
|
|
Show Posts
