LOL, I've gotten myself up to 2000 coins and felt so good, like I had all the coins in the world!  Now I feel so puny, LOL


Another LOL

I thought it odd that an airdrop was even briefly considered. It would kill the price of the coin and really not rectify the original issue. New people would take their free coin, then dump... and kill the price, like you said.

I did mention one idea in cryptohunter's moderated thread (unless he deleted it, like most of my other posts) --

The only way I could see something like a mini-airdrop working is if a small amount of coin was given out to early miners/adopters, sort of like a token to partially rectify the early instamine thing. I have no idea how early miners/adopters would even be identified (blockchain/mining address)? But pretend if it could be confirmed, it would get around a couple of problems of a big airdrop, mainly new people gobbling up coins to dump and killing the price of the coin. Those receiving it would be much less likely to dump, were about mining or buying coin early on, so logically they'd be more likely to hold. People would probably still complain, but it's the only way I can see anything like that working.

It's easier to see in the explorer:
http://chainz.cryptoid.info/drk/tx.dws?1b4c93a3bf49ad4855f74121aea68517b1073fd3a75943e19f956ae553cd2207.htm

It looks like some coin was sent but it was broken up in a payment and a fee?  But not sure?

Or the opposite (less miners less network safety). I'm not entirely sure how merged mining operates, but if its simply one mining client doing the same hashing and applying it to multiple coins/pools, then DRK could benefit from merged mining with other X11 coins.

DRK can secure its network far better in this way because the inverse rewards with the increased diff create an artificial barrier for network hashrate that will probably not exceed the 20ghash rate for quite a while. But merged mining with other X11 will bypass this issue and secure DRK well.

DRK miners would probably love to increase their profitability by mining DRK + getting all the extra revenue from DRK clones. If several scrypt coins go the merged mining route, profitability for X11 could come under threat without a merged miner of our own that can be provided as an alternative. I mean if someone can mine, say, 15 scrypt coins with one miner, why would he mine DRK? It wouldn't make sense unless he has a CPU.

What I'm saying should be valid unless there is some kind of technical obstacle that I am unaware off. Perhaps those with Bitcoin merged-mining experience can shed some light.

Awesome, it looks like it was setup correctly, it's registered on the network!

And with that attitude you can say goodbye to your coins quickly.

What people aren't realizing is that by having a master node, you are essentially waving a bright flag saying "Hey, at ip address: xx.xx.xxx.xxx there is $700 (and hopefully a lot more!) just waiting for you to take if you can find it."

And you're thinking, but even if they could hack my server, I still encrypted my wallet with a 32 character password! Well guess what? If you have a master node, it means you're most likely active in the cryptocurrency community, so I can find you. And I can almost guarantee if I could break into your server, that I would be able to link you to both your online persona and your real identity.

And now with all of that, my social engineering attack would begin, you wouldn't even know I hacked your server until maybe even as long as 6 months later, when I crack the password guarding it.

My point is thus, having a master node out there is not something to take lightly unless losing the balance of the wallet is no big deal to you.

I think it is a fantastic idea, I am just warning people who don't have the right skills that having a master node is not for them. And if you have to a.) ask how to set one up or b.) have to ask if you have the right skills, 99.9% chance you should not be setting one up.

This is a very good point. Is there anyway to obscure the Master Nodes real IP address?

Edit: Scratch that. A master node operator could just run it through a proxy or tor.

I personally am not much of a hacker (black hat at least), but I know/talk to people who are, and you are their favorite type of victim. So confident they are secure that it makes it so easy to get an attack in right under their nose because they are absolutely convinced they are invincible.

I'm not saying it would be easy, or that it even would work on you, that is up to a million factors, a non-negligible one of which is pure chance, but if a good, determined hacker wants to RAT your computer and they know a fair amount about you, it is going to happen. If I have access to a server you own, assuming the hosting company has your real contact information, I am going to have your address within a few days from *most* companies, if I wasn't able to already have it through other means. And if I have your address, and as I said, determined enough, most consumer routers have vulnerabilities in them, especially if you don't have the latest firmware. So once I've compromised your router, it is a matter of time watching your traffic until I find something I can exploit, and boom, RAT'ed.

But even more so, as you said, you printed it off. Maybe I'll just break into your house and look around when you're at work.

(By I in the above I mean a nefarious hacker, which I personally am not.)

1.) For $700, most of what I said is not realistic, but for $2000, $5000, $10,000? You bet your ass it is to some people.
2.) You might think everything I just said is ludacris, but I can assure you, it happens, a lot more often than you would think if you didn't have knowledge of it.


About the keypool, if the node is already running, why would you need to refill the keypool offline, all you would have to do is login to the node and run "./darkcoind keypoolrefill" and then backup the latest wallet. Realistically you could setup a cron script to do it that would be just as secure as doing it manually. (if someone got access to the server, they have the wallet, them finding out you encrypted it with a key and then pushed it into a S3 bucket named "wedding_photos.zip" (bonus points if you made the archive actually contain wedding photos which would fool *most* hackers if they got their hands on it) wouldn't matter, they would be able to download it straight from the server)

Anyone? A little help