[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[reflexmk]

@ddink7 Thanks for explanation. As is see it now "only" 50% of the 350 Dash are stolen, the remaining are regular rewarded due many owned MNs (otoh?  ). I hope one day enforcement will be truly decentralized too.

The 50% that are stolen are the ones that should go to the masternodes, you're getting it wrong. He's got a pool and probably rents a lot of hash, and keeps the whole reward for himself.

[crowning]

The backup is cool.  I guess I was thinking it did a backup on startup, which now that I think about it wouldn't make sense.  If it backs up at shutdown, then we are good. 

Right now it does a backup at startup. The reasoning is that if your wallet should corrupt your wallet.dat file you'd have a backup before that happened, not a backup of an already corrupted file.

Of course having a backup during shutdown and/or at the end of a mixing session also makes absolutely sense...I'll think about this.

[AizenSou]

weird stuff! my MN got 3 payments today! In 3hour-ish intervals.

10.5 dash in a timespan of around 9 hours. what are the ods huh!

Which version and protocol do u have on your node now?

5 nodes here and nothing since 9 days LOL

I think it was two payments inn 45 and one in 46. I didn't check balance while I was changing version.
They are both compiled from source for he pi2

Make it 10 days straight now without any payment. I'm pretty bad at lottery LOL. But at least my nodes are stable @ v46 now, don't crash every 2 hours anymore.

[110110101]

v46 is working much better for me as well.
But I seem to have lost two payouts as of now. I saw that others were not receiving payouts for blocks found by XxDotRpSDzgyAkx3jHkLZD8YYZRwbcjmmA, and now myself included. Enforcement would be nice again.

[Macno]

Anyone using the Android wallet? It used to work like a charm, then it started being slow and now it has stopped working altogether?

[Jacksp]

Goodbye reference node! haha
Step by step, dash will be BIG

[ddink7]

Also, how can enforcement be on when there is still unpaid blocks (jmma) and paid to older versions.

We turned it off, the cycle is way too small due to only a few masternodes being updated when v12 came out at first. When it settles down we'll enable it again. In the mean time I asked coinmine to pay random masternodes rather than using the winners list which will work till enforcement is enabled. We'll fix this so it doesn't happen in the next update.

Evan, could you clarify this a bit? The way I read your post at dashtalk, it sounded like the first to get upgraded end up first in line, and everybody else goes to the back of the line. That would imply that as soon as the first masternodes to upgrade get paid, everybody else will too, essentially in order of upgrade. The way I'm reading your above comment is that essentially late-to-update masternodes are "banned" for a period of time, and the cycle continues with first-to-update masternodes for some time before allowing the later masternodes to receive a payment? Or am I misreading?

Also, what conditions are you waiting for before turning back on enforcement? By "settling down" do you mean that you are waiting for these "bans" to expire, or for more masternodes to update, or what exactly?

Just trying to understand the process better...thanks!!

[jokowi]

Goodbye reference node! haha
Step by step, dash will be BIG

when..??

[Moloch]

Goodbye reference node! haha
Step by step, dash will be BIG

when..??

August 29th

[minersday]

Also, how can enforcement be on when there is still unpaid blocks (jmma) and paid to older versions.

We turned it off, the cycle is way too small due to only a few masternodes being updated when v12 came out at first. When it settles down we'll enable it again. In the mean time I asked coinmine to pay random masternodes rather than using the winners list which will work till enforcement is enabled. We'll fix this so it doesn't happen in the next update.

Evan, could you clarify this a bit? The way I read your post at dashtalk, it sounded like the first to get upgraded end up first in line, and everybody else goes to the back of the line. That would imply that as soon as the first masternodes to upgrade get paid, everybody else will too, essentially in order of upgrade. The way I'm reading your above comment is that essentially late-to-update masternodes are "banned" for a period of time, and the cycle continues with first-to-update masternodes for some time before allowing the later masternodes to receive a payment? Or am I misreading?

Also, what conditions are you waiting for before turning back on enforcement? By "settling down" do you mean that you are waiting for these "bans" to expire, or for more masternodes to update, or what exactly?

Just trying to understand the process better...thanks!!

https://dashpay.atlassian.net/wiki/display/DOC/Masternode+payment+logic

[ddink7]

1) How long until XxDotRpSDzgyAkx3jHkLZD8YYZRwbcjmmA stops hijacking 10%+ of the masternode payments?

