Scripting/bootstrap improvements

Various improvements to the bytecode. The bootstrap script now accepts two types of input. Support for signature verification has been added, but not yet incorporated into the bootstrapping process. `CombinedMessage()` was also replaced with `GobEncode()`/`GobDecode()` methods for `SignedMessage`.

I think one of the biggest weaknesses of the scripting system right now is input handling. There's no way to check that the input matches what you want; you just have to process it as if it were correct, and hope that bad input will cause one of the opcodes will fail. This is a stark departure from the vision of scripts verifying and either accepting or rejecting input.

To address this, I'd like to implement some rudimentary argument/type checking. I'm not sure what exactly the opcodes will look like, but probably some form of chained if-statement that calls reject if the condition fails. Of course, you don't have to do any input checking if you don't want to.

Since gob-encoded data is self-describing, it should be fairly easy to extract the type of a given argument. Unencoded types are a bit trickier though; i.e. how do you distinguish a uint64 from two int32s? Maybe all inputs should be gob-encoded? I'll have to think about this.
Only 1 wallet can exist of each ID. This looks like the script always creates a wallet of id '0'?

that should be given in the input