Your not, blocks go so fast...61280, right now
Iam far ahead of you already at "blocks" : 61158,
Hes on the wrong chain :d
Topic: [NUT] NutCoin - The Anti Scarcity Stabilized Currency - page 9. (Read 32740 times)
Hes on the wrong chain :d
Your not, blocks go so fast...61280, right now
Iam far ahead of you already at "blocks" : 61158,
{
"blocks" : 60615,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00373042,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 1432690,
"pooledtx" : 0,
"testnet" : false
}
{
"version" : 80601,
"protocolversion" : 70003,
"walletversion" : 60000,
"balance" : 9375000.00000000,
"blocks" : 60618,
"timeoffset" : -2,
"connections" : 10,
"proxy" : "",
"difficulty" : 0.00373042,
"testnet" : false,
"keypoololdest" : 1388742744,
"keypoolsize" : 0,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : ""
}
For me seems to be working fine since the start. I would say not to restart.
Btw, I'm getting 10000 transactions. Do you guys know why?
Note: People need to be very careful in the start to not add seeds like crazy to the config file, it will help with the forks. I was only using the two first seeds from start and worked ok. A few orphans at first because it's common with a low diff coin.
"blocks" : 60615,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00373042,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 1432690,
"pooledtx" : 0,
"testnet" : false
}
{
"version" : 80601,
"protocolversion" : 70003,
"walletversion" : 60000,
"balance" : 9375000.00000000,
"blocks" : 60618,
"timeoffset" : -2,
"connections" : 10,
"proxy" : "",
"difficulty" : 0.00373042,
"testnet" : false,
"keypoololdest" : 1388742744,
"keypoolsize" : 0,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : ""
}
For me seems to be working fine since the start. I would say not to restart.
Btw, I'm getting 10000 transactions. Do you guys know why?
Note: People need to be very careful in the start to not add seeds like crazy to the config file, it will help with the forks. I was only using the two first seeds from start and worked ok. A few orphans at first because it's common with a low diff coin.
Iam far ahead of you already at "blocks" : 61158,
{
"blocks" : 60615,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00373042,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 1432690,
"pooledtx" : 0,
"testnet" : false
}
{
"version" : 80601,
"protocolversion" : 70003,
"walletversion" : 60000,
"balance" : 9375000.00000000,
"blocks" : 60618,
"timeoffset" : -2,
"connections" : 10,
"proxy" : "",
"difficulty" : 0.00373042,
"testnet" : false,
"keypoololdest" : 1388742744,
"keypoolsize" : 0,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : ""
}
For me seems to be working fine since the start. I would say not to restart.
Btw, I'm getting 10000 transactions. Do you guys know why?
Note: People need to be very careful in the start to not add seeds like crazy to the config file, it will help with the forks. I was only using the two first seeds from start and worked ok. A few orphans at first because it's common with a low diff coin.
"blocks" : 60615,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00373042,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 1432690,
"pooledtx" : 0,
"testnet" : false
}
{
"version" : 80601,
"protocolversion" : 70003,
"walletversion" : 60000,
"balance" : 9375000.00000000,
"blocks" : 60618,
"timeoffset" : -2,
"connections" : 10,
"proxy" : "",
"difficulty" : 0.00373042,
"testnet" : false,
"keypoololdest" : 1388742744,
"keypoolsize" : 0,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : ""
}
For me seems to be working fine since the start. I would say not to restart.
Btw, I'm getting 10000 transactions. Do you guys know why?
Note: People need to be very careful in the start to not add seeds like crazy to the config file, it will help with the forks. I was only using the two first seeds from start and worked ok. A few orphans at first because it's common with a low diff coin.
Im also getting no orphans, but I only get 5k per block and some had a screenshot here showing 10k per block.....
{
"version" : 80601,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : xxx.00000000,
"blocks" : 60875,
"timeoffset" : -3,
"connections" : 13,
"proxy" : "",
"difficulty" : 0.00373042,
"testnet" : false,
"keypoololdest" : 1388741193,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}
got also 70002
Iam getting no orphans so :d
"version" : 80601,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : xxx.00000000,
"blocks" : 60875,
"timeoffset" : -3,
"connections" : 13,
"proxy" : "",
"difficulty" : 0.00373042,
"testnet" : false,
"keypoololdest" : 1388741193,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}
got also 70002
Iam getting no orphans so :d
{
"blocks" : 60451,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00373042,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 6123156,
"pooledtx" : 0,
"testnet" : false
}
"blocks" : 60451,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00373042,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 6123156,
"pooledtx" : 0,
"testnet" : false
}
yep.. and btw I get WAY less orphans than before.
{
"blocks" : 60451,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00373042,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 6123156,
"pooledtx" : 0,
"testnet" : false
}
"blocks" : 60451,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00373042,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 6123156,
"pooledtx" : 0,
"testnet" : false
}
Busted tha nut! 
I'm on block 60352. still mining.
Busted tha nut!
that's the nutest currency i've never seen.
I got 2.8 M NUTs at block 52963 and when I stop mining, the block count stopped 
So be sure you are not alone on your own fork ...
Then I checked my 'getinfo' and I realized I was on protocol version 70002 instead of 70003 although I updated the client a few hours ago
After the client updated I am back to 500k NUTs
So I virtually lost 'NUTs' but at least I am happy to learn a lot
restart procedure is described by OP in post #301:
1) close nutcoind and/or the wallet
2) be sure it is not remaining in activity monitor (force close it if needed)
3) edit nutcoin.conf, and be sure there is ONLY this node (protocol 70003) :
addnode=192.99.4.55:9508
4) remove peers.dat
5) git pull an recompile the daemon with the last version (protocol 70003)
6) restart nutcoind or wallet
This will shutdown and burst every peers connected with the old version 70002, forcing them to download the new version.
So be sure you are not alone on your own fork ...
Then I checked my 'getinfo' and I realized I was on protocol version 70002 instead of 70003 although I updated the client a few hours ago
After the client updated I am back to 500k NUTs
So I virtually lost 'NUTs' but at least I am happy to learn a lot
restart procedure is described by OP in post #301:
1) close nutcoind and/or the wallet
2) be sure it is not remaining in activity monitor (force close it if needed)
3) edit nutcoin.conf, and be sure there is ONLY this node (protocol 70003) :
addnode=192.99.4.55:9508
4) remove peers.dat
5) git pull an recompile the daemon with the last version (protocol 70003)
6) restart nutcoind or wallet
This will shutdown and burst every peers connected with the old version 70002, forcing them to download the new version.
Give it up mate. Its dead. Tried the procedure and still at 27K blocks.
Mine never actually finishes syncing. It's at like 29k blocks but it says 0 hours left and out of 54k blocks.
The node is dead... I cannot run nutcoind.
I got 2.8 M NUTs at block 52963 and when I stop mining, the block count stopped
So be sure you are not alone on your own fork ...
Then I checked my 'getinfo' and I realized I was on protocol version 70002 instead of 70003 although I updated the client a few hours ago
After the client updated I am back to 500k NUTs
So I virtually lost 'NUTs' but at least I am happy to learn a lot
restart procedure is described by OP in post #301:
1) close nutcoind and/or the wallet
2) be sure it is not remaining in activity monitor (force close it if needed)
3) edit nutcoin.conf, and be sure there is ONLY this node (protocol 70003) :
addnode=192.99.4.55:9508
4) remove peers.dat
5) git pull an recompile the daemon with the last version (protocol 70003)
6) restart nutcoind or wallet
This will shutdown and burst every peers connected with the old version 70002, forcing them to download the new version.
So be sure you are not alone on your own fork ...
Then I checked my 'getinfo' and I realized I was on protocol version 70002 instead of 70003 although I updated the client a few hours ago
After the client updated I am back to 500k NUTs
So I virtually lost 'NUTs' but at least I am happy to learn a lot
restart procedure is described by OP in post #301:
1) close nutcoind and/or the wallet
2) be sure it is not remaining in activity monitor (force close it if needed)
3) edit nutcoin.conf, and be sure there is ONLY this node (protocol 70003) :
addnode=192.99.4.55:9508
4) remove peers.dat
5) git pull an recompile the daemon with the last version (protocol 70003)
6) restart nutcoind or wallet
This will shutdown and burst every peers connected with the old version 70002, forcing them to download the new version.
Give it up mate. Its dead. Tried the procedure and still at 27K blocks.
setgenerate false
you dont need to mine this. It going to be either dead or reset tomorrow.
you dont need to mine this. It going to be either dead or reset tomorrow.
this is correct ?

