Search content
Sort by
Showing 20 of 68 results by freynder
Re: [ANN][DRK] Darkcoin | First Anonymous Coin | Inventor of X11, DGW and Darksend | Instant TX
ok, that seemed to have been the problem 
was still using darkcoin.conf in the directory file instead of masternode.conf
k, didnt know that the masternodeprivkey wasn't supposed to be shared. dont know what they can do with it..?
its not like this is my privkey for my coins
was still using darkcoin.conf in the directory file instead of masternode.confk, didnt know that the masternodeprivkey wasn't supposed to be shared. dont know what they can do with it..?
its not like this is my privkey for my coins
It could be used to update the masternode data or to stop it. You will not lose coins indeed, but potentially lose control of the masternode.
Re: [ANN][DRK] Darkcoin | First Anonymous Coin | Inventor of X11, DGW and Darksend | Instant TX
guys,
is there anyone who can point me to an understandable guide of the start-many setup?
i understand that this should now work properly?
although i haven't found a thread yet where this is well explained.
tx
is there anyone who can point me to an understandable guide of the start-many setup?
i understand that this should now work properly?
although i haven't found a thread yet where this is well explained.
tx
It works perfectly, and is very easy. Instructions are in the download archive, look for /src/darkcoin.version-number/doc/masternode_conf.md
In short:
1. Import your existing privkeys into a new or an existing wallet. Preferably a new up to date wallet.
2. Make a textfile called masternode.conf, structure it according to the directions in masternode_conf.md
3. Unlock your wallet with 'walletpassphrase ' and issue 'masternode start-many' at the console.
thanks for the explanation!
i think i almost got it, though i have some follow up questions, because i keep having an error :
- the error is : options configuration file contains an invalid line 'the mn1 details' only use the key = value syntax (what am i doing wrong here) i used the alia,IP + port, mn privkey, collateral output tx id and index (they are all index 0)
- is it possible to have like 3 mn setup in your wallet for which you can use the start-many command and also have like 2 or 3 receiving addresses which are not meant for masternodes? or does this have to be a wallet with solely the private keys of the public addresses with 1K DRK each on it?
thanks in advance for your guidance
Check the formatting, make sure it's exactly as in the example, single whitespace between each entry, no spare lines/tabs/spaces.
And yes you can have a day-to-day address or whatever else in the same wallet, just make sure when you are sending funds that you select inputs from the day-to-day address (use coin control) so that you don't inadvertently break a Masternode by sending from one of the 1000DRK collateral lumps.
formatting is exactly the same
conf file looks like this currently:
mn1 54.201.192.114:9999 7sPNxbVThiJwCKusGNLqsopE7HAAJ5yZNBZKjfWNEgMpZdjiSA9
defe770ef1ee1977efc84b08d817502b65d18a22dbb8ec5e54681196044ffd6b 0
mn2 54.186.228.115:9999 7sMqM5HxamJRx3k6kLcHnLTuSLyeKDcHiL1nJ1CaFU6ZWJsbCMB
c466666faf0e87b90f4a805613bd349930fb5bc80188ee758e6f6937ba3cd383 0
is there anything more besides this that i need to add?
Are you actually using masternode.conf file? It seems like you are using darkcoin.conf instead.
Also you should not share the private keys on the forum, so better change them.
Re: [ANN][DRK] Darkcoin | First Anonymous Coin | Inventor of X11, DGW and Darksend | Instant TX
If you create a new wallet.dat, encrypt it, back it up, getnewaddress and send funds to it, does the back up of the wallet.dat also have the new address? Does getnewaddress actually create a new address or just assign one? Is that what the keypool size is?
If you generated new address in a wallet, the backup of the wallet will not contain the new address unless it was backed up after the new address was generated.
That is not my understanding. getnewaddress rpc command will get an address from the keypool first, unless it ran out; and add it to the addressbook as a 'receive' purpose address book entry. So the backup wallet.dat would have the new address.
Re: [ANN][DRK] Darkcoin | First Anonymous Coin | Inventor of X11, DGW and Darksend | Instant TX
I have suggested it before:
Why not move the Masternode network completely and solely into the IPv6 space.
Every node could have an arbitrary amount of addresses, bound to an arbitrary amount of wallets.
The node addresses could even be changed all the time by some maintenance protocol.
Why not move the Masternode network completely and solely into the IPv6 space.
Every node could have an arbitrary amount of addresses, bound to an arbitrary amount of wallets.
The node addresses could even be changed all the time by some maintenance protocol.
How would non-IPv6 clients be able to connect to a masternode? I believe most end users like myself currently do not have access to IPv6 through their ISP.
Could MNs run their own DNS service - no more need for a fixed IP?
Not sure exactly what problem this would solve. AFAIK there is also no requirement for a fixed IP currently. The protocol allows to send a dsee message to update the address of a masternode for a VIN.
Really? So I can change the IP of my server (or have my ISP periodically assign me a new one if I'm running a MN on my domestic connection,) keep everything else the same, and it will still work? Guess I missed that memo.
Do you not still have to update your local/remote .conf files with the new server IP?
No, I'm just saying that the protocol allows it. You would still need to change your conf and restart the client to generate the dsee message again. Although nothing prevents anyone to change the client to detect a change of IP address and send an updated dsee to the network. You might even be able to implement this in a script without touching the client: when IP changes, kill darkcoind and restart it with the new IP address.
Edit: Thinking about this futher, this is probably not practical with a locked wallet, as it would need to be unlocked each time to generate the updated dsee message.
Re: [ANN][DRK] Darkcoin | First Anonymous Coin | Inventor of X11, DGW and Darksend | Instant TX
I have suggested it before:
Why not move the Masternode network completely and solely into the IPv6 space.
Every node could have an arbitrary amount of addresses, bound to an arbitrary amount of wallets.
The node addresses could even be changed all the time by some maintenance protocol.
Why not move the Masternode network completely and solely into the IPv6 space.
Every node could have an arbitrary amount of addresses, bound to an arbitrary amount of wallets.
The node addresses could even be changed all the time by some maintenance protocol.
How would non-IPv6 clients be able to connect to a masternode? I believe most end users like myself currently do not have access to IPv6 through their ISP.
Could MNs run their own DNS service - no more need for a fixed IP?
Not sure exactly what problem this would solve. AFAIK there is also no requirement for a fixed IP currently. The protocol allows to send a dsee message to update the address of a masternode for a VIN.
Re: [ANN][DRK] Darkcoin | First Anonymous Coin | Inventor of X11, DGW and Darksend | Instant TX
I have suggested it before:
Why not move the Masternode network completely and solely into the IPv6 space.
Every node could have an arbitrary amount of addresses, bound to an arbitrary amount of wallets.
The node addresses could even be changed all the time by some maintenance protocol.
Why not move the Masternode network completely and solely into the IPv6 space.
Every node could have an arbitrary amount of addresses, bound to an arbitrary amount of wallets.
The node addresses could even be changed all the time by some maintenance protocol.
How would non-IPv6 clients be able to connect to a masternode? I believe most end users like myself currently do not have access to IPv6 through their ISP.
Re: [ANN][DRK] Darkcoin | First Anonymous Coin | Inventor of X11, DGW and Darksend | Instant TX
If something could be done about this should be great : that only need to start it once in local then can keep the wallet in cold for ever.
That's an interesting thought. The reason why the wallet needs to be unlocked is to be able to access the address private key in order to sign the message which is then sent out to the network. If the vin, address and masternode private key remain the same, there should be no reason to have to unlock the wallet again in the future to start the same masternode at a later time. One could think about reusing the same communication. Looking at the current implementation, there is also a check for the protocol version, but this could be excluded from the signed message I guess.
Re: [ANN][NYAN] NyanCoin - ★★★V1.2 Released! KGW Implemented! MANDATORY UPDATE ★★★
Please join one of the most profitable pools. Compare the block stats with other pools and see this pool at 102.18% after a month running. Don't think 0% fee pools are better value but look at the numbers! Running non stop, stable and great block stats!
http://nyan.coindaemon.com
Features:
1% fee
STRATUM, VARDIFF
PPLNS
Dedicated server hardware: 12x CPU, 48GB RAM
Up to date software
Fast payouts - processed every minute
100% uptime so far
Stratum configuration:
Main: stratum.coindaemon.com port 6611
Backup: stratum2.coindaemon.com port 6612
Our stats:
http://nyan.coindaemon.com
Features:
1% fee
STRATUM, VARDIFF
PPLNS
Dedicated server hardware: 12x CPU, 48GB RAM
Up to date software
Fast payouts - processed every minute
100% uptime so far
Stratum configuration:
Main: stratum.coindaemon.com port 6611
Backup: stratum2.coindaemon.com port 6612
Our stats:
Re: [ANN][NYAN] NyanCoin - ★★★V1.2 Released! KGW Implemented! MANDATORY UPDATE ★★★
what's happening with those guys selling at about one third of the price?
Count the zeros:
0.00003490 at btc-cc
0.00000970 at coinedup
So they are selling at 3x coinedup price.
Re: [ANN][NYAN] NyanCoin - ★★★V1.2 Released! KGW Implemented! MANDATORY UPDATE ★★★
Please join our pool:
http://nyan.coindaemon.com
Features:
1% fee
STRATUM, VARDIFF
PPLNS
Dedicated server hardware: 12x CPU, 48GB RAM
Up to date software
Fast payouts - processed every minute
100% uptime so far
Stratum configuration:
Main: stratum.coindaemon.com port 6611
Backup: stratum2.coindaemon.com port 6612
Our stats:
http://nyan.coindaemon.com
Features:
1% fee
STRATUM, VARDIFF
PPLNS
Dedicated server hardware: 12x CPU, 48GB RAM
Up to date software
Fast payouts - processed every minute
100% uptime so far
Stratum configuration:
Main: stratum.coindaemon.com port 6611
Backup: stratum2.coindaemon.com port 6612
Our stats:
Hello all,
Please be informed that as of 2/6 the pool is owned and operated by user nonstopmine. An automatic payout to all miners has been processed. Payment system changed to PROP. The change should be transparent for miners and not require any change to their settings.
Please be informed that as of 2/6 the pool is owned and operated by user nonstopmine. An automatic payout to all miners has been processed. Payment system changed to PROP. The change should be transparent for miners and not require any change to their settings.
If the hashrate has been reduced by 10% does that then mean it has effectively reduced our collective ability to mine?
No, it just means that blocks are found at a lower rate. The reward is divided amongst less people as well which means it will be higher. Your ability to mine always stays the same, it is relative to your own hash power.
I see. Any chance you could explain to me what variance is? I'm still kinda new. Thanks!
It is a statistics term indicating how far off results are from the average.
Hello,
I have been mining with this pool for about a week now and it has been great so far; however, no blocks haven't been found in over a day. Is anything going wrong? did everyone just freak out because of the 1% fee?
I have been mining with this pool for about a week now and it has been great so far; however, no blocks haven't been found in over a day. Is anything going wrong? did everyone just freak out because of the 1% fee?
Hello,
Nothing is wrong, this is just a combination of difficulty, hashrate and variance. With the current hashrate and difficulty, a block is expected to be found every 18.5 hours on average. The current round seems to be a long one and we are already waiting for 32 hours for the block. That is just something that happens with low hashrate pools, variance is an important factor. On the other hand, most of the the previous 10 blocks have been found well below the average, so it works both ways. The 1% fee change had relatively little impact on the total hashrate, maybe 10% lower hashrate.
I hope this helps. You can find the same information on the Statistics->Pool and Block pages.