I don't think he's very happy about the viddy I'd hate to see Camo leave BCT He really is a good guy and like some of us - a little mis-understood I enjoyed his post, and enjoyed the video a great deal. Would be a shame if he got twisted up about it. Maybe he needs some therapeutic murdering animal time, let the blood flow, and then get back to setting up the masternodes we need. Looks like Camo might be serious :-( via SMS: Me: (1/2) Reading through bct. A lot of people don't want you to bail. So 8:14 PM Me: (2/2) don't leave 😀 8:14 PM Camosoul: Meh, moving on... edit for correction We should give him a day or two, then commission georgem to create some of camos favorite things. I'm thinking pictures of thick brunnettes, not wearing much, chewing on the jugulars of stupid people, sporting darkcoin tattoos. Edit: + Assault rifles. |
|
|
|
I don't think he's very happy about the viddy I'd hate to see Camo leave BCT He really is a good guy and like some of us - a little mis-understood I enjoyed his post, and enjoyed the video a great deal. Would be a shame if he got twisted up about it. Maybe he needs some therapeutic murdering animal time, let the blood flow, and then get back to setting up the masternodes we need. |
|
|
|
Holy shit that had me laughing |
|
|
|
Now all that is needed for full anonymous delivery, is that masternode network would support trustless decentralized mixing of molecular teleportation transports so the authorities couldn't spy what stuff is being teleported to your house.
Evan pls |
|
|
|
If you think camo doesn't know how to run a masternode.... It appears there is someone that is pulling all the masternodes from the wallet and running scripts on them to hack in.
Is this a surprise? And in this case they was able to gain access via SSH, so it had nothing to do with problems in the wallet/daemon/masternode itself.
As suspected. - The firewall was not running, so all ports were open
- Root access via SSH was allowed
- OpenSSL v1.0.1f was installed on the server
- The password to unlock the wallet was still in bash history command
- The root password was less than 8 characters
As suspected. My recommendations: - DO NOT allow root ssh access
- Only open port 9999 in your firewall to the world
- Only open port 22 (SSH) to a trusted ip
- Setup SSH to use certificates for logging in
- Do not run any application on the server that you dont have to
- Encrypt you wallet
- Clear your bash history
All common sense... It worries me that a rote list is being handed out. These are things a person should know if they're going to support the network... If a person doesn't know this much already, they have no business running any server on the internet, much less a masternode. Following some rote guide line by line will only give them a false sense of security and no ability to handle the future. Frankly, I'd prefer all ports but 9999 and TOR Listen be secured by port knocking. Re-direct all externally accessible services through TOR so that they only listen to localhost and no known .onion exists for those services to anyone but yourself. Since TOR uses renzdezvous points, the TOR port being open grants them access to none of the services passing through it, and no idea what the traffic is, where it goes, what it's for, etc... They can't protscan a port that doesn't exist. SOCKS5 stream for the win. Using TOR for this has massive advantages completely removed from it's anonymity/encryption/obfuscation functions.I re-route all my SSH through TOR. SSHD doesn't even listen to the NIC, localhost only. Also, the entire SSHD service is port knocked to trigger "service sshd start" on top of not even listening to the NIC... Run knock sequence then ssh through socat .onion... Nobody even knows it's there... Nobody knows the address but me. Logs can't even give me away since I'm coming in through tor... If only DPR had used his head... ;-) his wallet address is XhGwaKJPMdqEyMU85QBReNNMzVGKDW2EPz
He learned the HARDWAY how not to setup your masternode. I will be putting together a list of things to check and an ISO and AMI for people to use with MOST of the issue addressed, you will still be responsible for checking any think I missed and verify it works for your setup.
His lose WILL help everyone else by showing what you MUST setup so please help him where you can. I will pull some together myself to send.
Pain is an excellent teacher. A smart man learns from his mistakes. A wise man learns from the mistakes of others. If you don't know what you're doing; don't! It's sad and all, but I'm not sending him any welfare. I want him to learn. Let it hurt... Call me a meany poopie face if you want, but this was super extreme stupid. No excuse at all. If you don't know what youo're doing; don't. There is no guide that can teach you common sense. You MUST understand. There is no substitute. |
|
|
|
I think this is an appropriate time to repost. It's just so pretty. |
|
|
|
|
It is literally impossible to make everyone happy all the time. If the Dalai Lama snapped his fingers and ended world hunger and everyone received all the food they every wished for, Maruchan Ramen noodles would suddenly go out of business and everyone that worked for them would lose their jobs and be super pissed. Its a convoluted and retarded point, but you get my gist.
|
|
|
|
Apparently, I have no idea how to navigate git... Lols. I still don't. Link == win. 512MB vultr $0.007 SSD plans can't build... RAM insufficient... build local, scp... You can make some swap space, buy yeah if you have lots of MNs it's quicker to build it on your pet monsterbox, scp it to one of your MN's and then use that to push it to the rest, much quicker than uploading umpteen times on a domestic connection, unless you're very lucky in the local fibre department. Unfortunately, that link didn't help me, it's still not 10.16... I'd love to give this a shot but when I git clone the URL on the start-many branch, it's 15.13 I'm unsure if anyone is quite advocating main net use yet but here it is: https://darkcointalk.org/posts/26020/ |
|
|
|
seems like a smart move to introduce this many masternode thing to get way more masternodes in a short time - and thereby increasing the strength of the network.
Yep, we need more masternode to make DRK scarcier than ever. The price will increase and maybe touch the moon. Go DRK, go ! price shouldn't be your primary motivation if you truly care about this project.. Absolutely. It IS however a defense against sybil attacks. If the price went down to .01 USD, it wouldn't cost very much to own the entire masternode network and subvert it. |
|
|
|
Is 8.50 MH a good speed for 2 x R9 280x series card .
Hell yeah *post your setting pls { "pools" : [ { "url" : "pool", "user" : "us", "pass" : "xx" } ] , "intensity" : "16,16", "worksize" : "256,256", "kernel" : "x11mod", "lookup-gap" : "2", "thread-concurrency" : "24576,24000", "shaders" : "2048,1792", "gpu-threads" : "5,5", "gpu-engine" : "1150,1150", "gpu-memclock" : "1500,1500", "gpu-memdiff" : "0", "gpu-powertune" : "0", "gpu-vddc" : "0.000", "temp-cutoff" : "70", "temp-overheat" : "65", "temp-target" : "60", "api-mcast-port" : "4028", "api-port" : "4028", "expiry" : "90", "failover-switch-delay" : "60", "gpu-dyninterval" : "7", "gpu-platform" : "0", "log" : "5", "no-pool-disable" : true, "queue" : "0", "scan-time" : "59", "tcp-keepalive" : "30", "temp-hysteresis" : "2", "shares" : "0", "kernel-path" : "/usr/local/bin", "no-client-reconnect" : true, "no-submit-stale" : false, "load-balance" : true } Nice work, not sure if I'll be able to reproduce your hash rate, but thanks  |
|
|
|
Is 8.50 MH a good speed for 2 x R9 280x series card .
Hell yeah *post your setting pls |
|
|
|
Been waitin for someone to crack that one hahahah. |
|
|
|
DAMNIT I'M STILL DICKING AROUND LEARNING LOCALBITCOINS DON'T SKYROCKET PRICE YOU FUCKERS!! But seriously, without cryptsy or mintpal, this coin just became a bit rare. Take it easy with the buys until I make mine!  |
|
|
|
It's the same miner that was paying his own masternode: XixmyNSGGGXEJEzKghoRnTto5ZVhficSek Gotcha. Looks like he'll get cleaned up in a week. Thanks |
|
|
|
Maybe I have to say that I updated wallet soo many times, but this time I didn't close wallet while was doing renaming. Just fast routinely sent. followed simple guide without thinking. Its Linux.
Usually I just move out wallet.dat, start new QT and move new wallet.dat too, put old one back. delete old QT.
Scary thing is it really could happen to anyone. I really wasn't speaking directly about you, just thinking about people needing to in the future. I'm glad Propulsion was able to help you, cheers! |
|
|
|
Since the last guy corrupted the hell out of his wallet, I've updated these instructions (in red).
For wallet incompatibility message.
Note: Never modify any files in the darkcoin directory with QT or the daemon running!
on windows on the search bar type in:
%appdata%
A folder will pop up. Go to Roaming and then Darkcoin.
Before beginning, make sure QT/daemon is not running!
Inside the darkcoin folder, you'll see a "wallet.dat" file.
Rename it to "wallet.dat.old" and then start the new QT. This will generate a new wallet. Copy the first address to a notepad and close the wallet.
Back in the Darkcoin folder, rename the "wallet.dat" file to wallet.dat.new and rename the "wallet.dat.old" to "wallet.dat"
Open QT again. Send your entire balance to the new address and let it get one confirmation. After that, close QT, rename "wallet.dat" to "wallet.dat.old" and "wallet.dat.new" to "wallet.dat".
Open QT again. Now your entire balance should be in the new wallet format.
______________________________________________
Also, AzzAz, I sent you an email.
I would also propose the possibility of using an exchange as a stopover for coins while new wallet.dat is negotiated if someone really didn't know what they were doing. |
|
|
|
install the wallet today the old version was working fine befor
So you did have a previous darkcoin wallet on your computer, and then downloaded the new one today, correct? |
|
|
|
can someone please show a way updating my wallet to the latest...i mean i just need to replace the wallet.dat file??or is more complecated??and i want also to setup 12 masternodes !! can this be done by me on windows just following the guides or i do need help?
on windows on the search bar type in: %appdata% A folder will pop up. Go to Roaming and then Darkcoin. Inside the darkcoin folder, you'll see a "wallet.dat" file. Rename it to "wallet.dat.old" and then start the new QT. This will generate a new wallet. Copy the first address to a notepad and close the wallet. Back in the Darkcoin folder, rename the "wallet.dat" file to wallet.dat.new and rename the "wallet.dat.old" to "wallet.dat" Open QT again. Send your entire balance to the new address and let it get one confirmation. After that, close QT, rename "wallet.dat" to "wallet.dat.old" and "wallet.dat.new" to "wallet.dat". Open QT again. Now your entire balance should be in the new wallet format. If you have trouble with this, I don't recommend you trying to run your own Masternode. Why not simply run new wallet over old? Because the keypool size changed from 100 to 1000. Great. I did it and... when I first opened new QT there was 1 adress. I did all as said, copied that to notepad and closed wallet. changed wallet.dat as said, and at the end when opened new wallet again: nothing. ! And adress at receive is not the same now?? Help? Right now, before making any changes. Create a duplicate back up of ALL wallet.dat files. Inlcuding any .old or .new. |
|
|
|
can someone please show a way updating my wallet to the latest...i mean i just need to replace the wallet.dat file??or is more complecated??and i want also to setup 12 masternodes !! can this be done by me on windows just following the guides or i do need help?
FYI, if all you need to do is update to the newest wallet, this very well might not require doing anything to your wallet.dat. For updating all that is required is that you download the newest version and run it. If this is coming from a rather old wallet, then you will get a message saying something like "You should send funds to a new wallet", in which case you should follow the wallet.dat instructions. |
|
|
|
|
Show Posts
