Charity is just that.  Open up a donation address, pick a cause, and request donations.  This doesn't have anything to do with voting on the masternode network.

I put a ton of time and effort into mining curecoin and other altruistic coins.  It isn't that I am opposed to charity, it just isn't going to be the first thing a group of 3100 masternodes vote for.  (Or maybe it is, so submit a proposal)

There are some of us that believe this is a good price and good time to buy.  (and if you just got paid from installing a few solar jobs, you have some funds to put into DASH.)

The question is, do you trust a bank(subject to bail-ins), a fiat currency(inflating away), or the first ever decentralized, distributed voting, private, instant, secure cryptocurrency, with an x% payback with masternodes.

Wooooh.  Let's not think of DASH like a fiat currency controlled by an appointed republic acting like they are saving the world that can print as much as they want while inflating away value while digging a deeper debt hole.

There are already some charity projects.  Charitycoin, 2givecoin, etc.  You can see how well they are doing, but it isn't like they are getting top 100 on coin market cap.  Startcoin is another coin tailored for kickstarter projects.

1000 DASH for a masternode is much more valuable to spend today when you think about promotion, development, exchanges, etc - rather than distributed over 5-6 years of payments.  Of course, I totally could be wrong, and masternode paying panda saving and free server proposals could start getting approved left and right.  Submit a proposal and let's see what happens.

Buy wall is now 59.4BTC.  With the charts above, looks like the .0102 will be too low. 

Evan, I would assume you only send amounts in binary, so there must be another 4.6BTC in transit.  LOL.

Evan, thanks for the charts.

Yes, also agree.  Especially the sub-quorum stuff.    (I don't actually know what that is, but it sure works.)  It is so fast that it is hard to measure.

I did however check the "send zero-fee transaction if possible" and it won't send via InstantX when this is checked.  I suggest that zero-fee box is mutually exclusive with InstantX.  (you can only check one or the other - not both)

I will predict that instead of InstantX being an option, it will be standard with all transactions.

Anyone can start a masternode.  Requirements are:
1000 DASH and a static IP address.
Typically, you would rent a server for about $5/mo to host your masternode.

Block rewards are split as below.
45% to miners
45% to masternodes
10% to development projects(that are voted in by masternodes)

Typical earnings for a masternode are about 0.5 Dash/day.
Masternodes don't use power like miners do.  They do a lot of transactions and need about 100GB of bandwidth/mo, 500MB of ram, and a mid to low range CPU.

Check out the masternode guides on the dashtalk site for specific details on setting up a masternode.

As for coins, I believe the max coins that will be mined is 22 million.  This is distributed about 5 at a time in blocks mined every 2.5 minutes that decreases 7% each year.

There are some really innovating ideas here.  Masternodes to privatize and speed up transactions.  Decentralized voting and funding structure.  These are missing in Bitcoin and will enable DASH to succeed long into the future.  Once you go DASH you won't go back.

And trolls like us too.    

My guess is they are just counting 1 transaction as a vote and any transaction amount is still 1 vote.  Just fire up the coinwallet.eu dust maker and you have all the votes you would ever need.  :-)

Actually, the voting ends at a certain block.  There would be no reason to send 1000s of transactions early in the vote as it would create competition.  So you wait until the bock before the votes are counted and put enough BTC in to make your choice win.  Just like the end of an ebay auction.

Thanks for the video link.  If the BTC are returned to you, there is still a cost in fees.  Most likely an automated program can be created to create the wallets, vanity addresses, and vote.  So maybe a combination of smarts and BTC would win the vote.

It looks like they create several bitcoin vanity deposit addresses.  Voters send funds to the address of their choice to vote.  So effectively, whoever has the most bitcoins has the most influence on the vote.  Pretty close to the way corporations work with most governments, LOL.

Maybe they enforce signatures or something, but really there is nothing stopping someone from creating 1000s of wallets to vote.

Now that I think of it, this would be like ebay for voting.  That last block will have a ton of bids, I mean votes, to make sure their choice wins.

