Create Stacks test net testing guide

[larrysalibra]

Create a brief guide to help team members know what they should try out.

[jcnelson]

1. Follow the instructions on https://testnet.blockstack.org to install the feature/stacks-transactions branch of blockstack.js and the Blockstack CLI.
2. Generate some owner and payment private keys using the make_keychain command.
3. Fund your payment address with some Stacks via the faucet
4. Verify that blockstack-cli -t balance YOUR_ADDRESS returns your Stacks balance after it confirms. You can also verify that the TXID printed on the faucet has sufficient confirmations via blockstack-cli -t get_confirmations TXID
5. Verify the price of a name with blockstack-cli -t price NAME.id2 is priced in Stacks
6. Verify that you can register a name in the .id2 namespace, which is paid for in Stacks
7. Verify your Stacks balance decreases by the name amount
8. Verify that you can preorder, reveal, and ready a namespace paid for with Stacks.
9. Verify that you can send Stacks to a new address, and then spend from it.

If you're feeling malicious:

• Try to overdraw your account by:
  • sending too many Stacks to a new address
  • buying too many namespaces
  • buying too many names
• Try to double-register names
• Try to double-register namespaces
• Try to double-register subdomains

Note that if you want to be malicious, you should pass the -U option to disable the CLI's safety checks. By the same token (no pun intended), if you notice that the CLI lets you do something malicious without the -U, please let me know (this would be a UX bug).

Instructions are now up on the testnet site.

[jcnelson]

Tokens will be live later today.