diff --git a/guide/private-key-management/overview.md b/guide/private-key-management/overview.md index 4a210f791..25e10328d 100644 --- a/guide/private-key-management/overview.md +++ b/guide/private-key-management/overview.md @@ -127,6 +127,14 @@ The use cases for shared schemes include spouses managing a joint account, group - [Multi-key](/guide/private-key-management/multi-key/) - several keys and several people control the wallet +### Non-recommended schemes + +There are also several non-recommended private key schemes not detailed in this guide that are not widely used due to their poor security, lack of interoperability and unnecessary complexity. Below are schemes not recommended to be used in your Bitcoin applications and why. + +- Key sharding (Shamir's secret sharing): Sometimes referred to as an alternative to multi-key setups, but the security risks are much greater. Its major drawbacks are a single point of failure, no key invalidation, no widely used implementation (though [SLIP-0039](https://github.com/satoshilabs/slips/blob/master/slip-0039.md) does exist), and poor auditability. Read more about the issues with key sharding [here](https://docs.keys.casa/wealth-security-protocol/rejected-key-schemes/key-sharding-shamirs-secret-sharing). +- DAT files: A legacy form of backing up Bitcoin private keys that use the generic .dat file type. These are still used today by [Bitcoin Core](https://bitcoincore.org/) due to [security concerns](https://bitcoin.stackexchange.com/questions/92716/why-keys-generated-in-bitcoin-core-mismatch-that-from-online-generators-despite) with non-hardened key derivation. This form of private key scheme is not widely adopted due to its lack of interoperability among wallets, not being human readable like a recovery phrase, and being potentially insecure if the user does not encrypt the keys contained within the file. +- 1-of-2 multi-key: This multi-key scheme may prevent users from misplacing a private key but offers no security benefits with added complexity to the scheme. Making multiple redundant copies of a single sig key offers the same benefits around key misplacement without the added complexity. Learn more [here](https://docs.keys.casa/wealth-security-protocol/rejected-key-schemes/1-of-2). + --- Let's start by looking at the [automatic cloud backup](/guide/private-key-management/cloud-backup/) scheme.