victor101carranza
Member
Offline
Activity: 102
Merit: 10
|
|
July 17, 2013, 01:52:24 PM |
|
I have deleted peers.dat already it didn't work the rescan might help I just need instruction on how to do it on windows xp.
|
|
|
|
victor101carranza
Member
Offline
Activity: 102
Merit: 10
|
|
July 17, 2013, 02:47:51 PM |
|
Hi MobGod my address is MdLRCQTMV3c6N3mWJnG4ewkyYEtVFK3VtZ I'm looking for rescan info on google.
|
|
|
|
MobGod
|
|
July 17, 2013, 02:51:09 PM |
|
Hi MobGod my address is MdLRCQTMV3c6N3mWJnG4ewkyYEtVFK3VtZ I'm looking for rescan info on google.
Ok might not be right away but if I see anything that needs to come to you I will process your payments, but please try the rescan also
|
|
|
|
plekhanov
Newbie
Offline
Activity: 20
Merit: 0
|
|
July 17, 2013, 05:19:53 PM |
|
Can you rescan your wallet please
I re-scanned my client's wallet and did pick up some missed records. I've been mining since Wednesday morning, but haven't seen any coinworld.us payouts yet. MeKzQLrKbHt5DxvVCT47W5ZiaMJS5ZjyiU is the address I'm using to mine.
|
|
|
|
MobGod
|
|
July 17, 2013, 05:32:19 PM |
|
Can you rescan your wallet please
I re-scanned my client's wallet and did pick up some missed records. I've been mining since Wednesday morning, but haven't seen any coinworld.us payouts yet. MeKzQLrKbHt5DxvVCT47W5ZiaMJS5ZjyiU is the address I'm using to mine. Ok so you and vic only correct
|
|
|
|
plekhanov
Newbie
Offline
Activity: 20
Merit: 0
|
|
July 17, 2013, 05:42:20 PM |
|
Ok so you and vic only correct
We're the squeaky wheels. Thanks.
|
|
|
|
|
|
plekhanov
Newbie
Offline
Activity: 20
Merit: 0
|
|
July 17, 2013, 08:09:52 PM |
|
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?
|
|
|
|
MobGod
|
|
July 17, 2013, 10:22:32 PM |
|
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
|
|
|
|
plekhanov
Newbie
Offline
Activity: 20
Merit: 0
|
|
July 18, 2013, 01:01:35 AM |
|
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?
|
|
|
|
plekhanov
Newbie
Offline
Activity: 20
Merit: 0
|
|
July 18, 2013, 01:18:06 AM |
|
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.
|
|
|
|
DogtownHero
Member
Offline
Activity: 70
Merit: 10
j-coin//just 4 cpu's
|
|
July 18, 2013, 01:37:00 AM |
|
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 "C:\Program Files (x86)\nanotoken\nano-qt.exe" -server -checkblocks=0 -checklevel=4 -rescan
|
|
|
|
plekhanov
Newbie
Offline
Activity: 20
Merit: 0
|
|
July 18, 2013, 01:44:47 AM |
|
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.
|
|
|
|
MobGod
|
|
July 18, 2013, 02:13:25 AM |
|
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. no it's catching up on it's own was a peer issue the blocks where stuck on the pool but you can tell all payouts are working
|
|
|
|
plekhanov
Newbie
Offline
Activity: 20
Merit: 0
|
|
July 18, 2013, 06:11:37 AM |
|
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.
|
|
|
|
MobGod
|
|
July 18, 2013, 06:41:57 AM |
|
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
|
|
|
|
MobGod
|
|
July 18, 2013, 07:37:05 PM |
|
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
|
|
|
|
r3wt (OP)
|
|
July 18, 2013, 09:28:33 PM |
|
URGENT: ALL USERS MUST UPDATE CONF FILESadd 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. 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
|
My negative trust rating is reflective of a personal vendetta by someone on default trust.
|
|
|
MobGod
|
|
July 19, 2013, 12:40:33 AM |
|
Pool and explorer all set
|
|
|
|
|