In some future world, I can see the case for switching the order of the args for saveAccountState -- it looks like it is most common for reason to be sent, then a callback, then an existing transaction. Not something for this pull request though, as it is an existing API, just calling out something that caused me to trace through the code more to find out why two nulls normally showed up in saveAccountState calls.