Turnkey’s Post

Why build embedded wallets with Turnkey? Because we actually care about security. Turnkey considers a broad spectrum of critical threats, from insider schemes to plain old phishing, for our embedded wallet implementations. Here are some risks you should be considering in your threat model: 🚨THREAT #1: Compromise of your database With Turnkey’s non-custodial embedded wallet implementation, every single request must be cryptographically stamped by a secret only your end user holds. That means even if your database is hacked, your users' funds are safe. 🚨 THREAT #2: Compromise of your front-end application A Turnkey non-custodial embedded wallet implementation NEVER exposes a seed phrase, not even client-side. Doing so creates a massive threat vector for a long-lived persistent attack, whereby a vulnerability allows an attacker to scrape your users’ mnemonic phrases over a prolonged period of time and steal funds all at once. Not only do we never expose seed phrases, but user authenticators can be rolled in the case of an attack and scoped to very specific actions. Turnkey also allows you to set detailed policies to ensure sensitive actions require multiple approvals or specific types of authentication by the end user. 🚨THREAT #3: Compromise of your provider's API At Turnkey, we run all secure workloads, including tx signing, parsing, and policy evaluation, in secure enclaves. 🔐 Secure enclaves = Highly constrained computing environments designed for sensitive data or workloads We’ve taken huge engineering leaps to be able to run these critical applications in secure enclaves because it enables us to secure any action that could impact wallet security, not just the storage and access to private keys. In other words: Every single sensitive operation within Turnkey’s environment — signing messages, modifying policies, parsing transactions, etc. — executes inside the trust boundary. We trust our secure environment and we don’t trust anything else. 🚨 THREAT #4: Compromise of your provider’s employee’s devices Turnkey operates with strict isolation between developer machines and the fully segregated machines we use for deployments. 🚨 THREAT #5:  Insider attacks from your provider Within Turnkey, no single engineer has the power to modify Turnkey’s code.  Our use of secure enclaves and our custom, deterministic operating system, QuorumOS, means that multiple controls are in place to prevent unilateral action. Our relentless focus on security means that you have more time to focus on product. Secure embedded wallets are the future. Learn more: https://lnkd.in/dGqFf2-p