Also, what you wrote about things catching up is correct. The LUV token uses a python script that "listens" to the Hive blockchain and scans for !LUV commands. When it gets one, the script sends one LUV from the @LUVshares account to the person being commented to. Sometimes the communication between the script and the witness nodes gets broken. Then, it tries to reconnect and usually does. However, at times things time-out and the script shuts down and must be manually restarted. When restarted, it simply goes back to the last block recorded, then moves forward, picking up any !LUV commands that were left during the down time. !LUV
Also, what you wrote about things catching up is correct. The LUV token uses a python script that "listens" to the Hive blockchain and scans for
!LUVcommands. When it gets one, the script sends one LUV from the @LUVshares account to the person being commented to. Sometimes the communication between the script and the witness nodes gets broken. Then, it tries to reconnect and usually does. However, at times things time-out and the script shuts down and must be manually restarted. When restarted, it simply goes back to the last block recorded, then moves forward, picking up any!LUVcommands that were left during the down time. !LUV@crrdlx(1/5) gave you