Submit leader's vote after observing 2/3 validator votes (#780)

* fixup!

* fixups!

* send the vote and count it

* actually vote

* test

* Spelling fixes

* Process the voting transaction in the leader's bank

* Send tokens to the leader

* Give leader tokens in more cases

* Test for write_stage::leader_vote

* Request airdrop inside fullnode and not the script

* Change readme to indicate that drone should be up before leader

And start drone before leader in snap scripts

* Rename _kp => _keypair for keypairs and other review fixups

* Remove empty else
* tweak test_leader_vote numbers to be closer to testing 2/3 boundary
* combine creating blob and transaction for leader/validator

README.md

@@ -71,6 +71,20 @@ These files can be generated by running the following script.
 $ ./multinode-demo/setup.sh
 ```
 
+Drone
+---
+
+In order for the leader, client and validators to work, we'll need to
+spin up a drone to give out some test tokens.  The drone delivers Milton
+Friedman-style "air drops" (free tokens to requesting clients) to be used in
+test transactions.
+
+Start the drone on the leader node with:
+
+```bash
+$ ./multinode-demo/drone.sh
+```
+
 Singlenode Testnet
 ---
 
@@ -85,22 +99,8 @@ $ ./multinode-demo/leader.sh
 ```
 
 Wait a few seconds for the server to initialize. It will print "Ready." when it's ready to
-receive transactions.
-
-Drone
----
-
-In order for the below test client and validators to work, we'll also need to
-spin up a drone to give out some test tokens.  The drone delivers Milton
-Friedman-style "air drops" (free tokens to requesting clients) to be used in
-test transactions.
-
-Start the drone on the leader node with:
-
-```bash
-$ ./multinode-demo/drone.sh
-```
-
+receive transactions. The leader will request some tokens from the drone if it doesn't have any.
+The drone does not need to be running for subsequent leader starts.
 
 Multinode Testnet
 ---