In existing implementation using `WorkerBee` in Denser application is difficult and inefficient. There is an existing instance of `Wax` and `chain` in Denser application (rather huge and extended in custom way), but it cannot be passed to WorkerBee. Denser applications need observing whether transactions, invoked by their users, have been applied into the Hive blockchain, however this doesn't need constant observing of chain blocks for the whole life of Denser application. Denser needs to start and stop a singleton of `WorkerBee`, and restart it for a given block. The focus should be pointed to the method `WorkerBee.start`. Another option could be exporting `WorkerBee` class and allowing to extend it, so also modifying method `WorkerBee.start` this way. I'm opting for that latter thing – enabling a possibility of extending `WorkerBee` class (and other stuff as well). See [thread on Rocket Chat](https://chat.syncad.com/channel/hive_front?msg=YL6ga5zeH9EMvhBpq).