As you may have noticed, we have temporarily disabled Lelantus via our emergency switch after we observed irregular behavior in Lelantus and several suspicious transactions.
Our core team is working with several parties, including engineers from Trail of Bits (who audited our Lelantus cryptographic library), Sarang Noether (cryptographer) and a black hat to identify the issue. We have made significant progress in narrowing down the cause and are working on a proof-of-concept code to verify that what we’ve found is the core issue before resuming Lelantus functionality. Our team is also determining a plan to restore Lelantus functionality with minimum impact.
While we have taken practical precautions including audits and review, developing cutting edge privacy tech comes with risks. The safeguards we put in place in recognition of this has mitigated damage as the technology matures and becomes battle-tested.
We will post updates as we have them, and thank you for your patience.