From e91c223a79f06afb32fb5d87287d6de7a7bf7d52 Mon Sep 17 00:00:00 2001 From: Bobinson K B Date: Tue, 8 Dec 2020 14:05:30 +0000 Subject: [PATCH] GitBook: [master] one page modified --- witnesses/obtaining-private-keys-for-use-in-cli_wallet.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/witnesses/obtaining-private-keys-for-use-in-cli_wallet.md b/witnesses/obtaining-private-keys-for-use-in-cli_wallet.md index efb6910..38d0326 100644 --- a/witnesses/obtaining-private-keys-for-use-in-cli_wallet.md +++ b/witnesses/obtaining-private-keys-for-use-in-cli_wallet.md @@ -1,10 +1,6 @@ # Obtaining private keys for cli\_wallet - - -#### - -#### 3. Using password generated in GUI wallet in _cli\_wallet_ +### Using password generated in GUI wallet in _cli\_wallet_ In the Graphene based blockchains like Peerplays the hierarchical permissions like fund transfer, sending memo etc are separated using different roles and Public-Private key-pairs for each role. We have 3 types of roles OWNER, ACTIVE and MEMO. These keys are generated using a brain key.