If your app touches anything onchain, you’re building on top of a wallet. This thread breaks down the basics of wallet creation and how Turnkey helps you build secure, seamless wallets efficiently 🧵

1/ Crypto wallets store cryptographic keys and use them to sign transactions, verify identities, and interact with blockchains. The wallet signature is what gives each transaction its authority. Without it, nothing moves onchain.

2/ Regardless of your design choices, the same foundational components are needed to build a functional and secure crypto wallet. Key generation and management, address derivation, transaction signing, network communication and a robust architecture with strong security.

3/ Designing a wallet means navigating four hard tradeoffs: ◾Security: where keys live, and who has access ◾Usability: how users interact with the wallet ◾Flexibility: how it scales across ecosystems ◾Control: how much control you have as a builder

4/ Every wallet design hinges on three core decisions: Who controls the keys, how onchain authorization is enforced, and how users connect to the wallet. These choices define the architecture and shape everything from UX and onboarding to recovery and scaling.

5/ Turnkey gives developers the building blocks for secure wallets by generating, storing, and signing keys entirely within secure enclaves. They never leave these isolated environments. No one, not even Turnkey, can access raw private keys.

6/ Wallets aren’t just keypairs, they’re systems for secure, authorized control of assets + actions. Turnkey powers secure wallets with enclave-backed keys and policy-driven signing, designed for developers who want control + speed. Check out the blog 👇