This should go in the OP ASAP. AND again, which wallet should I download 0.9.3.1 or the RC2? I dont plan to run a masternode. THANKS! Both wallets work (on linux anyway), RC2 includes DarkSend beta functionality if you want to test that. |
|
|
|
2.8 MH on 780 Ti is impressive.
Not for ~£500 it isn't.  edit: haha - DRK network hashrate (estimate): 83.06 GH/s |
|
|
|
More mn aggravation:
I can only see one of my masternodes when I run 'masternode list' from the mn itself, it does not show up from elsewhere.
On the mn, getinfo gives:
{
"version" : 100701,
"protocolversion" : 70014,
"walletversion" : 60000,
"balance" : 1000.00000000,
"blocks" : 65867,
"timeoffset" : 0,
"connections" : 11,
"proxy" : "",
"difficulty" : 1206.83445281,
"testnet" : false,
"keypoololdest" : 1399685720,
"keypoolsize" : 100,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : ""
}
so it's connected and up to date.
nmap shows ports 9998,9999 open on mn.
helpme@masternode:~$ netstat -an | grep LISTEN:
tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:9999 0.0.0.0:* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 ::1:631 :::* LISTEN
tcp6 0 0 :::9998 :::* LISTEN
tcp6 0 0 :::9999 :::* LISTEN
darkcoin.conf is:
rpcuser=random_user
rpcpassword=random_password
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
externalip=xx.xx.xx.xx
masternode=1
addnode=23.23.186.131
externalip is correct, conf is otherwise the same as my Amazon box which works fine.
Was previously trying to run this with a local wallet, was having problems with IP:0 showing on mn list, so made a new wallet, addr 0, which now lives on the mn, mn starts just fine.
Any suggestions?
bump watching 'tail -f ~/.darkcoin/debug.log' shows me it's definitely talking to other masternodes  |
|
|
|
|
More mn aggravation:
I can only see one of my masternodes when I run 'masternode list' from the mn itself, it does not show up from elsewhere.
On the mn, getinfo gives:
{
"version" : 100701,
"protocolversion" : 70014,
"walletversion" : 60000,
"balance" : 1000.00000000,
"blocks" : 65867,
"timeoffset" : 0,
"connections" : 11,
"proxy" : "",
"difficulty" : 1206.83445281,
"testnet" : false,
"keypoololdest" : 1399685720,
"keypoolsize" : 100,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : ""
}
so it's connected and up to date. nmap shows ports 9998,9999 open on mn.
darkcoin.conf is:
rpcuser=random_user
rpcpassword=random_password
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
externalip=xx.xx.xx.xx
masternode=1
addnode=23.23.186.131
externalip is correct
Was previously trying to run this with a local wallet, was having problems with IP:0 showing on mn list, so made a new wallet, addr 0, which now lives on the mn, mn starts just fine.
Any suggestions?
|
|
|
|
I want to set up a masternode as well. It looks like a majority are set up at Amazon and in the US. Where should I set it up to benefit the network/coin the most? Or does that not matter?
Outside the US would already be great. Masternode location shouldnt matter at all. If you initialize a Darksend transaction from China to Brazil, the masternode location is irrelevant. The voting system is not based on geo-/ip-information (i hope). It's to bring some diversity to the network. What if Amazon has a problem and all its servers are down ? What if the servers in a specific country are shutdown ? The probability is very low but the risk exists and it must be taken into account for the safety of the network IMO. 2nd croutonnode is up.  And it's neither Amazon nor US. More will follow!  Are you trying the home server route? Maybe when you've worked out all the kinks you could share your knowledge?  No, this one is on a paid-for VPS, but it's cheap and kind of local to me. (For a very loose definition of local, but it's better than across the Atlantic. ) Couldn't get the remote wallet thing working this time so just doing it the original way with stupendously long passwords and scary voodoo incantations.  I'm going to set up another tomorrow on my home box. If I get DDOS'd so be it, worst that can happen is my intertubes go down for a while, my home box is locked up tight, there's no danger of losing any DRK unless someone turns up and puts a gun to my face but they'd first have to get past the assault-crocodiles in the castle moat... |
|
|
|
I know most people are under the impression that no DDOS protection is needed if you lock down the ports etc, but my next node will be 100% DDOS protected. I'd hate for Darkcoin to be a laughing stock if all nodes were knocked offline by some very determined people.
I don't think there's such a thing as 100% DDOS protected but if there is, please tell us how! |
|
|
|
I want to set up a masternode as well. It looks like a majority are set up at Amazon and in the US. Where should I set it up to benefit the network/coin the most? Or does that not matter?
Outside the US would already be great. Masternode location shouldnt matter at all. If you initialize a Darksend transaction from China to Brazil, the masternode location is irrelevant. The voting system is not based on geo-/ip-information (i hope). It's to bring some diversity to the network. What if Amazon has a problem and all its servers are down ? What if the servers in a specific country are shutdown ? The probability is very low but the risk exists and it must be taken into account for the safety of the network IMO. 2nd croutonnode is up. And it's neither Amazon nor US. More will follow! |
|
|
|
masternode related question:
I am buggering about trying to get a mn with remote wallet setup, having port:0 type issues, so I checked to see if port 9999 was open on the server:
Nmap scan report for xx.xx.xx.xx
Host is up (0.057s latency).
Not shown: 997 closed ports
PORT STATE SERVICE
22/tcp open ssh
9998/tcp open distinct32
9999/tcp open abyss
Anyone know what the hell distinct32 and abyss are? This is on Ubuntu14.04 desktop with basically nothing extra but darkcoind (and dependencies) installed.
That's just a name. http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?&page=16sv2:~ # cat /etc/services | grep 9999
distinct 9999/tcp # distinct
distinct 9999/udp # distinct
sv2:~ # cat /etc/services | grep 9998
distinct32 9998/tcp # Distinct32
distinct32 9998/udp # Distinct32
Nothing to worry about then? Damn, means I haven't found the problem yet...  |
|
|
|
masternode related question: I am buggering about trying to get a mn with remote wallet setup, having port:0 type issues, so I checked to see if port 9999 was open on the server: Nmap scan report for xx.xx.xx.xx Host is up (0.057s latency). Not shown: 997 closed ports PORT STATE SERVICE 22/tcp open ssh 9998/tcp open distinct32 9999/tcp open abyss Anyone know what the hell distinct32 and abyss are? This is on Ubuntu14.04 desktop with basically nothing extra but darkcoind (and dependencies) installed. edit abyss is some sort of web server, still no idea what distinct32 is, and neither are even installed as far as I can tell... |
|
|
|
|
I refuse to mine shitcoins on general principles.
62 masternodes! Bet there's 200+ by the 14th, and 500 by the 21st.
|
|
|
|
Cache coin are waiting for DarkSend to go open source so they can make their new PoS with anonymity added. Hopefully eduffield will release the source as obfuscated perl. |
|
|
|
chaeplin it would be handy if your masternode count page listed the actual masternodes by IP. Because this would save me valuable seconds each day logging in to mine to see if they are still alive.  edit: or would this just provide a convenient list for DDOSers?  The "masternode list" command already does this for you. You don't have to be on the masternode box in order to execute it. Hah, I never even thought of that, I just wasted ten minutes writing a cron job to email me the same thing from the masternode and was feeling pleased with myself.  |
|
|
|
chaeplin it would be handy if your masternode count page listed the actual masternodes by IP. Because this would save me valuable seconds each day logging in to mine to see if they are still alive. edit: or would this just provide a convenient list for DDOSers? |
|
|
|
Ok, hold on, another idea.
Lets say 3 masternodes, 1 local wallet.
1) local wallet - address 0 -> 1k DRK -> Masternode 1 start -> close local wallet -> backup_wallet_MN1.dat -> cold storage
2) stop local daemon, delete local wallet.dat
3) start daemon -> address 0 -> 1k DRK -> Masternode 2 start -> close local wallet -> backup_wallet_MN2.dat -> cold storage
4) stop local daemon, delete local wallet.dat
5) etc etc...
This should work too, right? Better even.
That's basically the current procedure. Being able to hold all the MN balances in one wallet would save a little faffing about though. |
|
|
|
Bit of a tradeoff security wise though, I prefer keeping my wallets separate, with separate passwords, in separate physical locations, with separate backups. Guarded by separate assault-crocodiles. Then again I'm both paranoid and inept. I just have regular crocodiles. Where do you get them trained to become assault crocs? WI? My regimen includes forced viewing of X Factor and daily injections of supplemental crocosterone, about 300mg/half-ton of bodymass. |
|
|
|
Does that mean we can run multiple masternodes from the same local wallet?
Dunno, but running multiple "nodes" from one wallet / computer kind of goes against the distributed mixing network idea. So I hope the answer is "no". That is absolutely not the idea. Its for the remote/local setup. the masternodes would still do the mixing, authored by the local wallet. At least that my understanding of it. 1000 DRK, one masternode @illodin is right, the idea is to make it costly to run a masternode. You'd still need 4000 DRK to run 4 MNs, just each 1000 in it's own addr 0. Bit of a tradeoff security wise though, I prefer keeping my wallets separate, with separate passwords, in sepatate physical locations, with sepatate backups. Guarded by separate assault-crocodiles. Then again I'm both paranoid and inept. Wouldn't surprise me if eduffield made this possible weeks/months ago and just forgot to mention it to anyone. I thought each masternode needed it's own static ip It still would have, this is for setups where the 1000 DRK MN balance is stored remotely, each MN still runs on a unique box/VM/IP |
|
|
|
Does that mean we can run multiple masternodes from the same local wallet?
Dunno, but running multiple "nodes" from one wallet / computer kind of goes against the distributed mixing network idea. So I hope the answer is "no". That is absolutely not the idea. Its for the remote/local setup. the masternodes would still do the mixing, authored by the local wallet. At least that my understanding of it. 1000 DRK, one masternode @illodin is right, the idea is to make it costly to run a masternode. You'd still need 4000 DRK to run 4 MNs, just each 1000 in it's own addr 0. Bit of a tradeoff security wise though, I prefer keeping my wallets separate, with separate passwords, in separate physical locations, with separate backups. Guarded by separate assault-crocodiles. Then again I'm both paranoid and inept. Wouldn't surprise me if eduffield made this possible weeks/months ago and just forgot to mention it to anyone. |
|
|
|
|
For masternodes, can the static IP be IPv6?
|
|
|
|
Someone with a time machine who knows just how big DRK will be a la Biff from Back to the Future 2? I wish I had that many... Yeah he/she bought another 5397 half an hour ago. Smart individual. Would do the same if I could hide it from the wife.  |
|
|
|
Great stuff, am tempted to post eltitos sexy picture in there. |
|
|
|
|
Show Posts
