Secure, flexible, and scalable wallet infrastructure

Turnkey x Dynamic: Embedded passkey wallets
Dynamic is launching mobile-first embedded wallets, powered by Turnkey. If you’re interested in exploring your own integration with Turnkey, contact us at hello@turnkey.com. Passkey wallets for your developers Dynamic is one of the premiere user authentication tools in crypto. They make it easy for developers to integrate polished onboarding flows and allow their end users to connect their wallets to different dApps. Dynamic is now launching a mobile-first embedded wallet, powered by Turnkey’...

Introducing Turnkey
Today, we’re excited to introduce Turnkey: secure private key infrastructure purpose-built for crypto developers. Our founding team initially met while building the world’s largest and most trusted crypto custodian, Coinbase Custody, and we’ve teamed up again to unlock the next wave of innovation in crypto. Starting today, Turnkey’s private beta is officially live. We’re also thrilled to announce our $7.5M Seed round led by Sequoia Capital, with participation from Variant and Coinbase Venture...

Understanding Solana transactions and parsing
Solana is a decentralized blockchain that launched in early 2020. It quickly began rising in popularity, and strong communities formed around applications such as Metaplex, Raydium, and more recently, pump.fun. Solana has also built their own novel architecture aiming to solve the speed and scalability aspects of the blockchain trilemma. Due to its new architecture, the way accounts and transactions work on Solana is different from more traditional blockchains such as Bitcoin and Ethereum. In...

Turnkey x Dynamic: Embedded passkey wallets
Dynamic is launching mobile-first embedded wallets, powered by Turnkey. If you’re interested in exploring your own integration with Turnkey, contact us at hello@turnkey.com. Passkey wallets for your developers Dynamic is one of the premiere user authentication tools in crypto. They make it easy for developers to integrate polished onboarding flows and allow their end users to connect their wallets to different dApps. Dynamic is now launching a mobile-first embedded wallet, powered by Turnkey’...

Introducing Turnkey
Today, we’re excited to introduce Turnkey: secure private key infrastructure purpose-built for crypto developers. Our founding team initially met while building the world’s largest and most trusted crypto custodian, Coinbase Custody, and we’ve teamed up again to unlock the next wave of innovation in crypto. Starting today, Turnkey’s private beta is officially live. We’re also thrilled to announce our $7.5M Seed round led by Sequoia Capital, with participation from Variant and Coinbase Venture...

Understanding Solana transactions and parsing
Solana is a decentralized blockchain that launched in early 2020. It quickly began rising in popularity, and strong communities formed around applications such as Metaplex, Raydium, and more recently, pump.fun. Solana has also built their own novel architecture aiming to solve the speed and scalability aspects of the blockchain trilemma. Due to its new architecture, the way accounts and transactions work on Solana is different from more traditional blockchains such as Bitcoin and Ethereum. In...
Secure, flexible, and scalable wallet infrastructure

Subscribe to Turnkey

Subscribe to Turnkey
Share Dialog
Share Dialog


<100 subscribers
<100 subscribers
OAuth is now live on Turnkey!
Turnkey enables dramatically better crypto UX by allowing innovative teams like Infinex, Bullpen, Utopia, Alchemy, and Thunder Terminal to create secure non-custodial wallets for their users.
Previously, end users could authenticate with biometric passkeys, API keys, and email. With OAuth, Turnkey customers and their users can now sign in with popular providers such as Google, Apple, and Facebook and approve transactions directly in-app — providing a seamless way to use web2 identity providers to authenticate into non-custodial wallets.
With this launch, Turnkey is taking one more step towards making wallets truly invisible. Your users don’t need to know they’re using crypto, even if they’re signing transactions onchain.
We’ve added OAuth to the set of trusted authenticators that developers can add to sub-organizations, on top of API keys, email, and passkeys. As a result, your end user can just log in with Oauth, and take actions directly onchain from within your app.

You can check out an example of OAuth in our demo wallet, or check out our docs for how to configure OAuth for your own organization.
For a more detailed overview of how OAuth works and the challenges in building it securely, read on below, or take a technical deep dive in our first engineering blog post, coming tomorrow!
Turnkey’s OAuth feature is built on OIDC (OpenID Connect). OIDC extends OAuth 2.0, which focuses on resource sharing, by providing user authentication through the following process: Users are redirected to their provider for login, then returned to the original website with a JWT containing authentication information.
We’ve taken a security-conscious approach to OAuth that utilizes TEEs, so that we can verify OIDC (OAuth) tokens in a fraud-proof way. Building on our existing TEE-based verifiable wallet infrastructure stack, we built a new secure enclave application to fetch content over TLS—known as our "TLS fetcher".
So, how does the TLS fetcher work? We’ve developed a way for enclaves to establish TLS connections, make requests, and cryptographically sign responses. Enclaves can contact remote hosts via a TCP (layer 4) proxy running outside of the trusted boundary. The secure enclave code asks the proxy to establish TCP-level connections, but remains in control of the TLS session (layer 7). The TLS session keys live in the secure enclave, on the target host, and nowhere else.
For a more technical perspective on TLS sessions within TEEs and the novel use cases it unlocks, read our Founding Engineer’s blog post with a deep dive on how we built the TLS fetcher enclave.
Stay tuned, or subscribe to our engineering blog ahead of time to get it when it drops.
OAuth is now live on Turnkey!
Turnkey enables dramatically better crypto UX by allowing innovative teams like Infinex, Bullpen, Utopia, Alchemy, and Thunder Terminal to create secure non-custodial wallets for their users.
Previously, end users could authenticate with biometric passkeys, API keys, and email. With OAuth, Turnkey customers and their users can now sign in with popular providers such as Google, Apple, and Facebook and approve transactions directly in-app — providing a seamless way to use web2 identity providers to authenticate into non-custodial wallets.
With this launch, Turnkey is taking one more step towards making wallets truly invisible. Your users don’t need to know they’re using crypto, even if they’re signing transactions onchain.
We’ve added OAuth to the set of trusted authenticators that developers can add to sub-organizations, on top of API keys, email, and passkeys. As a result, your end user can just log in with Oauth, and take actions directly onchain from within your app.

You can check out an example of OAuth in our demo wallet, or check out our docs for how to configure OAuth for your own organization.
For a more detailed overview of how OAuth works and the challenges in building it securely, read on below, or take a technical deep dive in our first engineering blog post, coming tomorrow!
Turnkey’s OAuth feature is built on OIDC (OpenID Connect). OIDC extends OAuth 2.0, which focuses on resource sharing, by providing user authentication through the following process: Users are redirected to their provider for login, then returned to the original website with a JWT containing authentication information.
We’ve taken a security-conscious approach to OAuth that utilizes TEEs, so that we can verify OIDC (OAuth) tokens in a fraud-proof way. Building on our existing TEE-based verifiable wallet infrastructure stack, we built a new secure enclave application to fetch content over TLS—known as our "TLS fetcher".
So, how does the TLS fetcher work? We’ve developed a way for enclaves to establish TLS connections, make requests, and cryptographically sign responses. Enclaves can contact remote hosts via a TCP (layer 4) proxy running outside of the trusted boundary. The secure enclave code asks the proxy to establish TCP-level connections, but remains in control of the TLS session (layer 7). The TLS session keys live in the secure enclave, on the target host, and nowhere else.
For a more technical perspective on TLS sessions within TEEs and the novel use cases it unlocks, read our Founding Engineer’s blog post with a deep dive on how we built the TLS fetcher enclave.
Stay tuned, or subscribe to our engineering blog ahead of time to get it when it drops.
No activity yet