quantus/extension
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

Move FAQ to docs (#598)

Browse Source 
* Update README.md

* add another link to the doc

* Update README.md
This commit is contained in:
Thibaut Sardan
2020-12-22 22:25:45 +01:00
committed by GitHub
parent 4f806db60d
commit 27df3807a6
1 changed files with 2 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -19
View File
@@ -17,25 +17,8 @@ As it stands, it does one thing: it _only_ manages accounts and allows the signi
![interface screenshots](docs/extension-overview.png)
## FAQ
### I want to send funds directly from the extension.
The extension is not meant to be a full wallet replacement. It tries to focus on pure account management while making this as smooth as possible. The extension simply makes the stored/imported accounts available to any dApp that can perform transfers, allow you to vote on democracy proposals and/or participate in any feature available on Polkadot and Substrate. We really aim to keep this singular account-only focus with no network connectivity, leaving the hard-work of understanding chains and their intricacies over to over to wallets such as [polkadot-js/apps](https://polkadot.js.org/apps/).
### My addresses display differently on the extension vs a dapp.
Unlike a dapp, the extension itself does not connect to a network. The addresses are formatted with a network-specific prefix, which on a dapp, is retrieved upon connection from the chain properties. Underlying the public keys can be the same, but based on the address formatting the display could be different. This does not affect operation at all. You can choose which format to display the addresses in your extension via the "Options" screen.
### What does it mean to derive account?
We can imagine that accounts are stored as a tree. It allows us to structure accounts by our own needs. The root account is created at first and all the new ones will be its children by default. If we want to derive from other accounts, it can be done by selecting Derive New Account option in parent account’s context menu. Before deriving an account, the [HDKD derivation path](https://github.com/paritytech/parity-signer/wiki/HDKD-on-Parity-Signer#the-form-of-path) can be provided - it is a great tool that could be used for further account structuring.
The format of a derivation path is `//<hard>/<soft>///<password>` where
* `//hard` means that the connection between accounts is not “visible” for public addresses.
* `/soft` connects accounts in a manner that can be proven.
* `///password` provides an additional (optional) encryption.
### Why can't I import an account with a hex-encoded private key?
This is a deliberate choice since mnemonic phrases are easier to write down, to memorize or type in a field. They have a checksum (not every 12/24 words list is a valid mnemonic) and constitute a much better means of holding un-encrypted information. Therefore, this extension does not and will not have the functionality to recover an account from a hex seed phrase.
## Documentation and examples
Find out more about how to use the extension as a Dapp developper, cookbook, as well as answers to most frequent questions in the [Polkadot-js extension docuementation](https://polkadot.js.org/docs/extension/)
## Development version