2) Is it possible to prevent this from happening during future upgrades?

1.) How about now?  

2.) When we stop changing the masternode protocol between versions this will stop. 2 to 3 days per 3-6 months doesn't seem like much of a sacrifice in order to have the type of flexibility to development such different protocols between versions. We're able to explore different ideas and really figure out the best option for the network because of it.

Can someone explain how this hijacking works? Maybe if everyone is able to try this it would not be that unfair with all all blocks going to one person...

PS: for me ~350 Dash/day is a sacrifice. I would be happy if you can donate this amount to me every 6 month.

Miners are supposed to send 50% of the block reward to masternodes. Normally this in "enforced" (blocks without the appropriate payment to the appropriate masternode are rejected by the network). When a new version is released, consensus is not achieved instantaneously. If enforcement was left on, the network would fork. In our recent case, miners on V11 would have their blocks rejected by clients running V12, and vice versa. Evan has to wait for a consensus to emerge (usually 85%) before turning on enforcement in order to prevent forks.

P.S. If you truly have the 700 masternodes needed to generate 350 Dash/day, then it's not too great of a sacrifice. I'm not going to be crying any tears of depriving you of $1,000 a day for six days out of the year when you have $2,100,000 in assets. Sorry for the lack of sympathy.

@Pille: I realize I probably came across as a little bit of an ass here and I didn't mean it personally. Every time we have a major update (approx. 3 times per year) people start complaining about missed masternode payments. Let me do some maths:

Average MN Payment Per Day = 0.5 DASH*
Expected Income Per MN Per Year = 182.5 DASH
Expected ROI Per Year = 18.25%

When enforcement is turned off, approximately three times a year for three days at a time, 20% of the network "cheats" and doesn't pay masternodes. Everybody else continues to pay masternodes voluntarily. That means that if you own one masternode, in one year you will lose:

3 (Updates Per Year) * 3 (Days Without Enforcement Per Update) * 0.5 DASH (Expected MN Payment) * 20% (Number of Cheaters on the Network) = 0.9 DASH Per Year

On average, the owner of one masternode will "miss out" on less than 1 DASH per year due to enforcement being off during major updates. That reduces the expected ROI from 18.25% to 18.16% and is a miniscule price to pay for all the benefits that these major updates bring us.

For you to truly lose 350 DASH per day when enforcement is off:

Average Masternode Payment = 0.5 DASH Per Day
Percentage of Cheaters on Network = 20%

350 / 0.5 = 700
700 / 0.2 = 3500

You would have to own 3500 masternodes. There aren't that many masternodes on the entire network.


*Assuming 3000 masternodes and 50% masternode reward

[dashwhale]

Although i really your site  , i dont like the whale with the hat, sigar and mouchtache. I think it gives the wrong message to the broader public who enter Dash.

Its about monetary freedom worldwide, not about getting rich. The masternode owners support this idea by owning one and thus contributing to this cause.

@fuzzyduck Thank you for your comment and kind words. There are several websites out there in cryptocurrency field, which are pale. They are streamlined with reduced logos, engaging no emotions, having no real identity. We activly decided against a pale brand.

People love DASH, love running masternodes and love discussing things until their heads smoke. The interaction of the community with DASH is very emotional. The logo (bit arrogant looking whale with tophat, monocle and cigar) ironically plays with the innate whale-money theme in the cryptocurrency community. We want the people to identify with the Dashwhale brand. We want the people to remember it. The platform is open to everybody and therefore should not devide the community. It is one of the few places where regular user can voice their opinions, which are heard by masternode owners, which then will vote, taking these opinions into account.

https://www.dashwhale.org

(comprehensive masternode monitoring and budget proposal voting/discussion)

[wozzek23]

Goodbye reference node! haha
Step by step, dash will be BIG

when..??

August 29th

 
It is not nice to mock a newbie while everyone knows DASH will be big on 11th of March, 2016.

[minersday]

Although i really your site  , i dont like the whale with the hat, sigar and mouchtache. I think it gives the wrong message to the broader public who enter Dash.

