flare, send a few DRK crumb over, create a new address and send 1k to it. 6 confirms and should be good to go.
I have tried to make a simple python scripts to send earnings.Another issue I had on testnet, that worries me a bit... is that I had 100k tDRKs, and I send just a few tDRK out ... and even with excess funds it touched my tMasternode 1k deposit.
Another issue I had on testnet, that worries me a bit... is that I had 100k tDRKs, and I send just a few tDRK out ... and even with excess funds it touched my tMasternode 1k deposit.
Wow, I have not noticed 'Coin control' options, because I use cli.Are you saying some of the 1k DRK you deposited for a masternode was used in a transaction and messed up your masternode setup?
If that is the case you need to enable the "Coin Control" options in your client. It allows you to select which inputs you use to make transactions. Make sure you deselect the address with the 1,000.00 DRK for your masternode. That way it won't get messed with. Alternatively, you can generate a new, "cold storage" address and use it. Save the private key somewhere secure. Whenever you finally decide to spend/move the 1k DRK you can import the priv. key into your client and use it like any other address...
The DRK Lord
I have tried to make a simple python scripts to send earnings.
I will but not soon.
Are you saying some of the 1k DRK you deposited for a masternode was used in a transaction and messed up your masternode setup?
If that is the case you need to enable the "Coin Control" options in your client. It allows you to select which inputs you use to make transactions. Make sure you deselect the address with the 1,000.00 DRK for your masternode. That way it won't get messed with. Alternatively, you can generate a new, "cold storage" address and use it. Save the private key somewhere secure. Whenever you finally decide to spend/move the 1k DRK you can import the priv. key into your client and use it like any other address...
The DRK Lord
Lol You and I have had PM's about it. Check our conversation "Downside?" :wink:Wow, I have not noticed 'Coin control' options, because I use cli.
My question is: should i need to generate new privkey when i change new ip address?
So to answer your question: Yes, new IP --> new masternodeprivkey to avoid caching problems in network.
This maybe related to know bug #7 - the caching of IP/pubkey entries was to agressive and led to problems when reusing old masternodeprivkey with new IP. I don't know if Evan already sorted that out to the fullest, but as not all masternodes/pools have updated to 0.x.11.5 yet, the masternodelist still gets polluted by old entries.
So to answer your question: Yes, new IP --> new masternodeprivkey to avoid caching problems in network.
2014-06-27 00:30:29 ThreadRPCServer method=masternode
2014-06-27 00:30:29 CDarkSendPool::RegisterAsMasterNode() - Checking inbound con
nection to '54.203.70.151:9999'
2014-06-27 00:30:29 trying connection 54.203.70.151:9999 lastseen=0.0days
2014-06-27 00:30:29 connected 54.203.70.151:9999
2014-06-27 00:30:29 send version message: version 70018, blocks=92286, us=54.203
.70.151:9999, them=54.203.70.151:9999, peer=9
2014-06-27 00:30:29 Found unspent output equal to nValue
2014-06-27 00:30:29 accepted connection 54.203.70.151:47337
2014-06-27 00:30:29 CDarkSendPool::RegisterAsMasterNode() - Is capable master no
de!
2014-06-27 00:30:29 Misbehaving: 54.203.70.151:9999 (0 -> 1)
2014-06-27 00:30:29 ProcessMessage(dsee, 249 bytes) FAILED
2014-06-27 00:30:29 connected to self at 54.203.70.151:47337, disconnecting
2014-06-27 00:30:29 disconnecting node 54.203.70.151:47337
2014-06-27 00:30:29 socket closed
2014-06-27 00:30:29 disconnecting node 54.203.70.151:9999
2014-06-27 04:24:45 peer=82 says we are misbehaving 20
2014-06-27 04:24:53 ResendWalletTransactions()
2014-06-27 04:25:17 AcceptToMemoryPool: 98.249.39.67:57037 /Satoshi:0.9.11.5/ : accepted 0853eacc92ce9ab2c9836e19e4df13699300fa5b5a51f080ee1501944dd670bd (poolsz 5)
2014-06-27 04:25:27 ProcessMessage(dseep, 116 bytes) FAILED
2014-06-27 04:25:27 ProcessMessage(dseep, 116 bytes) FAILED
2014-06-27 04:25:29 DarkSendStatusUpdate - state: 2 entriesCount: 0 accepted: -1
2014-06-27 04:25:29 DarkSendStatusUpdate - state: 2 entriesCount: 0 accepted: -1
2014-06-27 04:25:29 received block 00000000000225652095ce737f6699d37f50209ab25703e724d53443bf3703d8 peer=1
2014-06-27 04:25:29 Committing 391 changed transactions to coin database...
2014-06-27 04:25:29 SetBestChain: new best=00000000000225652095ce737f6699d37f50209ab25703e724d53443bf3703d8 height=92378 log2_work=58.694145 tx=406010 date=2014-06-27 04:24:49 progress=0.999999
2014-06-27 04:25:29 ERROR: CTxMemPool::acceptableInputs() : inputs already spent
2014-06-27 04:25:29 CDarkSendPool::NewBlock - Is Masternode, resetting
2014-06-27 04:25:30 ProcessBlock: ACCEPTED
-------
2014-06-27 04:26:28 getblocks -1 to 0 limit 500 peer=84
2014-06-27 04:27:48 dsee - Got NEW masternode entry 54.244.103.227:9999
2014-06-27 04:27:48 ERROR: CTxMemPool::acceptableInputs() : inputs already spent
2014-06-27 04:27:48 dsee - Rejected masternode entry
2014-06-27 04:27:48 dsee - Got NEW masternode entry 54.244.103.227:9999
2014-06-27 04:27:48 ERROR: CTxMemPool::acceptableInputs() : inputs already spent
2014-06-27 04:27:48 dsee - Rejected masternode entry
Hey guys, i'm having a strange "problem":
i got new ip address from ISP. so i move my Maternodes from old IP address to new ones. (in the main net not test net). I don't change any setting which is working perfect well on the old ip except the LOCAL config file that point to the new REMOTE masternode ip address. In President's Masternode list, some of my Masternode shows in new ip address, some shows in old address. Even strange is that: one of my masternode should be showed in NEW IP address but not. It got paid still.....
All of my masternode version are: 10.11.4 (i will update today to 10.11.5)
My question is: should i need to generate new privkey when i change new ip address?
Thanks in advanced.
I recieved a 10% masternode payout. Just for your information. Block 92227.
http://explorer.darkcoin.io/block/0000000000041c5386c19acc83bcf9bf0f8df28e245ba86ed1dbb6a041ea2db3
Will this also be fixed with the masternode enforcement?