From b21cb55f867959df87eb6a9c4801182d12a212f7 Mon Sep 17 00:00:00 2001 From: jonesmarvin8 <83104039+jonesmarvin8@users.noreply.github.com> Date: Mon, 15 Jun 2026 15:49:26 -0400 Subject: [PATCH] Update docs/lee_key_protocol.md Co-authored-by: Moudy --- docs/lee_key_protocol.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/lee_key_protocol.md b/docs/lee_key_protocol.md index 2a362913..1926f850 100644 --- a/docs/lee_key_protocol.md +++ b/docs/lee_key_protocol.md @@ -102,7 +102,7 @@ In both cases, the chain code `cc` is the last 32 bytes of `hash_value`. ### Schnorr secret key -The Schnorr secret key (`ssk`) is used for managing public ownership and authorization Authorization for spending funds and, in some cases, modifying account data is handled by signing the transaction with the account’s Schnorr secret key. The Schnorr secret key serves as protective layer between the account's secret key and quantum attackers. +The Schnorr secret key (`ssk`) is used for managing public ownership and authorization. Authorization for spending funds and, in some cases, modifying account data is handled by signing the transaction with the account’s Schnorr secret key. The Schnorr secret key serves as a protective layer between the account's secret key and quantum attackers. The Schnorr secret key (`ssk`) is computed from the secret key (`sk`) as follows: 1. `private_key` is the scalar associated in the basefield for `secp256k1` generated from `sk`.