Yes, this is still in the earlier stages as development. Using blockchainmode as a parameter is something that should be coming out this week. 

You can get the current processed block number by using `processor.getCurrentBlockNumber()`, yes that is very important to the package. There is a documentation which contains items like this on the github (plus, this is also mentioned in the token tutorial I posted alongside this announcement). I’m not sure how `steem-state` would react to when a witness skips signing a block— when this occurs, the block *number* is not skipped, correct? (If I’m right, then `steem-state` will have no trouble with skipped blocks).

STEEMSQL seems like a good idea, I’ll look into it.

Yes — I will look into that. Currently, the name of the user who ‘created’ a transaction is simply derived from `required_auths[0]`, so using `required_auths` is currently untested and is not likely to work (I don’t have much knowledge in those DApps, if you could enlighten me that would be great). That will definitely be something I will add in the future. 

Thanks for reading this article and providing feedback @therealwolf! I’ll get to work building the next versions and including some of your suggestions! Currently this is the MVP and has a lot more features to come (I mean, the package is only 150 lines of code).