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

I gave you a nice shout out. Great website.


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

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!

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.

Very nice indeed!

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

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

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

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

@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)

@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

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

August 29th

when..??

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!!

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

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

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.

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.

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.

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.