From 7456fbc8a1816e27f9748d4df4f99171338aae1c Mon Sep 17 00:00:00 2001 From: Joe Date: Mon, 31 Oct 2022 17:07:32 +0000 Subject: [PATCH] update clef page --- src/pages/docs/fundamentals/account-management_clef.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/pages/docs/fundamentals/account-management_clef.md b/src/pages/docs/fundamentals/account-management_clef.md index 3e3d608941..0e547995f5 100644 --- a/src/pages/docs/fundamentals/account-management_clef.md +++ b/src/pages/docs/fundamentals/account-management_clef.md @@ -7,7 +7,13 @@ Geth uses an external signer called [Clef](/docs/clef/introduction) to manage ac ## Initialize Clef -The first time Clef is used it needs to be initialized with some information about where to store keys and a password for encrypting its internal data. This password is known as the "master seed". To do this, pass the path to the keystore to `clef init`. +The first time Clef is used it needs to be initialized with a master seed that unlocks Clef's secure vault and a path where the vault should be located. Clef will use the vault to store passwords for keystores, javascript auto-signing rules and hashes of rule files. To initialize Clef, pass a vault path to `clef init`, for example to store it in a new directory inside `/home/user/go-ethereum`: + +```sh +clef init /home/user/go-ethereum/clefdata +``` + +It is extremely important to remember the master seed and keep it secure. It allows access to the accounts under Clef's management. ## Connecting Geth and Clef