Any chance you want to share what the problem was that has now been resolved?  Was it the result of an outside attacker, an in-house mistake, or the result of regulatory action?  I think given the nature of the business and the crackdowns in the crypto industry, it could be helpful to share details with your users and for others in the field to be aware of to help them avoid similar circumstances in the future for their own services.

Today, we release 0.4.7.8 fixing several issues including a High severity security issue only affecting the 0.4.7.x series. You can track this issue with TROVE-2022-001 52 and CVE-2021-38385 50.