From 125d229df04cf1dc1f675acffe1c1354c28d3929 Mon Sep 17 00:00:00 2001 From: Determinant Date: Sun, 7 Feb 2021 17:32:00 -0500 Subject: fine tune options --- README.rst | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'README.rst') diff --git a/README.rst b/README.rst index f438cb4..7a6670b 100644 --- a/README.rst +++ b/README.rst @@ -12,14 +12,14 @@ Examples - To see all private keys and the mnemonic phrase, use ``--show-private`` (only use it after you look around and ensure there is no one else looking at your screen) -- Use arbitrary UTF-8 string as your mnemonic ``./keytree.py --custom-words --save-keystore mykeystore.json`` +- Use arbitrary UTF-8 string as your mnemonic ``./keytree.py --custom --save-keystore mykeystore.json`` - Show Fuji testnet address format ``./keytree.py --hrp fuji`` - Use Metamask's deriving algorithm: ``./keytree.py - --account-path "44'/60'/0'/0"``. By default, ETH addresses/keys use AVAX's - deriving path (AVAX C-Chain keys/addresses) instead of Metamask's. To treat - the mnemonic in Metamask's way, use ``--account-path``. Whatever deriving - path is used, the generated individual key-address pair is always valid - Ethereum format. + --path "44'/60'/0'/0"`` or ``./keytree.py --metamask``. By + default, ETH addresses/keys use AVAX's deriving path (AVAX C-Chain + keys/addresses) instead of Metamask's. To treat the mnemonic in Metamask's + way, use ``--path``. Whatever deriving path is used, the generated + individual key-address pair is always valid Ethereum format. Caveat ------ @@ -32,4 +32,4 @@ pip. Portable Binary --------------- -Use ``./keytree-0.1.0-x86_64.AppImage`` in place of ``./keytree.py``. +Use ``./keytree-0.1.1-x86_64.AppImage`` in place of ``./keytree.py``. -- cgit v1.2.3-70-g09d2