One thing is for sure, ever since I issued a start-many post update, payments seem to be way more "orderly" than ever before. masternode1 paid, masternode2 paid, masternode3 paid... But I think this may be by design. Feels more like a queue now than pure luck.
My window wallet continually freezes while updating everyday. Hangs when trying to close and doesn't like competing against my Doge, BTC wallets updating even though I made DASH the highest priority for updating from start. Once the BTC and Doge have updated, it appears to work fine after closing program and restarting once the other wallets have updated.
Maybe your CPU and network resources are low because of Doge and Btc, if you use all of them simultaneous.
I compiled Darkcoin on Debian 8.0 with libdb5.1. and it was working just fine. Now I compiled DASH on the same system (with the --with-incompatible-bdb option) and I'm getting "Error initializing wallet database environment /path" error when trying to run ./dashd Is there any way to resolve this issue without downgrading to libdb4.8. since I would probably face wallet.dat incompatibility after that. As far as I know BDB is not backwards-compatible. debug.log Code: 2015-04-07 10:00:23 Dash version v0.11.2.17-09a8987-beta (2015-04-03 20:26:55 -0700) 2015-04-07 10:00:23 Using OpenSSL version OpenSSL 1.0.1j 15 Oct 2014 2015-04-07 10:00:23 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-04-07 10:00:23 Default data directory /root/.dash 2015-04-07 10:00:23 Using data directory /root/.dash 2015-04-07 10:00:23 Using at most 125 connections (1024 file descriptors available) 2015-04-07 10:00:23 Using 4 threads for script verification 2015-04-07 10:00:23 Using wallet wallet.dat 2015-04-07 10:00:23 init message: Verifying wallet... 2015-04-07 10:00:23 CDBEnv::Open : LogDir=/root/.dash/database ErrorFile=/root/.dash/db.log 2015-04-07 10:00:23 ERROR: CDBEnv::Open : Error 22 opening database environment: Invalid argument 2015-04-07 10:00:23 Moved old /root/.dash/database to /root/.dash/database.1428400823.bak. Retrying. 2015-04-07 10:00:23 CDBEnv::Open : LogDir=/root/.dash/database ErrorFile=/root/.dash/db.log 2015-04-07 10:00:23 ERROR: CDBEnv::Open : Error 22 opening database environment: Invalid argument 2015-04-07 10:00:23 : Error initializing wallet database environment /root/.dash! 2015-04-07 10:00:23 Shutdown : In progress... 2015-04-07 10:00:23 StopNode() 2015-04-07 10:00:23 Verifying mncache.dat format... 2015-04-07 10:00:23 Loaded info from mncache.dat 1ms 2015-04-07 10:00:23 Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, nDsqCount: 0 2015-04-07 10:00:23 Writting info to mncache.dat... 2015-04-07 10:00:23 Written info to mncache.dat 3ms 2015-04-07 10:00:23 Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, nDsqCount: 0 2015-04-07 10:00:23 Masternode dump finished 5ms 2015-04-07 10:00:23 Shutdown : done db.log Code: Page 0: metadata page corrupted Page 0: could not check metadata page wallet.dat: DB_VERIFY_BAD: Database verification failed illegal flag combination specified to DB_ENV->open illegal flag combination specified to DB_ENV->open What I'm not getting is why it shows "Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)" in the debug.log and not the Berkeley DB 5.1.29: (October 25, 2011) which is actually being used on my system Or is it somehow possible to safely downgrade an encrypted wallet.dat to the libdb4.8.? Ideas are appreciated
can you try dump privkey on the wallet and import it into the wallet with downgraded libdb, if this possible ? if all fail you can just send all coin to polo and send back to your new wallet.
yes, but since I have 10k+ addresses in my wallet, extracting and then importing privs to a new wallet is a hell of a job. I'd better try fixin' current installation when I'm trying to use a pre-compiled binary, it shows error " Warning: wallet.dat corrupt, data salvaged! Original wallet.dat saved as wallet.{timestamp}.bak in /root/.dash; if your balance or transactions are incorrect you should restore from a backup." which is no surprise, since precompilled binary is built with libdb 4.8. Code: 2015-04-07 12:48:53 Dash version v0.11.2.16-91d5f04-beta (2015-03-30 09:06:26 -0700) 2015-04-07 12:48:53 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015 2015-04-07 12:48:53 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-04-07 12:48:53 Default data directory /root/.dash 2015-04-07 12:48:53 Using data directory /root/.dash 2015-04-07 12:48:53 Using at most 125 connections (1024 file descriptors available) 2015-04-07 12:48:53 Using 4 threads for script verification 2015-04-07 12:48:53 Using wallet wallet.dat 2015-04-07 12:48:53 init message: Verifying wallet... 2015-04-07 12:48:53 CDBEnv::Open : LogDir=/root/.dash/database ErrorFile=/root/.dash/db.log 2015-04-07 12:48:53 Renamed wallet.dat to wallet.1428410933.bak 2015-04-07 12:50:23 Salvage(aggressive) found 44351 records 2015-04-07 12:50:38 : Warning: wallet.dat corrupt, data salvaged! Original wallet.dat saved as wallet.{timestamp}.bak in /root/.dash; if your balance or transactions are incorrect you should restore from a backup. 2015-04-07 12:50:38 Bound to [::]:9999 2015-04-07 12:50:38 Bound to 0.0.0.0:9999 2015-04-07 12:50:38 init message: Loading block index... 2015-04-07 12:50:38 Opening LevelDB in /root/.dash/blocks/index 2015-04-07 12:50:38 Opened LevelDB successfully 2015-04-07 12:50:38 Opening LevelDB in /root/.dash/chainstate 2015-04-07 12:50:38 Opened LevelDB successfully 2015-04-07 12:50:53 LoadBlockIndexDB(): last block file = 5 2015-04-07 12:50:53 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=4036, size=26747827, heights=244396...248424, time=2015-03-31...2015-04-07) 2015-04-07 12:50:53 LoadBlockIndexDB(): transaction index disabled 2015-04-07 12:50:53 LoadBlockIndexDB(): hashBestChain=00000000000de9d5924cd6c95d262bf5b7aacd845a32d48becba87d969d3d626 height=248424 date=2015-04-07 12:21:00 progress=0.999739 2015-04-07 12:50:53 init message: Verifying blocks... 2015-04-07 12:50:53 Verifying last 288 blocks at level 3
Start the old Darkcoin db5.1 wallet and send the funds to a new address of an official wallet from dashpay.io.
The way you enter the queue doesn't matter. When you do start-many your nodes just closer to each other so there is more probability that they will be payed one by one but there is no advantage over other ways of starting nodes.
i think that you can automate dumppriv key using bash script or something. 1. listaddress grouping into addr.txt 2. trim addr.txt 3. dumpprivkey from addr.txt into privatelist.txt 4. trim files.txt 5. importprivkey into dashcoin from privatelist.txt
Warning: Just sent from darkcoin v0.11.1.25 to dash wallet and it did not arrive, must have gone on the wrong chain.
I think it not work because there is no nodes for Darkcoin. Copy old wallet to Dash folder and do it from there with Dash client. Edit: typo
There are nodes, it worked until 2nd April around the fork time. Going to be a few people gonna do this who haven't upgraded! ..
It was not fork, but stuck because reference node. Did you try this: Copy old wallet to Dash folder and do it from there with Dash client.
No, copying the wallet is not the point-I am thinking what will happen to others, I am just pointing out if anyone tries sending from darkcoin thats whats going to happen, I suppose there is no way to avoid that as upgrade is mandatory with the protocol change.
Comes back on -reindex as expected. Edit: Thats odd I tried it 3 times and only 1 time did the coin reach the Dash wallet correctly so its luck of the draw I guess.
this is how i extract private key and also maybe import in batch. Pls inform me if make mistake, thanks run coin-qt -server ============ dump priv key ============ ./coind listaddressgroupings >> test.txt awk '/"/' test.txt >btest.txt #only print those between symbol cat btest.txt | sed 's/"//g' >ctest.txt #remove symbol cat ctest.txt | sed 's/,//g' >dtest.txt #remove symbol cat dtest.txt | sed 's/ //g' >etest.txt #remove space awk '/./' etest.txt >> ftest.txt #remove empty awk < ftest.txt '{ print "./coind dumpprivkey " $1" " $2" " $3" " $4 }' | "/bin/sh" >>privkey.txt ============ import privkey.txt ============ awk < privkey.txt '{ print "./coind importprivkey " $1" " $2" " $3" " $4 }' | "/bin/sh" >privkey1.txt
Is there a post that explains how to set up your masternode to donate to the foundation? I am looking for the last hour and can't find anything. Sorry, I know there is a post somewhere I literally can not find it. I was thinking about making a guide for others, maybe even turn it into a video. Any help pointing me in the right direction would be rad. I know it's gotta be easy. I also know that it might not be working at the moment, but i still want to know. thanks.
UdjinM6, many thanks for your help. Really appreciate it. I somehow managed to get it working with the pre-compiled binary and -salvagewallet and -rescan options. Which is a bit weird since I have libdb5.1. installed and the binary most likely compiled with libdb4.8. I also was able to unlock a salvaged wallet.dat, so now everything is up and running. Cheers
I had the same question and found this post on doing donations with a multi masternode config. https://github.com/darkcoin/darkcoin/blob/master/doc/masternode_conf.md And this is the link to setup multiple masternodes from one wallet. https://dashtalk.org/threads/reuben...rnodes-from-one-wallet-guide-start-many.4034/
