- Apr 8, 2014
- 1,946
- 1,306
- 1,283
No you will not lose them.How do I reindex? Will I loose my coins if I do?
No you will not lose them.How do I reindex? Will I loose my coins if I do?
Darkcoin server stopping
[email protected]:~$ ./darkcoind -rescan
Darkcoin server starting
[email protected]:~$ ./darkcoind getinfo
{
"version" : 110007,
"protocolversion" : 70052,
"walletversion" : 60001,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 204572,
"timeoffset" : 0,
"connections" : 8,
"proxy" : "",
"difficulty" : 4083.62714253,
"testnet" : false,
"keypoololdest" : 1415488991,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."
Rescan does not work, stuck on 204572 block after 11.0.6 -> 11.0.7 change. (peers.dat deleted)
> darkcoind --help
...
-reindex Rebuild block chain index from current blk000??.dat files on startup
...
-rescan Rescan the block chain for missing wallet transactions on startup
...
could that be programmed in?small note for everyone who is confused by rescan/reindex options
when wallet stuck you need to rebuild blockchain -> -reindexCode:> darkcoind --help ... -reindex Rebuild block chain index from current blk000??.dat files on startup ... -rescan Rescan the block chain for missing wallet transactions on startup ...
Not sure if it's a good idea to auto-reindex but until then I guess you can use a bash script and thiscould that be programmed in?
-alertnotify=<cmd> Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message)
I'd really like to get my node back online.........I can't get v11 to work with p2pool - so I can't upgrade......Ever since I upgraded to the latest version I've been unable to get p2pool to connect on port 9999:
2015-01-16 16:38:13.821624 p2pool (version 81fc6c5-dirty)
2015-01-16 16:38:13.821724
2015-01-16 16:38:13.821780 Testing bitcoind RPC connection to 'REMOVED' with username 'IYFTechDRK'...
2015-01-16 16:38:13.850612 ...success!
2015-01-16 16:38:13.850710 Current block hash: 5f2afca31990cbc9c8be1722088daafeac266253c55a1e7f06a47
2015-01-16 16:38:13.850753 Current block height: 204176
2015-01-16 16:38:13.850777
2015-01-16 16:38:13.850815 Testing bitcoind P2P connection to '127.0.0.1:9999'...
2015-01-16 16:38:18.851266 ...taking a while. Common reasons for this include all of bitcoind's connection slots being used...
If I revert to v10 I have no problem..........it just won't connect on 9999
Looks like ourlink have p2pool running on 11.00.07Anyone?
I'd really like to get my node back online.........
Mac OS wallet is on download page...We still do NOT have a MAC Wallet
+ I have no idea how to reindex
(my incoming transfer is still stuck on the same block ?!?!)
Erase Blockchain and peer and start again ?!
--reindex does NOT tell me anything.
Can I please get a Idiot Translation !
Tx
/Applications/Darkcoin-Qt.app/Contents/MacOS/Darkcoin-Qt -reindex
great !Mac OS wallet is on download page...
https://www.darkcoin.io/downloads/
https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.11.0.7-osx.dmg
Or am I missing smth?
To reindex on Mac OS open Terminal and run
Code:/Applications/Darkcoin-Qt.app/Contents/MacOS/Darkcoin-Qt -reindex
v11 was supposed to be compatible with v10 and just an update to Bitcoin codebase.Usually updates are a race, even when unimportant. But now we get one of the most important ones, and it's mandatory, and we still can't break 50% 48 hours after the mark?
This is why some people shouldn't run masternodes. They don't really care. They barely know how. They're not even paying attention... Some updates need to punt old versions, maybe getting no more payments will get their attention?
It seems obvious in hindsight, but hindsight has happened a few times so that isn't really an excuse anymore.v11 was supposed to be compatible with v10 and just an update to Bitcoin codebase.
It was just announced this morning as a hard fork mandatory update because of unforeseen problems.
Perhaps next time (for once) a schedule to update should be put in place instead of sneaking to mainnet and hoping for the best,
The MANDATORY updates should disallow rewards to Older version masternodes! That would get the owners of MN to pay attention and upgrade their systems faster.....Usually updates are a race, even when unimportant. But now we get one of the most important ones, and it's mandatory, and we still can't break 50% 48 hours after the mark?
This is why some people shouldn't run masternodes. They don't really care. They barely know how. They're not even paying attention... Some updates need to punt old versions, maybe getting no more payments will get their attention?
Agreed.The MANDATORY updates should disallow rewards to Older version masternodes! That would get the owners of MN to pay attention and upgrade their systems faster.....
You are a superstar !Mac OS wallet is on download page...
https://www.darkcoin.io/downloads/
https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/darkcoin-0.11.0.7-osx.dmg
Or am I missing smth?
To reindex on Mac OS open Terminal and run
Code:/Applications/Darkcoin-Qt.app/Contents/MacOS/Darkcoin-Qt -reindex
Did you update to 11.0.7?anything changed in the code since yesterday? I posted that upgrading wallet on my pool caused blocks not being accepted. How can I be sure now it will not happen anymore?
Ok but ins't there a chance they eventually re-peer until the old ones are updated?just to make sure that all information from peers are on correct forks, I understand that we can minimize the fork getting wrong information from older version peers by manually checking the peer info (getpeerinfo) and kill connection with those outdated version by ourselves because reindex is taking too much resources.
Yes, they will re-peer.Ok but ins't there a chance they eventually re-peer until the old ones are updated?
Also how can you get a list of IP still on 70051 using peerinfo? its a long list of peers...