Search results

Pretty sure, libdb version. file wallet.dat has LSN 1/17743, past end of log at 1/333 Commonly caused by moving a database from one database environment to another without clearing the database LSNs, or by removing all of the log files from a database environment DB_ENV->log_flush: LSN of...

* This guide use dumpprivkey and importprivkey * Purpose of this guide is less hassle in wallet backup. * Tested in testnet * user ms06 and user ms05 * As address(private key) for NM is in both wallet, spend in main wallet could spend some portion of NM's 1K. ----> This will not break backup...

If privkey, masternodeaddr, and wallet.dat at local and privkey at remote are changed, there should be no problem. If any mismatch happens, remote ip address would be banned by others. This cause a lot of headache. My test experience in testnet would be help...

Hmm, what was the version of libdb ? I saw a warnning on binary wallet compatibility. https://github.com/darkcoinproject/darkcoin/blob/master/doc/build-unix.md Ubuntu precise has packages for libdb5.1-dev and libdb5.1++-dev, but using these will break binary wallet compatibility, and is not...

Banning is done by ip address. So changing ip will help. You don't need to make a New wallet. Backup wallet. darkcoind backupwallet new_name_01_wallet.dat Using same wallet, make a new address, send 1k DRK to the new address. Backup wallet. darkcoind backupwallet new_name_02_wallet.dat And...

Difference between commands. getaccountaddress : getaccountaddress will return the same address until coins are received on that address; once coins have been received, it will generate and return a new address. listaddressgroupings : Returns all addresses in the wallet and info used for...

My experience in testnet might help. https://www.darkcointalk.org/threads/help-test-rc2-forking-issues.1009/page-44#post-8910 In essence, move 1K to a NEW address, make a new masternodeprivkey, then restart.

I haven't test hot only setup.

There is only one difference in local and hot config. masternodeaddr=remoteaddress:port If masternodeaddr is in darkcoin.conf, it's local. So check your dackocin.conf, if it has masternodeaddr. If setup is hot only config, masternodeaddr is not needed. Did you use externalip in config ...

ms06@x60t:~> darkcoind listaccounts { "" : -321.00000000, "0" : 425.60000000, "1" : 0.00000000, "123" : 6832.54740000, "ttt" : 1234.00000000 } ms06@x60t:~> ms06@x60t:~> darkcoind getaddressesbyaccount 0 [ "muj9oHwCtoWLcrALSfV7yQS2yh1KLpbXo6"...

My only masternode in testnet, got banned by three other nodes. Uptime of three nodes is more than two days, and 'masternode list' shows all the master node with flag 0. Ban msg is 'Got bad masternode address signature'...

Settings like this will help int a / daemon a / user a bind=127.0.0.1 bind=a.a.a.a externalip=a.a.a.a rpcport=99998 rpcallowip=127.0.0.1 int b / daemon b / user b bind=127.0.0.2 bind=b.b.b.b externalip=b.b.b.b rpcport=9997 rpcallowip=127.0.0.1

Yes, no effect on the proper block chain.

I saw this msg on testnet and mainnet ms06@x60t:~/.darkcoin> ./darkcoind getinfo { "version" : 101001, "protocolversion" : 70018, "walletversion" : 60000, "balance" : 4129.53600000, "blocks" : 21112, "timeoffset" : 0, "connections" : 4, "proxy" : "", "difficulty" ...

"ProcessMessage(dsee, 241 bytes) FAILED" are caused by old version clients. Client version : 0.9.4.6 Client version : 0.9.4.11 Client version : 0.10.8.6 Client version : 0.10.8.11 Masternode entry is broadcasted to network. And the relayed msg through the above clients cause ProcessMessage...

At home skip 4 add swap / it's for ec2 t1 micro. At linux istallation, allocate swap. at 6, skip sysstat at 6, use iptables rule in home section / If machine is VM on home computer, and network setting is NAT, you can skip this two. Use NAT for VM, do not brigde.

Current RC binary supports 64bit only. Code: file darkcoin* darkcoin-qt: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, not stripped darkcoind: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked...

3 servers of mine banned from mainnet peers( 10 ~ 30 min) * banned servers ( sv03, sv04, sv05 in graph) a) 1 server : 0.9.10.1 with p2pool-drk b) 2 servers : 0.9.10.1, listen = 0, only connect=other is used some other peers(including drkpool.com, and explorer.darkcoin.io, 23.23.186.131) in...

PS aka snake tail. Evan tipped `head -1` https://bitcointalk.org/index.php?topic=421615.msg6572728#msg6572728

http://explorer.darkcoin.io/chain/DarkCoin works.