Re: [ANN][DRK] DarkCoin | First Anonymous Coin | First X11 | First DGW | ASIC Resistant
Another question about DarkSend:
- Do masternodes pay TXfee while they move coins as part of the DarkSend transactions?
Or course, the planned node-reward will cover that if they do, but there is no reward yet, so I would effectively pay for being a node.
- Do masternodes pay TXfee while they move coins as part of the DarkSend transactions?
Or course, the planned node-reward will cover that if they do, but there is no reward yet, so I would effectively pay for being a node.
Nope.
I saw you were having problems and it's really difficult to debug at the moment. I'll add some commands and upload a new daemon.
Ok, I will give it another try and report back.
The problem is that darkcoind won't save more than a few hundreds of keys into the wallet.dat, no matter how big keypool I ask for (it does generate all the 10000 or more keys into the thin air but saves only ~500 initially and only ~200 new after it flushes those original 500 unencrypted keys when you later encrypt the file) and I figure DarkSend will eat the keys from the keypool like a crazy addict, and thus you will either need to periodically input your password on the online server (risking your coins if somebody hacked it, even more if you do it automatically and thus you keep the password on the online machine) or copy the wallet.dat to a flash drive, refill it's keypool on an offline computer and copy it back (while your masternode is offline).
Masternodes will never use any new addresses in the keypool, unless you send funds from the node itself. They're simply the center point that all users will connect to for mixing at a specific moment in time.
Other than that, great guide.
Perfect.
I wasn't sure if masternodes need certain amount of coins so they can actively move them around different addresses or that 1000 DRK is more like a "stake" which lays dormant the whole time.
In this case, one could also encrypt the wallet.dat with a random key and immediately destroy it forever (so even you don't know it) with a single key pair inside and print out the private key as a paper wallet which can be kept somewhere safe (e.g. not in your house and/or next to the server hardware).
When you decide to shut the node down and spend your coins, you simply delete your wallet.dat and import the private key from the paper wallet to a freshly generated wallet.dat
Where will node reward coins be sent?
If they go to the same address, won't the increased amount of coins disqualify that node from becoming a masternode?
Is it checked if your address had exactly 1000 DRK transaction once and it still has that 1000 DRK but ignores any other incoming and/or outgoing transactions?
But this also raises a serious question:
What stops people from faking the ownership of a 1000 DRK address if the masternode daemon doesn't need the private key for that public key?
For example, I already posted my 1000 DRK address. Somebody could simply claim it and become a masternode while I am struggling to finally connect my node.
He won't be able to spend my coins, but he will be registered as a masternode while I can't become one.