From f9e5ef378f9ba6ef75fb140db448b0a3c28f55cc Mon Sep 17 00:00:00 2001 From: Anton Livaja Date: Wed, 2 Apr 2025 20:20:07 -0700 Subject: [PATCH] remove section --- _posts/2025-03-20-bitby-report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2025-03-20-bitby-report.md b/_posts/2025-03-20-bitby-report.md index 4982c99..1bb1209 100644 --- a/_posts/2025-03-20-bitby-report.md +++ b/_posts/2025-03-20-bitby-report.md @@ -121,7 +121,7 @@ This reference design was developed for the Safe{Wallet} team, but it can be app 4. **All sensitive operations are fully verified offline before any cryptographic action is taken** -This design drastically reduces exposure to remote attacks and central points of trust, aligning closely with Distrust's first-principles security model. Some tools have been built in the Web3 ecosystem, such as [safe-utils](https://github.com/openzeppelin/safe-utils)—but, unfortunately, they completely miss the point of cold wallets, and encourge people to use these tools online. Safe-utils is also not bit-for-bit reproducible as of this writing, which disqualifies it as an adequate solution for a stack managing large sums. +This design drastically reduces exposure to remote attacks and central points of trust, aligning closely with Distrust's first-principles security model. #### Strategy 2 - Use remotely verified service