More detailed list:
5e6ca9a([update] csv export for curator rewards)
23523c7([add] csv export for benefactor rewards [add] csv export for curator rewards)
9e0e570([add] new queue settings for process author rewards)
b07e3e7([update] mongodb settings [add] test for tokenSend)
b650f74([add] block listener [add] command for get block [add] job for process blocks [add] model BchBlock for saving information about processed blocks)
668a84f([add] to blockchain api add new function getPost() for receiving posts from Blockchain [add] new wss servers to GOLOS node list)
b79ee14([add] to blockchain api add new function sendTokenToMany() for sending STEEM/SBD/GOLOS/GBG to any accounts)
1e6304d([fix] cleaning)
7ddc30d([add] to blockchain api add new function getOpsInBlock for receiving all operations from blocks)
4816cf1([add] to blockchain api add new function getOpsInBlock for receiving all operations from blocks)
f2e86fc([update] new articles)
More about block listner
Some time ago I had a telegram notifier bot, which was able to notify about various events that occurred in the blockchain.
But he was abandoned for various reasons. And now I decided to restore it as part of the Accusta system.
The listener of the blocks is necessary for catching events occurring in the blockchain.
There is command bch:get-block In https://github.com/semasping/Accusta/blob/master/app/Console/Commands/BchGetBlocks.php
which starts by cron every 10 minutes. It takes last_irreversible_block_num and processed the difference from last with the previous start. Then for each block, a separate job is run in a special queue https://github.com/semasping/Accusta/blob/master/app/Jobs/ProcessBchBlock.php.
And then in ProcessBchBlock is run more jobs for each event which need to be processed.