Security concerns

Anyone with access to the server the processor is running on will likely have access to the private key of the processor and the database password, as they will be in the config file/an environment variable/in memory. (However it should be noted that these values are never logged even if problems with these values arise, so the logs are safe to view.)

This means people who have access to these values can sign blocks, create contracts (which executes code on the server running the processor) and change the database. This may result in nodes rejecting the blocks or constructing their own version of the truth that differs from the processor and cannot be corrected. The only remedy is creating a hard fork where only the nodes that agree to this will use the corrected value. It should be noted that even if the nodes agree to this it is no easy or quick process and should be avoided at all cost.