Its about monetary freedom worldwide, not about getting rich. The masternode owners support this idea by owning one and thus contributing to this cause.

@fuzzyduck Thank you for your comment and kind words. There are several websites out there in cryptocurrency field, which are pale. They are streamlined with reduced logos, engaging no emotions, having no real identity. We activly decided against a pale brand.

People love DASH, love running masternodes and love discussing things until their heads smoke. The interaction of the community with DASH is very emotional. The logo (bit arrogant looking whale with tophat, monocle and cigar) ironically plays with the innate whale-money theme in the cryptocurrency community. We want the people to identify with the Dashwhale brand. We want the people to remember it. The platform is open to everybody and therefore should not devide the community. It is one of the few places where regular user can voice their opinions, which are heard by masternode owners, which then will vote, taking these opinions into account.

https://www.dashwhale.org

(comprehensive masternode monitoring and budget proposal voting/discussion)

Can I get google two-factor authentication to this? =)

[dashwhale]

@minersday

Yes, you already can enable 2FA at Dashwhale.org

[Solarminer]

If I generate a new receive address on a wallet and send funds to it.  Then load an old wallet, it still gets the transaction.  Just the label of that transaction won't come through.  If all the inputs/outputs of mixing go through the blockchain an old wallet version should still get the inputs.  Is there something else that causes this to fail?  Maybe the wallet can't allow a send and receive from the same wallet when it syncs old transactions?  Can this be fixed?
Requiring a backup after mixing doesn't seem like a production level solution.

Backup wallets keep 1000 unused addresses.  If your mixing used up those addresses, then a backup will not show any of the addresses generated afterwards, and with nearly 1000 coins, you probably have gone through many of those addresses

Thanks TS.  Ahh.  Not so easy to fix that.
Crowning, thanks for your input too.  Any chance we can force a wallet backup after mixing?  Or maybe just add a note near the darksend mixing rounds/amount option or a dialog ok box that warns you to backup your wallet after mixing?

But you can increase the number of keys made with keypool in the config at wallet startup so using keypool=100000 for example.
Satoshi said that each key uses 1k, so normally only 1 megabyte space used for default 1000, you could easily increase it to 100,000 keys and still only use 100 megabytes, I imagine loadup and wallet encryption may be a little slow.
https://bitcointalk.org/index.php?topic=1414.0

Thanks Sub-Ether.  Maybe there should be a check of used keys(n) during shutdown.  It adds the keypool=n+1000 in the config file to generate more keys.  If backups are done on startup and each mix uses 200 keys, this should always keep a valid backup(even up to 4 or 5 mix sessions).

EDIT: I added keypool=2000 in my config and it didn't changed my wallet size.  I had to run keypoolrefill to get the wallet to change size. 
Suggestion:  Set keypool as needed to keep 1000 free addresses.  On shutdown run keypoolrefill and backup wallet.

[minersday]

@minersday

Yes, you already can enable 2FA at Dashwhale.org

Very nice indeed!

[Solarminer]

Can't thank you enough.   Enormous [digital] high five to Solarminer... and everyone else that lent a hand.

fixed it for you - and
that is actually called a 'wi-five'
:-P

i friend of mine asked me where he can find the update button in his wallet. Good question...
[/quote]
Nice MB.  Like it.

About the update button, how about a check on startup and if you need to update it asks if you want to update?

I would suggest an auto update option added for masternode owners.   Something like adding auto-update=yes in the config file.  Should be easy right?  LOL.

[Rux]

Guys, me and rentahash have 400 DASH ...

As some of you know, i also have Masternode service like splawik and rest of the guys!

Currently i have 2 MN active, and so close to third!

we are short 600 DASH for Masternode, is anyone interested to pinch in with us? OTOH? anyone?

I have server ready, synced, just waiting for dash.conf to be configured and masternode could be active!



EDIT

i just got 300 DASH more, so thats 700 DASH for masternode ready!

300 SHORT, cmmon who's with us??

EDIT 2:

i dont take any fee, only fee is monthly 5$ that i take from MN earnings to pay server!

[anonymousxx1503]

@minersday

Yes, you already can enable 2FA at Dashwhale.org

I gave you a nice shout out. Great website.


https://twitter.com/CryptoArmada/status/634407619583717376