Not sure where everyone went come back
I dropped off when the reject rate hit about 45% for me. I'll take another look in a few minutes.
Topic: NanoTokens Information thread MOVED - page 7. (Read 38111 times)
I dropped off when the reject rate hit about 45% for me. I'll take another look in a few minutes.
NAN all the way 
Yea this one the hash rate peaked at 80mh now it's 80kh...
Yea this one the hash rate peaked at 80mh now it's 80kh...
Just in case you guys need the link again
http://coinworld.us:8884/static/
http://coinworld.us:8884/static/
The hell happened to the pool hash rate?
What pool ?
The hell happened to the pool hash rate?
Pool and explorer all set
URGENT: ALL USERS MUST UPDATE CONF FILES
add the line that says noirc=0. the network has came under a spam attack via irc. to protect against a fork, all users should add this line to their conf file. this one little line negates such an attack, as peers not in the addnode will not be able to be found, thus preventing malicious peers or "cancer nodes" from bogging down the network, or even worse, forking the chain.
add the line that says noirc=0. the network has came under a spam attack via irc. to protect against a fork, all users should add this line to their conf file. this one little line negates such an attack, as peers not in the addnode will not be able to be found, thus preventing malicious peers or "cancer nodes" from bogging down the network, or even worse, forking the chain.
Code:
noirc=0
rpcuser=Username
rpcpassword=Strong Password
rpcallowip=127.0.0.1
rpcport=7578
port=17578
daemon=1
server=1
gen=0
addnode=60.230.201.155
addnode=71.187.248.95
addnode=173.216.107.124
addnode=166.78.161.148
addnode=121.215.159.167
addnode=84.226.81.187
addnode=62.163.9.155
addnode=85.237.212.205
ok going to make a support system because i can't check every post for things i'm running, I've tried to make a thread but no-one looks at it, I will keep you guys posted but pool is fine and explorer is online
doing a final pull of the DB thats why it's down right now trying to get this working with np's at all should be ok by tomorrow
This has been educational.
I ran a re-scan. The scan found 518 blocks missing from my client's wallet. The re-scan didn't add the blocks to the wallet, which is normal if the blocks aren't for an address found in the wallet. However....
I backed up the wallet and created a new one, then imported the private keys from the older wallet into the new one. I also downloaded the blockchain from scratch. After that I did another re-scan. That scan found "only" 167 blocks missing from the wallet just created. The blockchain explorer is returning a 500 error at the moment, so looking up a few of them will be a chore for another day. Here are a few of them from the end of the list found by the scan:
AddToWallet a7f2f06bb5
AddToWallet ce3fae5d6d
AddToWallet 5c6facb254
Here's a few from the beginning of the list:
AddToWallet 09230627f5
AddToWallet ac1c549ea2
AddToWallet 028c82e01b
I have some (a smaller number) of missing blocks from the Qt wallets of other coin clients based on bitcoin-qt, so this does not look like anything specific to the Nanotoken Qt or CLI clients.
I ran this earlier and saw some entries for today (2013.07.17). I re-visited that link a minute ago. The last payout is from three days ago. Somebody (something) changed their (its) mind.
I ran this earlier and saw some entries for today (2013.07.17). I re-visited that link a minute ago. The last payout is from three days ago. Somebody (something) changed their (its) mind.
Crap not sure on Windows
I don't have access to XP, but I modified the menu entry in the Windows program list of a Windows 7 client to include these options:
-rescan -checkblocks=0 -checklevel=4
The last two options don't take long to run against the Nanotoken blockchain at the size that it is now. They would take much time when it grows to the size of bitcoin's. If you trust the nodes in your peer list, you can leave them out.
In the Windows programs list, I select and right click on the Nanotoken client. I go to the Shortcut tab, then edit the Target option so that it looks like this:
"C:\Program Files (x86)\nanotoken\nano-qt.exe" -server -checkblocks=0 -checklevel=4 -conf="$PATHNAME\nanotoken.conf" -rescan
$PATHNAME in my example is the full Windows directory path to where I store the configuration file. I quote it because part of the path contains spaces. I needed the -server option to accept connections from solo mining clients.
or you could open run and type
Code:
"C:\Program Files (x86)\nanotoken\nano-qt.exe" -server -checkblocks=0 -checklevel=4 -rescan
Crap not sure on Windows
I don't have access to XP, but I modified the menu entry in the Windows program list of a Windows 7 client to include these options:
-rescan -checkblocks=0 -checklevel=4
The last two options don't take long to run against the Nanotoken blockchain at the size that it is now. They would take much time when it grows to the size of bitcoin's. If you trust the nodes in your peer list, you can leave them out.
In the Windows programs list, I select and right click on the Nanotoken client. I go to the Shortcut tab, then edit the Target option so that it looks like this:
"C:\Program Files (x86)\nanotoken\nano-qt.exe" -server -checkblocks=0 -checklevel=4 -conf="$PATHNAME\nanotoken.conf" -rescan
$PATHNAME in my example is the full Windows directory path to where I store the configuration file. I quote it because part of the path contains spaces. I needed the -server option to accept connections from solo mining clients.
from my understanding you need fresh nodes because the block was getting messed with so if you have wrong nodes to say it's not going to work right
I agree. When I've run the client behind a lot of network security with IRC disabled (because leaving it on gets the client quarantined for bot-like behavior by the loal PC's security), no blocks can be pulled down. Does turning "dnsseeds" on, or "noirc" off, help?
ok now for the next one to be done can anyone tell me why this will not download blocks ?
What does "nanotokend getpeerinfo" show you/them?
from my understanding you need fresh nodes because the block was getting messed with so if you have wrong nodes to say it's not going to work right
Jump to: