From 0760932b04e2dc1e4b566c58532b711090d08958 Mon Sep 17 00:00:00 2001 From: Olivia Thet Date: Mon, 27 Nov 2023 15:06:13 -0500 Subject: [PATCH] small ordering change --- docs/integration-guides/export-wallets.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/integration-guides/export-wallets.md b/docs/integration-guides/export-wallets.md index c314d04..db37e76 100644 --- a/docs/integration-guides/export-wallets.md +++ b/docs/integration-guides/export-wallets.md @@ -102,11 +102,13 @@ Turnkey also supports exporting raw private keys. To implement export for privat ## Cryptographic details -Turnkey's export functionality ensures that neither your application nor Turnkey can view the wallet mnemonic or private key. The following diagram summarizes the flow: +Turnkey's export functionality ensures that neither your application nor Turnkey can view the wallet mnemonic or private key. - +It works by anchoring export in a **target encryption key** (TEK). This target encryption key is a standard P-256 key pair and can be created in many ways: completely offline, or online inside of script using the web crypto APIs. + + The following diagram summarizes the flow: -Our export flow works by anchoring export in a **target encryption key** (TEK). This target encryption key is a standard P-256 key pair and can be created in many ways: completely offline, or online inside of script using the web crypto APIs. + The public part of this key pair is passed as a parameter inside of a signed `EXPORT_WALLET` or `EXPORT_PRIVATE_KEY` activity.