getmininginfo

{
"blocks" : 28402,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00024414,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 4867,
"networkhashps" : 202626,
"pooledtx" : 0,
"testnet" : false
}

getmininginfo

{
"blocks" : 28402,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00024414,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 4867,
"networkhashps" : 202626,
"pooledtx" : 0,
"testnet" : false
}
I got 2.8 M NUTs at block 52963 and when I stop mining, the block count stopped
So be sure you are not alone on your own fork ...
Then I checked my 'getinfo' and I realized I was on protocol version 70002 instead of 70003 although I updated the client a few hours ago
After the client updated I am back to 500k NUTs
So I virtually lost 'NUTs' but at least I am happy to learn a lot
restart procedure is described by OP in post #301:
1) close nutcoind and/or the wallet
2) be sure it is not remaining in activity monitor (force close it if needed)
3) edit nutcoin.conf, and be sure there is ONLY this node (protocol 70003) :
addnode=192.99.4.55:9508
4) remove peers.dat
5) git pull an recompile the daemon with the last version (protocol 70003)
6) restart nutcoind or wallet
This will shutdown and burst every peers connected with the old version 70002, forcing them to download the new version.
So be sure you are not alone on your own fork ...
Then I checked my 'getinfo' and I realized I was on protocol version 70002 instead of 70003 although I updated the client a few hours ago
After the client updated I am back to 500k NUTs
So I virtually lost 'NUTs' but at least I am happy to learn a lot
restart procedure is described by OP in post #301:
1) close nutcoind and/or the wallet
2) be sure it is not remaining in activity monitor (force close it if needed)
3) edit nutcoin.conf, and be sure there is ONLY this node (protocol 70003) :
addnode=192.99.4.55:9508
4) remove peers.dat
5) git pull an recompile the daemon with the last version (protocol 70003)
6) restart nutcoind or wallet
This will shutdown and burst every peers connected with the old version 70002, forcing them to download the new version.
how to restart ?
We need a reset and one with a hard coded super seed.
I've got 2.4 mil but I definately did suggest this earlier. I know it sucks but technucally the whole coin was premined, lol. It was supposed to be launched until today. Great Demo guys, but if you want a shot at this. At minimum reset the block. I would also select a Windows QT client that was already pre-compiled and post a official conf with no more than 5 connect hosts. But hosts that you know are true.
Jump to: