Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 5520. (Read 9723748 times)

Point taken. But we're not talking about consolidating holders. You and I will not pool our DRK and make a node. You'll run yours how you see fit and I'll run mine as I see fit. If my 50,000DRK node gets DDoSed, then that's 50 entries you don't have to contend with for an hour or so. Do I care when I'm getting 50 entries while I'm NOT getting DDoSed? My bigass node is just one node. The network will be glad to see me disappear for a while. ;-)

As with government scrutiny in other places, I love being the big shiny target they can't really hit. It lets all the other people scurry around unnoticed... If I'm pulling odds on 50 entries a block, and get DDoSed for an hour or so, I don't care, and that means everyone else can relax, while also getting better odds...

What about a trade off as in a cap of three MN's per address and/or IP.

Anyone who wants to set up masternodes but doesn't know how, just post what youre doing in this thread, me and others will help you for free. Or go in the irc room and people will help you there to, its not hard.

They can even offer bigger rewards (the non distributed DRK) to make the miners stay.

No! Forcing people to manage over 2 dozen separate boxes only generates orders of magnitude more opportunities for human error. Too much of a good thing. I'd rather have one node hardened as hell becasue it's holding a million in DRK. Watch to see how often a node gets elected to know how much is in it.. Only adds that much more incentive to make sure people are securing the nodes and thus securing the network. We've already got somebody who was sloppy enough to get robbed... Maybe they'll start taking it more seriously when they can put 50,000 drk in one node, eh?

No! Forcing people to manage over 2 dozen separate boxes only generates orders of magnitude more opportunities for human error. Too much of a good thing. I'd rather have one node hardened as hell becasue it's holding a million in DRK. Watch to see how often a node gets elected to know how much is in it.. Only adds that much more incentive to make sure people are securing the nodes and thus securing the network. We've already got somebody who was sloppy enough to get robbed... Maybe they'll start taking it more seriously when they can put 50,000 drk in one node, eh?

Avoid multiple tickets for masternodes. It will reduce number of nodes making the system less resilient.

That part:


...won't work. We couldn't even get the miners of coinmine to switch when they were >51% because they were getting consistency and low variance (compared to the official which was DOS'ed).

The days of 2-3 pools also seem to be over: http://drk.poolhash.org/poolhash.html

The pie chart is revealing.

Just use hard fork and another system of election/payment that doesn't affect network stability. "Honest pools" won't work. Guaranteed.

If the pool doesn't pay the correct amount to the correct node, we'll know and we'll shame them. We'll get miners to move to honest pools.

That is not what I mean. I edited my previous post to be more clear.

As I currently understand Evan's plan:

Network pays pool 100% of reward - pool must split reward 80/20 - 80% to miners, 20% to masternode

Are you are saying a dishonest pool can't break this system?  Or I am misunderstanding what Evan proposed.

There were originally two strategies for masternode payments. One requires a hardfork and one doesn't. I originally decided to do the one that does, because you can't cheat as a pool operator. But, that comes with a price. The code must reject cheating blocks and that's what caused the forking issue.

The other way is to setup the client to pay nodes in a provably fair way. If the pool doesn't pay the correct amount to the correct node, we'll know and we'll shame them. We'll get miners to move to honest pools.

Like others have suggested, all of the groundwork has been laid. I have implemented the masternodes, the election system for payments and it's compatible with this soft fork.

So why 20% fees for masternode payments? This essentially will create twice as many nodes and create a much higher cost to spy on the network. It also creates a larger feedback loop for the price (because as darkcoin is taken out of the supply, it drives the price up), which is good for all of the investors and security of DarkSend. Miners will get less coin, but it's been proven time and time again that when you decrease the coins generated the price will just go up to meet the cost of mining.

My goal with Darkcoin has always been to take the #2 spot from Litecoin. I believe we have the best chance we've ever had now and these changes will actually help realize that goal.

As for my communication? Lately I've just had my nose to the grindstone, coding all of the time. I intend to be much more involved with the community in the future. This will include getting a team of software developers and managing the vision of the project. I think my time might be better spent in the future doing interviews, speaking at conferences and being Darkcoin's figurehead.

If someone had their masternode coins stolen it was probably due to poor security on their box.

With almost 400 masternodes I'd be shocked if someone didn't have their coins stolen.

For people's peace of mind, I still think the private keys should never need to touch the masternode. All thats needed to validate ownership of coins is a signed message. The user should be able to sign a message using Darkcoin QT on an offline computer and then transfer the signed message to the masternode using a USB drive. This signed message contains all the proof that the network needs for authorizing the masternode to receive dividends and process darksends.

I'm getting an odd problem with my client.

Every time I try to send, it alters the amount to 0 and erases the address, calls it a send to self of 0DRK and still shows confirms... Damn strange.

Restarted client. Now different effect...

Only applies to using darksend. regular send works fine.

Waiting for entries 1/3. Stays that way until a block pops, then says idle and poof, like the darksend attempt never happened... Absolutely no log output in regard to it.

I'm not even sure where to look... Fuckin' weird...

Now spontaneously back to "payment to yourself" shit... Address is definitely not mine...

Darksend is just plain broken.

So why 20% fees for masternode payments? This essentially will create twice as many nodes and create a much higher cost to spy on the network. It also creates a larger feedback loop for the price (because as darkcoin is taken out of the supply, it drives the price up), which is good for all of the investors and security of DarkSend. Miners will get less coin, but it's been proven time and time again that when you decrease the coins generated the price will just go up to meet the cost of mining.

the wallet was encrypted by  a hard password
the wallet was started as use and not root
i have changed the ssh port from 22 to another
installed fail2ban
did all security thing and still got hacked
the starge thing is that it has been sent only 999 and not all of the darks which is 1000.6
the walet that received the dark is XwKx3mWB9ncJo5ZudqyEZ1MoQWMSmE3CwP
is there anything to do to block that wallet adress? before he move it somewhere else and sell ?