Another good ssh client is Bitvise SSH.  It not only saves login info, but it also does file transfers over ssh.

I am impressed with this too.  Kind of like looking at a piece of art.  I do see the dash-cli getblock.  We could used that instead of my complicated dash-cli with grep commands.

Thanks Moocowmoo.  I figured there would be tweaks on this.

It makes sense to change the sleep to 2500 (about 41 minutes).  Should be good enough for 99.9% of the blocks.  It is still before the 70 minutes that you get kicked off the pay queue if you don't restart in time.  Thanks for the info on the kill dash-shutoff.

I haven't had any problems with .53 either.  But .51, .49, ... didn't do so well.  Usually, they just drop off.  When we have new releases, it is a very good idea to have something like this running.  Actually, using block number makes determining if the dashd is actually running much easier and more robust.  Instead of looking at this program like a crutch for the current version, think of it like a safety net so you can really throw out innovative and ground breaking features.

And just like the other restart scripts.  You can start with screen so it runs when you logout.
to start with screen type:
screen -dm /blockcheck.sh

This will run forever, so if you want it to stop type
screen -ls and get the number replace that with the 11111 below.
screen -X -S 11111 kill

You could also email yourself if you did restart with this command by adding this near the last /home/dash/dashd line.
ssmtp user@something.com < /home/dash/m.txt
Assumes you setup this script first.
https://dashtalk.org/threads/v12-release.5888/page-32#post-64582

And now, I announce the first ever automated block checking and restart script for your masternodes.

This program grabs the current block. Then waits 16 minutes(longest block I found was about 13 minutes) and checks that block. If the new block is bigger it stores the new block as the old and waits another 16 minutes. If the old block is not bigger we assume dashd is locked up. It first logs the last 30 lines of the debug.log and tries to shutdown nicely. And if that doesn't work it kills the process. Then restarts and finds blocks again. This should also restart the dashd if it doesn't get any output(like if it isn't running).

So for those with more than one masternode on a server, you should change dashd to dashd1, dashd2, etc. Then use pkill -9 dashd1, dashd2, etc. If you just use dashd it will shut anything down with dashd in it. If there is any interest, I could make a script for multiple nodes.

Start from crontab or with screen.  Go back a dozen pages for more info on those options.

Just to be clear on this.  DASH as it is right now, would still have this problem with transactions not scaling up.  DASH does have a voting mechanism and actual development budget, which can easily facilitate the tough decisions like what Bitcoin is trying to do.

Evan has said he has plans to make transactions unlimited and I expect this white paper will have some detail about that.

It is a bigger problem than just block size.  The problem is the size of the transactions and not being able to scale up(with today's hardware).  If any of the cryptos try to facilitate all pos transactions, the blockchain will be so big in a few months that they will be too slow to use.  Yeah, blocksize can limit blockchain growth and prevent usability problems, but at the risk of reducing transactions (200,000,000/year right now for bitcoin).

This white paper Evan is doing is going have some interesting developments and I am looking forward to it.

With the small inputs and a transaction size limit of about 675 inputs(I think it is actually about 10,000Bytes).  The maximum fee you could put on these small inputs is ~.0000675 or you would spend more in fees than the transaction.  Transactions with fees above ~.00007 should still go through.

The wallets need to be smart enough to know the transaction fee for the speed at which you need the transaction to go through.  Bitcoin has a fast or slow bar for confirmations, but I don't think this changes with network conditions - I could be wrong here.

Fee needed is now .0000483  (about 12 cents).  Check out the stats here.
https://www.blocktrail.com/BTC

I read this as transfer out of Poloniex.  I don't think they allow you to change the fees.  I think the correct answer here is to convert to DASH, transfer out and wait for the test to finish before converting back.

Depends on how you look at it.  Does DASH do well if Bitcoin dies from this test?

I am so conflicted.  Free BTC while causing havoc with the bitcoin network, possibly helping DASH.