aboutsummaryrefslogtreecommitdiff
path: root/README.rst
diff options
context:
space:
mode:
authorDeterminant <[email protected]>2021-05-17 13:24:47 -0400
committerDeterminant <[email protected]>2021-05-17 13:24:47 -0400
commit0471b3731fd24ef4e5d4c6d7a6a19e942b27dfa4 (patch)
tree79cae3a238eabdd648cafbb9fee9e69c73769635 /README.rst
parentb60df988b3d456b73a90a59e8b5cfe78e66f4002 (diff)
...
Diffstat (limited to 'README.rst')
-rw-r--r--README.rst6
1 files changed, 0 insertions, 6 deletions
diff --git a/README.rst b/README.rst
index c9c4f4a..752b4fa 100644
--- a/README.rst
+++ b/README.rst
@@ -14,12 +14,6 @@ Examples
screen)
- Use arbitrary UTF-8 string as your mnemonic ``./keytree.py --custom --save mykeystore.json``
- Show Fuji testnet address format ``./keytree.py <your options> --hrp fuji``
-- Use Metamask's deriving algorithm: ``./keytree.py <your options>
- --path "44'/60'/0'/0"`` or ``./keytree.py <your options> --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
------