StakeHound, a firm that enables staking, is suing custody service Fireblocks for allegedly contributing to the loss of private keys that accessed about $75 million worth of crypto.
StakeHound filed the lawsuit against the Israeli-based Fireblocks in the Tel Aviv District Court. The firm claims Fireblocks’ negligence led to the loss of the keys. According to the court documents reported by Calcalist, a Fireblocks employee failed to backup the keys, which were subsequently “deleted,” leaving StakeHound unable to access 38,178 ETH, or more than $76 million. Those court documents also claim that the employee was working in “an unsuitable work environment,” according to Calcalist.
StakeHound contracted Coincover’s service as well in holding the keys, but in order for the keys to be verified, Fireblocks had to also retain a copy. In a blog post, Stakehound wrote:
“In short, a series of errors by Fireblocks caused the loss of 2 keys that are part of the 3-of-4 threshold signature for the shards that form the withdrawal key. Fireblocks (1) did not generate their private keys in a production environment, (2) did not include the private keys required to decrypt their 2 key shares in the backup, and (3) lost both keys.”
But Fireblocks contends that it was never in charge of the keys.
In a blog post published Tuesday, Fireblocks said its research team filled a request to create a set of “BLS key shares” related to StakeHound’s ETH 2.0 staking project, which were managed outside the Fireblocks platform and not part of its usual wallet procedures.
This project wasn’t a usual service, it was a one-off request in which Fireblocks lent StakeHound resources to help build its open-source library.
Fireblocks said those using its wallet structure aren’t at risk for losing their keys because of the firm’s multiple backup procedures — procedures that weren’t included in the services StakeHound contracted, according to Fireblocks.
According to Fireblocks, StakeHound generated its own keys and stored them outside the Fireblocks platform. Fireblocks agreed to temporarily store the BLS keyshares, but because it doesn’t support BLS with its platform, Fireblocks said the same backup procedures that are normally found on Fireblocks didn’t apply. The keys remained in temporary storage, and a few months later temporary storage failed.
In the lead-up to the failure of the temporary storage, Fireblocks alleges that StakeHound also failed to store backups with a third-party service provider despite urging the firm to do so multiple times. It also communicated that StakeHound was required to perform a backup within 14 days of the key generation. StakeHound has not said whether it followed these directions.
Fireblocks is still trying to recover the lost ETH, according to its blog post.
© 2021 The Block Crypto, Inc. All Rights Reserved. This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
News Source from TheBlockCrypto.com